Refactor and improve documentation, add examples

docs/quickstart.md

@@ -0,0 +1,128 @@
+# Quickstart
+
+## Installation
+
+### From Source (recommended for now)
+
+```bash
+git clone https://github.com/Use-Tusk/fence
+cd fence
+go build -o fence ./cmd/fence
+sudo mv fence /usr/local/bin/
+```
+
+### Using Go Install
+
+```bash
+go install github.com/Use-Tusk/fence/cmd/fence@latest
+```
+
+### Linux Dependencies
+
+On Linux, you also need:
+
+```bash
+# Ubuntu/Debian
+sudo apt install bubblewrap socat
+
+# Fedora
+sudo dnf install bubblewrap socat
+
+# Arch
+sudo pacman -S bubblewrap socat
+```
+
+## Verify Installation
+
+```bash
+fence --version
+```
+
+## Your First Sandboxed Command
+
+By default, fence blocks all network access:
+
+```bash
+# This will fail - network is blocked
+fence curl https://example.com
+```
+
+You should see something like:
+
+```text
+curl: (56) CONNECT tunnel failed, response 403
+```
+
+## Allow Specific Domains
+
+Create a config file at `~/.fence.json`:
+
+```json
+{
+  "network": {
+    "allowedDomains": ["example.com"]
+  }
+}
+```
+
+Now try again:
+
+```bash
+fence curl https://example.com
+```
+
+This time it succeeds!
+
+## Debug Mode
+
+Use `-d` to see what's happening under the hood:
+
+```bash
+fence -d curl https://example.com
+```
+
+This shows:
+
+- The sandbox command being run
+- Proxy activity (allowed/blocked requests)
+- Filter rule matches
+
+## Monitor Mode
+
+Use `-m` to see only violations and blocked requests:
+
+```bash
+fence -m npm install
+```
+
+This is useful for:
+
+- Auditing what a command tries to access
+- Debugging why something isn't working
+- Understanding a package's network behavior
+
+## Running Shell Commands
+
+Use `-c` to run compound commands:
+
+```bash
+fence -c "echo hello && ls -la"
+```
+
+## Expose Ports for Servers
+
+If you're running a server that needs to accept connections:
+
+```bash
+fence -p 3000 -c "npm run dev"
+```
+
+This allows external connections to port 3000 while keeping outbound network restricted.
+
+## Next steps
+
+- Read **[Why Fence](why-fence.md)** to understand when fence is a good fit (and when it isn't).
+- Learn the mental model in **[Concepts](concepts.md)**.
+- Use **[Troubleshooting](troubleshooting.md)** if something is blocked unexpectedly.
+- Start from copy/paste configs in **[`docs/templates/`](templates/README.md)**.
+- Follow workflow-specific guides in **[Recipes](recipes/README.md)** (npm/pip/git/CI).