docs(dev): integrate more of the old documentation

Author: eliandoran

docs/Developer Guide/!!!meta.json

@@ -2,7 +2,7 @@
 The main workflow of the CI:
 
 *   Builds the Docker image and publishes in the GitHub Docker registry.
-*   Builds using a portion of the [delivery script](../../Build%20deliveries%20locally.md) artifacts for the following platforms:
+*   Builds using a portion of the [delivery script](../../Building/Build%20deliveries%20locally.md) artifacts for the following platforms:
     *   Windows `x86_64` as .zip file
     *   Windows `x86_64` installer (using Squirrel)
     *   macOS `x86_64` and `aarch64`.

docs/Developer Guide/Developer Guide/Old documentation/Building and deployment/CI/1_Main_image.png renamed to docs/Developer Guide/Developer Guide/Architecture/CI/1_Main_image.png

@@ -21,7 +21,7 @@ These are stored in `images`:
 
 ## App icons
 
-<table><thead><tr><th>Name</th><th>Resolution</th><th>Description</th></tr></thead><tbody><tr><td><code>ios/apple-touch-icon.png</code></td><td>180x180</td><td>Used as <code>apple-touch-icon</code>, but only in <code>login.ejs</code> and <code>set_password.ejs</code> for some reason.</td></tr><tr><td><code>mac/icon.icns</code></td><td>512x512</td><td>Provided as <code>--icon</code> to <code>electron-packager</code> for <code>mac-arm64</code> and <code>mac-x64</code> <a href="../Old%20documentation/Build%20deliveries%20locally.md">builds</a>.</td></tr><tr><td><code>png/128x128.png</code></td><td>128x128</td><td>Used in <code>linux-x64</code> <a href="../Old%20documentation/Build%20deliveries%20locally.md">build</a>, to provide an <code>icon.png</code>.</td></tr><tr><td><code>png/256x256-dev.png</code></td><td>256x256</td><td>Used by the Electron window icon, if in dev mode.</td></tr><tr><td><code>png/256x256.png</code></td><td>Used by the Electron window icon, if not in dev mode.</td></tr><tr><td><code>win/icon.ico</code></td><td><ul><li>ICO 16x16</li><li>ICO 32x32</li><li>ICO 48x48</li><li>ICO 64x64</li><li>ICO 128x128</li><li>PNG 256x256</li></ul></td><td><ul><li>Used by the <code>win-x64</code> <a href="../Old%20documentation/Build%20deliveries%20locally.md">build</a>.</li><li>Used by Squirrel Windows installer for: setup icon, app icon, control panel icon</li><li>Used as the favicon.</li></ul></td></tr><tr><td><code>win/setup-banner.gif</code></td><td>640x480</td><td>Used by the Squirrel Windows installer during the installation process. Has only one frame.</td></tr></tbody></table>
+<table><thead><tr><th>Name</th><th>Resolution</th><th>Description</th></tr></thead><tbody><tr><td><code>ios/apple-touch-icon.png</code></td><td>180x180</td><td>Used as <code>apple-touch-icon</code>, but only in <code>login.ejs</code> and <code>set_password.ejs</code> for some reason.</td></tr><tr><td><code>mac/icon.icns</code></td><td>512x512</td><td>Provided as <code>--icon</code> to <code>electron-packager</code> for <code>mac-arm64</code> and <code>mac-x64</code> <a href="../Building/Build%20deliveries%20locally.md">builds</a>.</td></tr><tr><td><code>png/128x128.png</code></td><td>128x128</td><td>Used in <code>linux-x64</code> <a href="../Building/Build%20deliveries%20locally.md">build</a>, to provide an <code>icon.png</code>.</td></tr><tr><td><code>png/256x256-dev.png</code></td><td>256x256</td><td>Used by the Electron window icon, if in dev mode.</td></tr><tr><td><code>png/256x256.png</code></td><td>Used by the Electron window icon, if not in dev mode.</td></tr><tr><td><code>win/icon.ico</code></td><td><ul><li>ICO 16x16</li><li>ICO 32x32</li><li>ICO 48x48</li><li>ICO 64x64</li><li>ICO 128x128</li><li>PNG 256x256</li></ul></td><td><ul><li>Used by the <code>win-x64</code> <a href="../Building/Build%20deliveries%20locally.md">build</a>.</li><li>Used by Squirrel Windows installer for: setup icon, app icon, control panel icon</li><li>Used as the favicon.</li></ul></td></tr><tr><td><code>win/setup-banner.gif</code></td><td>640x480</td><td>Used by the Squirrel Windows installer during the installation process. Has only one frame.</td></tr></tbody></table>
 
 ## Additional locations where the branding is used
 

docs/Developer Guide/Developer Guide/Old documentation/Building and deployment/CI/Main.md renamed to docs/Developer Guide/Developer Guide/Architecture/CI/Main.md

@@ -0,0 +1,34 @@
+# Build deliveries locally
+## Building the desktop
+
+Go to `apps/desktop`, and:
+
+*   To generate the packages, run `pnpm electron-forge:make`.
+*   To only build the Flatpak, run `pnpm electron-forge:make-flatpak`.
+*   To only build without packaging it, run `pnpm electron-forge:package`.
+
+## Building the server
+
+Go to `apps/server` and run `pnpm package` to run the build script. The built artifacts will appear in `apps/server/dist`, whereas the packaged build will be available in `apps/server/out`.
+
+## On NixOS
+
+Under NixOS the following `nix-shell` is needed:
+
+```
+nix-shell -p jq
+```
+
+For Linux builds:
+
+```
+nix-shell -p jq fakeroot dpkg
+```
+
+To test the Linux builds, use `steam-run`:
+
+```javascript
+$ NIXPKGS_ALLOW_UNFREE=1 nix-shell -p steam-run
+[nix-shell] cd dist/trilium-linux-x64
+[nix-shell] steam-run ./trilium
+```

docs/Developer Guide/Developer Guide/Old documentation/Building and deployment/CI/Main_image.png renamed to docs/Developer Guide/Developer Guide/Architecture/CI/Main_image.png

@@ -0,0 +1,17 @@
+# Documentation
+## Automation
+
+The documentation is built via `apps/build-docs`:
+
+1.  The output directory is cleared.
+2.  The User Guide and the Developer Guide are built.
+    1.  The documentation from the repo is archived and imported into an in-memory instance.
+    2.  The documentation is exported using the shared theme.
+3.  The API docs (internal and ETAPI) are statically rendered via Redocly.
+4.  The script API is generated via `typedoc`
+
+The `deploy-docs` workflow triggers the documentation build and uploads it to CloudFlare Pages.
+
+## Building locally
+
+In the Git root, run `pnpm docs:build`. The built documentation will be available in `site` at Git root.

docs/Developer Guide/Developer Guide/Architecture/Icons.md

@@ -0,0 +1,33 @@
+# Running a development build
+First, follow the <a class="reference-link" href="../Environment%20Setup.md">Environment Setup</a>.
+
+## Client
+
+The client is not meant to be run by itself, despite being described as an app. See the documentation on the server instead.
+
+## Server
+
+*   To run the server in development mode, run `server:start`. The dev port is `8080`.
+*   To run the server in production mode (with its own copy of the assets), run `server:start-prod`.
+*   To build for Docker, see <a class="reference-link" href="Docker.md">Docker</a>.
+
+To run with a custom port, change the `TRILIUM_PORT` environment variable from the `package.json`.
+
+## Desktop
+
+*   To run in development mode, use `pnpm desktop:start`.
+*   To run in production mode, use `pnpm desktop:start-prod`.
+
+## Safe mode
+
+Safe mode is off by default, to enable it temporarily on a Unix shell, prepend the environment variable setting:
+
+```
+pnpm cross-env TRILIUM_SAFE_MODE=1 pnpm server:start
+```
+
+## Running on NixOS
+
+When doing development, the Electron binary retrieved from NPM is not going to be compatible with NixOS, resulting in errors when trying to run it. However Trilium handles it automatically when running `pnpm desktop:start`.
+
+If there's no `electron` the system path it will attempt to use `nix-shell` to obtain it.