Work in progress

Signed-off-by: S. Julliand <sebjulliand@gmail.com>

Author: sebjulliand

.astro/types.d.ts

@@ -391,5 +391,5 @@ declare module 'astro:content' {
 
 	type AnyEntryMap = ContentEntryMap & DataEntryMap;
 
-	export type ContentConfig = typeof import("../src/content/config.js");
+	export type ContentConfig = typeof import("./../src/content/config.js");
 }

src/content/docs/developing/debug/debug10.png

@@ -55,13 +55,13 @@ To debug a program from the Object Browser, right-click on the program object an
 
 ## General requirements
 
-* PTFs
-* Certificates setup on the server
-   * created in `/QIBM/UserData/IBMiDebugService/certs` by default
-* IBM i Debug extension
-   * installed into Visual Studio Code
-* Local client certificate
-   * can be imported with the 'Import local certificate' command
+* PTFs (see below)
+* IBM i Debug extension ([marketplace](https://marketplace.visualstudio.com/items?itemName=IBM.ibmidebug))
+  * installed into Visual Studio Code
+* Debug Service Certificates setup
+  * created in `/QIBM/UserData/IBMiDebugService/certs` by default
+  * Debug Service certificate `debug_service.pfx`
+  * Debug Service client certificate `debug_service.crt`
 
 ## Required PTFs
 
@@ -92,16 +92,47 @@ After you have installed the PTFs, the connection inside of Visual Studio Code w
 ## Configuring & starting the service
 
 <CardGrid>
-
 <Card>
+After connecting to a system in Code for IBM i, you can hover over the connection in the bottom status bar to check the Debugger version and status. The status will be `on` if both the Debug Server and Debug Service are running.
+</Card>
+<Card>
+![](./debug6.png)
+</Card>
+</CardGrid>
+<CardGrid>
+<Card>
+Clicking on the Debugger status will take you to the IBM i Debugger view. This view shows the status of the Debug Server and the Debug Service. It also allows to start/stop the Debug Server and manage the Debug Service.
+</Card>
+<Card>
+![](./debug7.png)
+</Card>
+</CardGrid>
 
-After connecting to a system in Code for IBM i, if the PTFs are installed but the service is not configured (i.e. the certificates don't exist) you will see a notice asking if you'd like to open the Walkthrough to configure the Debug Service. Clicking the button will open the Walkthrough.
-
-</Card><Card>
+### Start/stop the Server and Service
+<CardGrid>
+<Card>
+The start/stop/restart actions are located on the right of each status. Running one of these actions will refresh the statuses once it's done.
+</Card>
+<Card>
+![](./debug8.png)
+![](./debug9.png)
+</Card>
+</CardGrid>
 
-![](./setup1.png)
+<Aside type="tip">
+   Starting and stopping the Debug Server and Service requires the *ALLOBJ special authority.
+</Aside>
 
-</Card></CardGrid>
+### Managing the Debug Service
+<CardGrid>
+<Card>
+If the Debug Service is not correctly configured, a warning sign will appear next to it. Expanding the Debug Service node will show the cause of the issue.
+</Card>
+<Card>
+![](./debug10.png)
+![](./debug11.png)
+</Card>
+</CardGrid>
 
 <Aside type="tip">
    There only needs to be one instance of the Debug Service running and therefore the certificates should only be generated once. All developers share the Debug Service.