docs: Clean up wip pages (#2282)

Co-authored-by: Tillmann <112912081+tillmann-crabnebula@users.noreply.github.com>
Co-authored-by: Chip Reed <chip@crabnebula.dev>

Author: 3 people

astro.config.mjs

@@ -388,7 +388,7 @@ export default defineConfig({
     // v1 /guides/debugging -> /guides/debug
     ...i18nRedirect('/v1/guides/debugging/application', '/guides/debug/application'),
     ...i18nRedirect('/v1/guides/debugging/vs-code', '/guides/debug/vs-code'),
-    ...i18nRedirect('/v1/guides/debugging/clion', '/guides/debug/clion'),
+    ...i18nRedirect('/v1/guides/debugging/rustrover', '/guides/debug/rustrover'),
     // v1 /guides/development -> /guides/develop
     ...i18nRedirect(
       '/v1/guides/development/development-cycle',

packages/config-generator/build.ts

@@ -26,9 +26,16 @@ generatePageFromSchema(
   'Scope'
 );
 
-async function generatePageFromSchema(schemaFile: string, outputFile: string, pageTitle: string, sidebarOrder: number = 1) {
+async function generatePageFromSchema(
+  schemaFile: string,
+  outputFile: string,
+  pageTitle: string,
+  sidebarOrder: number = 1
+) {
   if (!existsSync(schemaFile)) {
-    throw Error(`Could not find the Tauri config schema ${schemaFile}. Is the Tauri submodule initialized?`);
+    throw Error(
+      `Could not find the Tauri config schema ${schemaFile}. Is the Tauri submodule initialized?`
+    );
   }
 
   let schema: JSONSchema7 = (await import(schemaFile)).default;

src/components/ShowSolution.astro

@@ -1,6 +1,6 @@
 ---
 let { text } = Astro.props;
-text = text ?? "Show solution";
+text = text ?? 'Show solution';
 ---
 
 <show-solution class="show-solution">
@@ -16,28 +16,22 @@ text = text ?? "Show solution";
     #button: HTMLButtonElement | null = null;
     constructor() {
       super();
-      this.#button = this.querySelector("button");
-      this.#button?.addEventListener("click", this.#toggle);
-      this.#contentDiv = this.querySelector("div");
+      this.#button = this.querySelector('button');
+      this.#button?.addEventListener('click', this.#toggle);
+      this.#contentDiv = this.querySelector('div');
     }
     #toggle = () => {
       if (this.#button)
-        if (this.#contentDiv?.classList.contains("hidden")) {
-          this.#contentDiv.classList.remove("hidden");
-          this.#button.innerText = this.#button.innerText.replace(
-            "Show",
-            "Hide"
-          );
+        if (this.#contentDiv?.classList.contains('hidden')) {
+          this.#contentDiv.classList.remove('hidden');
+          this.#button.innerText = this.#button.innerText.replace('Show', 'Hide');
         } else {
-          this.#contentDiv?.classList.add("hidden");
-          this.#button.innerText = this.#button.innerText.replace(
-            "Hide",
-            "Show"
-          );
+          this.#contentDiv?.classList.add('hidden');
+          this.#button.innerText = this.#button.innerText.replace('Hide', 'Show');
         }
     };
   }
-  customElements.define("show-solution", ShowSolution);
+  customElements.define('show-solution', ShowSolution);
 </script>
 
 <style>

src/content/docs/blog/tauri-1-3.mdx

@@ -74,10 +74,15 @@ Assuming a **fully trusted** web service on `https://trusted.example` it is now
 Shared domains **MUST NOT** be used for this in any circumstances. We do not limit access to paths or specific files. You can only scope with **trusted** _(sub)domains_[^6]. Another very risky catch is that developers must be sure that the domain ownership does not change over the lifetime of the application. Domain takeover could lead to compromised user devices.
 
 [^1]: _Inter-Process Communication_, in this instance the communication between the Tauri core and the frontend code run inside the webview.
+
 [^2]: _Security Impact_: What is the theoretical biggest impact of this threat combination? This highly depends on correct scoping of Tauri API endpoints and hardening of custom implemented Tauri commands.
+
 [^3]: _Exposure_: Describes the exposed scope items of this feature to either an user or adversary. It is possible to restrict exposure to only certain domains, windows or only to custom implemented commands.
+
 [^4]: _Adversary Capabilities_: Which kind of privileges has the adversary? Can range from tricking user into entering malicious input to code execution in the frontend via cross-site-scripting (which is the highest privilege for frontend code in our case). Common capabilities are described in the [OWASP documentation](https://owasp.org/www-community/attacks/).
+
 [^5]: _An application can be exploited if it parses user input for making an URL redirection decision, which is then not properly validated._ [Wikipedia Source](https://en.wikipedia.org/wiki/Open_redirect)
+
 [^6]: see the [Reqwest reference](https://docs.rs/reqwest/latest/reqwest/struct.Url.html#method.domain)
 
 ### Browser Arguments [#5799](https://github.com/tauri-apps/tauri/pull/5799)

src/content/docs/develop/Debug/index.mdx

@@ -3,13 +3,8 @@ title: Debug
 sidebar:
   label: Overview
   order: 10
-  badge:
-    text: WIP
-    variant: caution
 ---
 
-{/* TODO: REVISE COPY TO V2 */}
-
 import CommandTabs from '@components/CommandTabs.astro';
 
 With all the moving pieces in Tauri, you may run into a problem that requires debugging. There are many locations where error details are printed, and Tauri includes some tools to make the debugging process more straightforward.
@@ -22,9 +17,19 @@ One of the most useful tools in your toolkit for debugging is the ability to add
 
 ```rs frame=none
 fn main() {
-  // Tauri provided convenience function for whether you ran with `tauri dev`.
-  let is_dev: bool = tauri::dev();
-  // If debug assertions are enabled or not.
+  // Whether the current instance was started with `tauri dev` or not.
+  #[cfg(dev)]
+  {
+    // `tauri dev` only code
+  }
+  if cfg!(dev) {
+    // `tauri dev` only code
+  } else {
+    // `tauri build` only code
+  }
+  let is_dev: bool = tauri::is_dev();
+
+  // Whether debug assertions are enabled or not. This is true for `tauri dev` and `tauri build --debug`.
   #[cfg(debug_assertions)]
   {
     // Debug only code
@@ -37,6 +42,8 @@ fn main() {
 }
 ```
 
+{/* TODO: js version */}
+
 ## Rust Console
 
 The first place to look for errors is in the Rust Console. This is in the terminal where you ran, e.g., `tauri dev`. You can use the following code to print something to that console from within a Rust file:
@@ -51,10 +58,10 @@ Sometimes you may have an error in your Rust code, and the Rust compiler can giv
 RUST_BACKTRACE=1 tauri dev
 ```
 
-or like this on Windows:
+or like this on Windows (PowerShell):
 
-```shell frame=none
-set RUST_BACKTRACE=1
+```powershell frame=none
+$env:RUST_BACKTRACE=1
 tauri dev
 ```
 
@@ -125,7 +132,7 @@ The devtools API is private on macOS. Using private APIs on macOS prevents your
 
 :::
 
-To enable the devtools in production builds, you must enable the `devtools` Cargo feature in the `src-tauri/Cargo.toml` file:
+To enable the devtools in **production builds**, you must enable the `devtools` Cargo feature in the `src-tauri/Cargo.toml` file:
 
 ```toml
 [dependencies]

src/content/docs/develop/Debug/intellij.mdx

@@ -1,15 +1,10 @@
 ---
-title: Debug in RustRover
-sidebar:
-  badge:
-    text: WIP
-    variant: caution
+title: Debug in JetBrains IDEs
 ---
 
-{/* TODO: Update links and internal navigation */}
 {/* TODO: Add support to light/dark mode images */}
 
-In this guide, we'll be setting up JetBrains RustRover for debugging the [Core Process of your Tauri app](/concept/process-model/#the-core-process).
+In this guide, we'll be setting up JetBrains RustRover for debugging the [Core Process of your Tauri app](/concept/process-model/#the-core-process). It also mostly applies to IntelliJ and CLion.
 
 ## Setting up a Cargo project
 
@@ -24,7 +19,7 @@ Alternatively, you could create a top-level Cargo workspace manually by adding t
 members = ["src-tauri"]
 ```
 
-Before you proceed, make sure that your project is fully loaded. If the Cargo tool window shows all the modules and targets of the workspace, you’re good to go.
+Before you proceed, make sure that your project is fully loaded. If the Cargo tool window shows all the modules and targets of the workspace, you're good to go.
 
 ## Setting up Run Configurations
 

src/content/docs/develop/Debug/rustrover.mdx

@@ -1,14 +1,7 @@
 ---
 title: Debug in VS Code
-sidebar:
-  badge:
-    text: WIP
-    variant: caution
 ---
 
-{/* TODO: REVISE COPY TO V2 */}
-{/* TODO: Revise this change: Debugging in VS Code > Debug in VS Code */}
-
 This guide will walk you through setting up VS Code for debugging the [Core Process of your Tauri app](/concept/process-model/#the-core-process).
 
 ## Prerequisites

src/content/docs/develop/Debug/vscode.mdx

@@ -2,7 +2,7 @@
 title: GitHub
 sidebar:
   badge:
-    text: WIP
+    text: Stub
     variant: caution
 ---
 

src/content/docs/develop/Tests/Pipelines/github.mdx

@@ -2,7 +2,7 @@
 title: GitLab
 sidebar:
   badge:
-    text: WIP
+    text: Stub
     variant: caution
 ---