docs: rewrite documentation.

add: Nix and Snapcraft support.

docs/getting-started/build-and-run.md

@@ -1,57 +0,0 @@
-# Build and run
-
-## Build
-
-Debug (default):
-
-```sh
-dcr build
-# or
-dcr build --debug
-dcr build --target linux --debug
-dcr build --debug --clean
-```
-
-Release:
-
-```sh
-dcr build --release
-dcr build --target windows --release
-```
-
-## Run
-
-```sh
-dcr run
-# or
-dcr run --target macos
-dcr run --release
-dcr run --target linux --release
-dcr run --release --force
-```
-
-`dcr run` first builds, then launches the produced binary.
-
-## Clean artifacts
-
-```sh
-dcr clean
-```
-
-Profile-only cleanup:
-
-```sh
-dcr clean --debug
-dcr clean --release
-dcr clean --all
-dcr clean --release --all
-```
-
-## Notes
-
-- `run` is unavailable for `build.kind = "staticlib"`, `build.kind = "sharedlib"`, `build.kind = "efi"`, and `build.kind = "elf"`.
-- Build profile flag (`--debug` / `--release`) can be passed in any argument position.
-- Unknown profile flags produce an error.
-- In workspace root, `clean --all` cleans all member projects.
-- `--target` builds/runs for specified target (short names: `linux`, `macos`, `windows`).
-- `--clean` for `build`/`run` removes `target/<target>/<profile>` and paths from `build.clean`.

docs/getting-started/create-your-first-project.md

@@ -1,41 +0,0 @@
-# Create your first project
-
-## Create in a new folder
-
-```sh
-dcr new hello
-cd hello
-```
-
-This creates:
-
-```text
-hello/
-- dcr.toml
-- src/
-- - main.c
-```
-
-## Or initialize current folder
-
-```sh
-mkdir hello
-cd hello
-dcr init
-```
-
-`dcr init` requires the current directory to be empty.
-
-## Next steps
-
-Build and run:
-
-```sh
-dcr run
-```
-
-Release build/run:
-
-```sh
-dcr run --release
-```

docs/getting-started/first-steps.mdx

@@ -0,0 +1,70 @@
+---
+sidebar_label: First steps
+---
+
+# First Steps
+
+## Create a project
+
+```bash
+dcr new my-app
+cd my-app
+```
+
+Structure:
+
+```
+my-app/
+├── dcr.toml
+└── src/
+    └── main.c
+```
+
+`dcr.toml`:
+```toml
+[package]
+name = "my-app"
+version = "0.1.0"
+type = "none"
+
+[build]
+language = "c"
+standard = "c11"
+compiler = "clang"
+kind = "bin"
+```
+
+## Build
+
+```bash
+dcr build
+```
+
+Output — `target/<triple>/debug/my-app` (Linux) or `target/debug/my-app.exe` (Windows).
+
+Build profiles:
+```bash
+dcr build --release       # release build
+dcr build --debug         # debug (default)
+```
+
+## Run
+
+```bash
+dcr run
+```
+
+Builds (if needed) and runs the binary.
+
+## First test
+
+```bash
+dcr test --init      # create test template
+dcr test             # run tests
+```
+
+## Formatting
+
+```bash
+dcr fmt              # clang-format with .clang-format
+```

docs/getting-started/installation.md

@@ -1,56 +0,0 @@
-# Installation
-
-## Option 1: Install via script
-
-### Linux/macOS
-
-```sh
-curl -fsSL https://dcr.dexoron.su/install.sh | bash
-```
-
-Alternative with `wget`:
-
-```sh
-wget -qO- https://dcr.dexoron.su/install.sh | bash
-```
-
-### Windows (PowerShell)
-
-```powershell
-powershell -ExecutionPolicy ByPass -c "irm https://dcr.dexoron.su/install.ps1 | iex"
-```
-
-## Option 2: Build from source
-
-```sh
-git clone https://github.com/dexoron/dcr.git
-cd dcr
-cargo build --release
-mkdir -p ~/.local/bin
-ln -sf "$PWD/target/release/dcr" ~/.local/bin/dcr
-```
-
-## Option 3: Arch Linux (AUR)
-
-```sh
-yay -S dcr
-```
-
-(You can also use `paru` or other AUR helpers.)
-
-## Verify installation
-
-```sh
-dcr --version
-```
-
-Expected format:
-
-```text
-dcr <version> (<target>)
-```
-
-## Update policy
-
-- If DCR was installed from GitHub releases, scripts, or manual build: use `dcr --update`.
-- If DCR is managed by `pacman/AUR`: update via package manager. On Linux, `dcr --update` detects pacman-owned binaries and prints a package-manager hint.

docs/getting-started/installation.mdx

@@ -0,0 +1,93 @@
+---
+sidebar_label: Installation
+---
+
+# Installation
+
+## Linux (Dexoron Packages)
+
+Configure your package manager at https://dcr.dexoron.su and install:
+
+**Arch Linux**
+```sh
+sudo pacman -Sy dcr
+```
+
+**Debian/Ubuntu**
+```sh
+sudo apt update && sudo apt install dcr
+```
+
+**Fedora/RHEL**
+```sh
+sudo dnf install dcr
+```
+
+## Arch Linux (AUR)
+
+```sh
+yay -S dcr
+```
+
+## macOS / Linux (Homebrew)
+
+```sh
+brew tap dexoron/dexoron
+brew install dcr
+```
+
+## Nix (flake)
+
+```sh
+nix run github:dexoron/dcr
+# or install to profile:
+nix profile install github:dexoron/dcr
+```
+
+## Cargo (crates.io)
+
+```sh
+cargo install dcr
+```
+
+## Linux / macOS (script)
+
+```sh
+curl -fsSL https://dcr.dexoron.su/install.sh | bash
+```
+
+## BSD (script)
+
+```sh
+curl -fsSL https://dcr.dexoron.su/install_bsd.sh | bash
+```
+
+## Windows (PowerShell)
+
+```powershell
+irm https://dcr.dexoron.su/install.ps1 | iex
+```
+
+## From source
+
+```sh
+git clone https://github.com/dexoron/dcr.git
+cd dcr && cargo build --release
+ln -sf "$PWD/target/release/dcr" ~/.local/bin/dcr
+```
+
+## Post-install
+
+Verify the installation:
+
+```bash
+dcr --version
+```
+
+To use the registry, create `~/.dcr/config.toml`:
+
+```toml
+[[registry]]
+name = "default"
+url = "https://index.dcr.pm"
+```

docs/getting-started/project-structure.md

@@ -1,40 +0,0 @@
-# Project structure
-
-## Minimal project
-
-```text
-project/
-- dcr.toml
-- src/
-- - main.c
-```
-
-## Typical generated/optional files
-
-```text
-project/
-- dcr.toml
-- dcr.lock
-- src/
-- - ... source files ...
-- target/
-- - debug/
-- - - obj/
-- - - deps/
-- - release/
-- - - obj/
-- - - deps/
-```
-
-## Meaning
-
-- `dcr.toml`: main project configuration.
-- `dcr.lock`: generated lock file for resolved path dependencies.
-- `src/`: recursively scanned source directory.
-- `target/<target>/<profile>/obj/`: cached object files for incremental rebuild (where `<target>` is `native` or target triple).
-- `target/<target>/<profile>/deps/`: synchronized copies of path dependencies.
-- `target/<target>/<profile>/<name>` (or `.exe` on Windows): output for `kind = "bin"`.
-- `target/<target>/<profile>/lib<name>.a` (or `<name>.lib` on Windows): output for `kind = "staticlib"`.
-- `target/<target>/<profile>/lib<name>.so` (or `.dylib` on macOS, `<name>.dll` on Windows): output for `kind = "sharedlib"`.
-
-If `build.out_dir` is set, the final artifact is written to that custom directory, while object cache still stays in `target/<target>/<profile>/obj`.