Adjust documentation to include template instructions

Author: bcb

README.md

@@ -24,19 +24,21 @@ flowchart TD
 
 ## 🚀 Quick Start
 
-1. **Clone SuperStack and start the stack:**
+1. Click [Use this
+   template](https://github.com/explodinglabs/superstack/generate) and create a
+   new repository on Github.
+
+2. Clone your new repository and start SuperStack:
 
 ```sh
-git clone https://github.com/explodinglabs/superstack myapp
+git clone https://github.com/yourname/myapp.git
 cd myapp
 cp example.env .env
 docker compose up -d
 ```
 
-2. **Explore your API**
-
-Open [http://localhost:8000/openapi/](http://localhost:8000/openapi/) in your
-browser to view and test endpoints using Swagger UI.
+Open [http://localhost:8000/openapi/](http://localhost:8000/openapi/) to view
+your Swagger UI.
 
 ## 📚 Full Documentation
 

docs/gettingstarted.md

@@ -3,48 +3,39 @@
 SuperStack uses Docker, so make sure [Docker is
 installed](https://docs.docker.com/get-docker/) before you begin.
 
-## 1. Clone SuperStack
+## 1. Get SuperStack
+
+### Option 1: Use the Template (Recommended)
+
+The easiest way to get started:
+
+1. Click [Use this
+   template](https://github.com/explodinglabs/superstack/generate) on GitHub.
+2. Create a new repository (e.g. `myapp`) from the template.
+3. Clone it to your machine:
 
 ```sh
-git clone https://github.com/explodinglabs/superstack myapp
+git clone https://github.com/yourname/myapp.git
 cd myapp
 ```
 
-<details>
-<summary>
-  Recommended: Change the clone to point to your own hosted repository.
-</summary>
+### Option 2: Clone and Track Upstream (Advanced)
 
-Rename "origin" to "upstream":
+If you want to keep SuperStack’s Git history and pull upstream changes later:
 
 ```sh
+git clone https://github.com/explodinglabs/superstack.git myapp
+cd myapp
 git remote rename origin upstream
+git remote add origin https://github.com/yourname/myapp
 ```
 
-This way you can still upgrade to a more recent SuperStack with:
+You can now pull upstream changes with:
 
 ```sh
 git pull upstream main
 ```
 
-Add your own code repository:
-
-```sh
-git remote add origin https://github.com/yourname/myapp
-```
-
-Now you can pull/push to your own repo as normal:
-
-<h3>Why not just fork SuperStack?</h3>
-
-Because you can't make a fork private.
-
-<h3>Why not make SuperStack a template repo?</h3>
-
-Because then you can't pull from upstream SuperStack.
-
-</details>
-
 ## 2. Configure Environment Variables
 
 Copy the example file:
@@ -53,8 +44,8 @@ Copy the example file:
 cp example.env .env
 ```
 
-> ⚠️ The `.env` file is for local development only, don't write secrets to a
-> file on other environments.
+> ⚠️ **The .env file is for local development only.** Don't store real secrets
+> in production — use CI/CD environment variables or a secrets manager.
 
 ## 3. Start the Stack
 

docs/index.md

@@ -25,11 +25,6 @@ Caddy), making it easy to develop locally or deploy remotely.
 
 ---
 
-## 📚 Documentation
-
-- [Getting Started](gettingstarted.md)
-- [Migrations](migrations.md)
-- [Postgres Extensions](extensions.md)
-- [Authentication](authentication.md)
-- [Psql](psql.md)
-- [Deploying to Remote Environments](deploying.md)
+## 📚 Get Started
+
+👉 [Continue to Getting Started](gettingstarted.md)

docs/psql.md

@@ -1,28 +1,21 @@
 # 🖥️ Using psql
 
-`psql` is the command-line tool for interacting with your PostgreSQL
-database. SuperStack makes it easy to run psql inside the container using a
-helper script.
+`psql` is the command-line tool for interacting with your PostgreSQL database.
+SuperStack makes it easy to run psql inside the container using a helper
+script.
 
 ## 📟 Open a psql Shell
 
 To connect interactively:
 
 ```sh
-bin/postgres psql
-```
-
-Example output:
-
-```
+$ bin/postgres psql
 psql (17.5 (Debian 17.5-1.pgdg120+1))
 Type "help" for help.
 
 app=#
 ```
 
-## 🔹 Run Inline SQL Commands
-
 You can also run SQL directly from the command line:
 
 ```