add installation instructions in a new installation.md file

Author: andrew

content/_index.md

@@ -15,20 +15,30 @@ layout: hextra-home
 {{< /hextra/hero-subtitle >}}
 </div>
 
-<div class="hx:mb-6">
+<div class="hx:mb-6 hx:flex hx:gap-4">
 {{< hextra/hero-button text="Get Started" link="docs/getting-started" >}}
+<a href="docs/installation" class="not-prose hx:font-medium hx:cursor-pointer hx:px-6 hx:py-3 hx:rounded-full hx:text-center hx:inline-block hx:border hx:border-gray-300 hx:dark:border-neutral-700 hx:hover:bg-gray-100 hx:dark:hover:bg-neutral-800 hx:transition-all hx:ease-in hx:duration-200">Installation</a>
 </div>
 
 <div class="hx:mt-6"></div>
 
 Your lockfile shows what dependencies you have, but not how you got here. Running `git log Gemfile.lock` produces noise that no one reads. git-pkgs walks through your git history and builds a SQLite database so you can ask: when did we add this? who added it? what changed between releases? has anyone touched this in the last year?
 
 ```bash
-git pkgs init           # index your history (one-time)
+git pkgs init           # analyze history (one-time)
+git pkgs list           # show current dependencies
+git pkgs stats          # see overview
 git pkgs blame          # who added each dependency
-git pkgs history rails  # when was this package changed?
-git pkgs why express    # why was this added?
-git pkgs diff main..feature  # what changed between branches?
+git pkgs history        # all dependency changes over time
+git pkgs history rails  # track a specific package
+git pkgs why rails      # why was this added?
+git pkgs diff --from=HEAD~10  # what changed recently?
+git pkgs diff --from=main --to=feature  # compare branches
+git pkgs vulns          # scan for known CVEs
+git pkgs vulns blame    # who introduced each vulnerability
+git pkgs outdated       # find packages with newer versions
+git pkgs update         # update all dependencies
+git pkgs add lodash     # add a package
 ```
 
 The database lives in `.git/pkgs.sqlite3` and stays current through git hooks. Core commands work entirely offline with no network access.

content/docs/getting-started.md

@@ -3,22 +3,7 @@ title: Getting Started
 weight: 10
 ---
 
-## Installation
-
-Install with Homebrew:
-
-```bash
-brew tap git-pkgs/git-pkgs
-brew install git-pkgs
-```
-
-Or download a binary from the [releases page](https://github.com/git-pkgs/git-pkgs/releases).
-
-Or build from source:
-
-```bash
-go install github.com/git-pkgs/git-pkgs@latest
-```
+See [Installation](/docs/installation) for setup instructions.
 
 ## Quick start
 

content/docs/installation.md

@@ -0,0 +1,55 @@
+---
+title: Installation
+weight: 5
+---
+
+## Homebrew
+
+```bash
+brew tap git-pkgs/git-pkgs
+brew install git-pkgs
+```
+
+## Download binary
+
+Download a prebuilt binary from the [releases page](https://github.com/git-pkgs/git-pkgs/releases).
+
+Binaries are available for:
+- macOS (Intel and Apple Silicon)
+- Linux (amd64 and arm64)
+- Windows (amd64)
+
+## Build from source
+
+Requires Go 1.22 or later.
+
+```bash
+go install github.com/git-pkgs/git-pkgs@latest
+```
+
+## Verify installation
+
+```bash
+git pkgs version
+```
+
+## Shell completions
+
+Generate completions for your shell:
+
+```bash
+git pkgs completion bash > /etc/bash_completion.d/git-pkgs
+git pkgs completion zsh > "${fpath[1]}/_git-pkgs"
+git pkgs completion fish > ~/.config/fish/completions/git-pkgs.fish
+```
+
+## Next steps
+
+Initialize git-pkgs in a repository:
+
+```bash
+cd your-repo
+git pkgs init
+```
+
+See [Getting Started](/docs/getting-started) for a walkthrough of the main commands.