New docs

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

@@ -1,2 +1,46 @@
 # Build and run
 
+## Build
+
+Debug (default):
+
+```sh
+dcr build
+# or
+dcr build --debug
+```
+
+Release:
+
+```sh
+dcr build --release
+```
+
+## Run
+
+```sh
+dcr run
+# or
+dcr run --release
+```
+
+`dcr run` first builds, then launches the produced binary.
+
+## Clean artifacts
+
+```sh
+dcr clean
+```
+
+Profile-only cleanup:
+
+```sh
+dcr clean --debug
+dcr clean --release
+```
+
+## Notes
+
+- `run` is unavailable for `build.kind = "staticlib"`.
+- Build profile flag is parsed from the first command argument.
+- Unknown profile flags produce an error.

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

@@ -1,2 +1,41 @@
 # 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/installation.md

@@ -1,2 +1,56 @@
 # 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/project-structure.md

@@ -1,2 +1,39 @@
 # 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/<profile>/obj/`: cached object files for incremental rebuild.
+- `target/<profile>/deps/`: synchronized copies of path dependencies.
+- `target/<profile>/<name>` (or `.exe` on Windows): output for `kind = "bin"`.
+- `target/<profile>/lib<name>.a` (or `<name>.lib` on Windows): output for `kind = "staticlib"`.
+
+If `build.target` is set, the final artifact is written to that custom directory, while object cache still stays in `target/<profile>/obj`.