fix: nav_order conflict, profile count, Docker Compose prereq, inert wording

Author: ankurs

Index.md

@@ -40,7 +40,7 @@ A Kubernetes-native Go microservice framework for building production-grade gRPC
 | **Container-aware Runtime** | Auto-tunes GOMAXPROCS to match container CPU limits via [automaxprocs] |
 | **Request Validation** | [Protovalidate] annotations enforced automatically on both gRPC and HTTP requests — define validation rules in your proto, get `InvalidArgument` errors for free |
 | **CI/CD Pipelines** | Ready-to-use [GitHub Actions] and [GitLab CI] workflows for build, test, lint, coverage, and benchmarks |
-| **Local Dev Stack** | Docker Compose with 20+ per-service profiles (databases, caches, brokers, AWS/GCP emulators) — `make local-stack` starts your selection, `make local-stack-obs` adds [Prometheus], [Grafana], [Jaeger] |
+| **Local Dev Stack** | Docker Compose with 19 services across 18 profiles + `obs` group (databases, caches, brokers, AWS/GCP emulators) — `make local-stack` starts your selection, `make local-stack-obs` adds [Prometheus], [Grafana], [Jaeger] |
 | **Application Metrics** | Interface-based metrics package with [promauto] registration — counter and histogram examples wired into handlers |
 | **Load Testing** | [ghz] gRPC load test config with `make loadtest` — results visible in Grafana dashboard when running with `make local-stack-obs` |
 

howto/local-dev.md

@@ -2,7 +2,7 @@
 layout: default
 title: "Local Development"
 parent: "How To"
-nav_order: 16
+nav_order: 17
 description: "Docker Compose local dev stack with per-service profiles for databases, caches, message brokers, AWS/GCP emulators, and observability"
 ---
 ## Table of contents
@@ -13,7 +13,7 @@ description: "Docker Compose local dev stack with per-service profiles for datab
 
 ## Overview
 
-Projects generated from the [ColdBrew cookiecutter] include a `docker-compose.local.yml` with 20 infrastructure services, each behind its own [Docker Compose profile](https://docs.docker.com/compose/how-tos/profiles/). You select which services to start — only those containers run.
+Projects generated from the [ColdBrew cookiecutter] include a `docker-compose.local.yml` with 19 infrastructure services across 18 individual profiles plus one group profile (`obs` for Prometheus + Grafana + Jaeger). You select which profiles to start — only those containers run.
 
 Your app runs natively via `make run` (fast builds, no Docker overhead). The compose stack provides only infrastructure dependencies.
 
@@ -154,7 +154,7 @@ make local-stack PROFILES="postgres mongodb nats"
 
 ### Disabling docker-compose entirely
 
-During project generation, set `include_docker_compose` to `n`. The post-gen hook removes `docker-compose.local.yml` and `deploy/`. Makefile targets remain but are inert (docker-compose errors clearly when the file is missing).
+During project generation, set `include_docker_compose` to `n`. The post-gen hook removes `docker-compose.local.yml` and `deploy/`. Makefile targets remain but will error with "no configuration file provided" if invoked — this is expected and serves as a clear signal to remove or ignore them.
 
 ## Grafana Dashboard
 

quickstart.md

@@ -23,6 +23,7 @@ Before you begin, install:
 - **[Go 1.25+](https://go.dev/dl/)** — `go version` should show 1.25 or later
 - **[cookiecutter](https://cookiecutter.readthedocs.io/)** — `brew install cookiecutter` or `pip install cookiecutter`
 - **[buf](https://buf.build/docs/installation)** — for protobuf code generation
+- **[Docker Compose](https://docs.docker.com/compose/install/)** — for the local dev stack (Step 7). Works with Docker Desktop, Colima, or any OCI runtime
 
 ## Step 1: Generate Your Project
 
@@ -314,7 +315,7 @@ make local-exec SVC=postgres CMD="psql -U postgres"  # Exec into any service
 Open [http://localhost:3000](http://localhost:3000) (Grafana, admin/admin) and [http://localhost:16686](http://localhost:16686) (Jaeger) to see metrics and traces in real-time.
 
 {: .note }
-The local stack is infra-only — your app runs natively via `make run` for fast iteration. Use `make local-stack-down` to stop everything. See the [Local Development How-To](/howto/local-dev/) for all 20 profiles, connection strings, Grafana dashboard customization, and troubleshooting.
+The local stack is infra-only — your app runs natively via `make run` for fast iteration. Use `make local-stack-down` to stop everything. See the [Local Development How-To](/howto/local-dev/) for all available profiles, connection strings, Grafana dashboard customization, and troubleshooting.
 
 ## Step 8: Run in Docker