Skip to content

Commit 5bffbcd

Browse files
author
abrulic
committed
updated readme.md
1 parent 29f8e31 commit 5bffbcd

2 files changed

Lines changed: 51 additions & 5 deletions

File tree

README.md

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -110,3 +110,54 @@ pnpm run dev
110110
6. After you see that everything works with the current content inside the `content` folder, remove those files and add your own
111111

112112
7. Happy coding!
113+
114+
## Features
115+
116+
### Versioned Documentation
117+
Generate per-tag version folders under `generated-docs/` (for example `v1.0.0/`) to publish and serve multiple doc versions.
118+
119+
**Example:**
120+
````bash
121+
pnpm run generate:docs --versions "^1.0.0"
122+
````
123+
124+
### Local Development Experience
125+
Run `pnpm run dev` to start the dev server and use the hot-reloading `.content-collections/` workflow for fast iteration. The dev server serves live content from `.content-collections/` (your working tree), so it usually shows only the current workspace docs.
126+
127+
**If you need to preview versioned outputs locally, you have two simple options:**
128+
129+
1. Run the generator and serve the `generated-docs/` output (example: `pnpm run generate:docs --branch main --versions="^1.0.0"`). This produces version folders under `generated-docs/` but disables hot-reloading because the site reads the generated output instead of the live `.content-collections/` folder.
130+
131+
2. Create a PR which produces both the versioned `generated-docs/` artifacts and the current snapshot — this is useful for previewing how versioned docs and the live snapshot appear together.
132+
133+
**Note:** When running the generator you must pass the default branch via `--branch` (for example `--branch main`) so the script can deterministically build the default-branch snapshot.
134+
135+
136+
### Automated Docs Generation
137+
The `pnpm run generate:docs` script automates:
138+
- Building the `generated-docs/` folder structure
139+
- Writing `app/utils/versions.ts` which the site consumes to show available versions
140+
141+
### CI/CD Ready
142+
Includes example GitHub Actions workflows to:
143+
- Build documentation
144+
- Pack the `generated-docs` artifact
145+
- Deploy preview or release sites
146+
147+
### Docker + Fly Deployment
148+
Includes `Dockerfile` and sample Fly workflows:
149+
- CI uploads the generated docs artifact
150+
- Deploy job unpacks it into the runner workspace
151+
- Image build includes `generated-docs/`
152+
153+
### Type-Safe and Tested
154+
Built-in quality tooling:
155+
- TypeScript (`tsc`) for type checking
156+
- Biome for linting
157+
- Vitest for testing
158+
159+
### Accessibility & Performance Focused
160+
Opinionated UI primitives and tooling optimized for:
161+
- Accessibility standards
162+
- Fast page loads
163+
- Great developer experience

scripts/generate-docs.ts

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -45,11 +45,6 @@ try {
4545
workspaceRelativePath = ""
4646
}
4747

48-
// biome-ignore lint/suspicious/noConsole: TODO remove this
49-
console.log(chalk.cyan(`Docs workspace root: ${workspaceRoot}`))
50-
// biome-ignore lint/suspicious/noConsole: TODO remove this
51-
console.log("outputDir:", outputDir)
52-
5348
const allTags = () => run("git tag --list").split("\n").filter(Boolean)
5449

5550
function resolveTagsFromSpec(spec: string) {

0 commit comments

Comments
 (0)