refactor: improve docs structure

docs/docs/getting-started/app-anatomy.md

@@ -1,13 +1,16 @@
 ---
-sidebar_position: 1
-title: Architecture
+sidebar_position: 2
+title: Anatomy of an app
 ---
 
-## Jan overall architecture
+## Jan Architecture
+
 ![Overall architecture](img/architecture-1.drawio.png)
+
 - Jan platform includes the following components:
+
   - Processes:
-    - UI process: 
+    - UI process:
       - This is Electron framework `renderer` component (Web technology equivalent)
       - Jan provides core platform UI that:
         - Allows App to `register()` function blueprint with name and arguments
@@ -20,3 +23,18 @@ title: Architecture
   - `@janhq/core` library that exposes Core API for App to reuse. Currently it only supports App `index.ts`
 
 - Vertically, there are `Platform Core` component and `App` component. Each of those includes UI and Node process that work in pair.
+
+##
+
+Platform has 3 events that are broadcast to installed Apps
+![Platform events](img/app-anatomy-4.drawio.png)
+
+- onLaunch()
+  ![Platform onLaunch()](img/app-anatomy-1.drawio.png)
+- onStart()
+  ![Platform onStart()](img/app-anatomy-2.drawio.png)
+- onDispose()
+  ![Platform onDispose()](img/app-anatomy-3.drawio.png)
+- At any given time, when there is new App installtion/ unintallation, the Platform restarts and trigger
+- When App is being used, here is how the information passes between Platform and Apps
+  ![Communication](img/app-anatomy-5.drawio.png)

docs/docs/getting-started/build-an-app.md

@@ -0,0 +1,6 @@
+---
+sidebar_position: 1
+title: Build an app
+---
+
+TODO: quickstart tutorial

docs/docs/getting-started/development-workflow.md

@@ -0,0 +1,6 @@
+---
+sidebar_position: 2
+title: Development workflow
+---
+
+todo

docs/docs/guides/concepts.md

@@ -1,5 +1,4 @@
 ---
-sidebar_position: 2
 title: Concepts
 ---
 

docs/docs/overview/app_anatomy.md

@@ -1,17 +0,0 @@
----
-sidebar_position: 3
-title: App Anatomy
----
-
-Platform has 3 events that are broadcast to installed Apps
-![Platform events](img/app-anatomy-4.drawio.png)
-
-- onLaunch()
-  ![Platform onLaunch()](img/app-anatomy-1.drawio.png)
-- onStart()
-  ![Platform onStart()](img/app-anatomy-2.drawio.png)
-- onDispose()
-  ![Platform onDispose()](img/app-anatomy-3.drawio.png)
-- At any given time, when there is new App installtion/ unintallation, the Platform restarts and trigger
-- When App is being used, here is how the information passes between Platform and Apps
-  ![Communication](img/app-anatomy-5.drawio.png)

docs/docs/tutorials/build-chat-app.md

@@ -1,6 +1,6 @@
 ---
 sidebar_position: 1
-title: How to Build a Jan App
+title: Building a chat app
 ---
 
 TODO

docs/docs/tutorials/build-rag-app.md

@@ -1,6 +1,6 @@
 ---
 sidebar_position: 2
-title: How to Build RAG App
+title: Building a RAG app
 ---
 
 TODO

docs/docs/tutorials/publish-jan-app.md

@@ -1,6 +1,6 @@
 ---
 sidebar_position: 3
-title: How to Publish a Jan App
+title: Publishing a Jan app
 ---
 
 TODO

docs/docusaurus.config.js

@@ -117,7 +117,7 @@ const config = {
           src: "img/logo.svg",
         },
         items: [
-          // Navbar Top
+          // Navbar left
           // {
           //   type: "docSidebar",
           //   sidebarId: "featuresSidebar",
@@ -135,7 +135,7 @@ const config = {
             type: "docSidebar",
             sidebarId: "guidesSidebar",
             position: "right",
-            label: "Guides",
+            label: "User Guides",
           },
           {
             type: "docSidebar",

docs/sidebars.js

@@ -49,13 +49,13 @@ const sidebars = {
   devSidebar: [
     {
       type: "category",
-      label: "Overview",
+      label: "Getting Started",
       collapsible: true,
       collapsed: false,
       items: [
         {
           type: "autogenerated",
-          dirName: "overview",
+          dirName: "getting-started",
         },
       ],
     },