rootiest/fish-config

Files

T

History

rootiest ab030d7ec0

Generate documentation / build-docs (push) Successful in 3m14s

Details

Offline docs drift reminder / remind (push) Successful in 16s

Details

docs: update site title and canonical URL

Rename the Starlight site to "Rootiest Fish Config" and switch its
canonical URL from the Cloudflare Pages subdomain to
fish-config.rootiest.fyi (now aliased in Cloudflare). Updates all
references in README, config-help, open-url, and the manual, and
regenerates the concat/man-page artifacts to match.

2026-07-26 15:34:08 -04:00

..

feat(docs-site): scaffold Astro Starlight site

2026-07-25 22:27:55 -04:00

feat(docs-site): scaffold Astro Starlight site

2026-07-25 22:27:55 -04:00

style(docs-site): use green as the primary accent instead of mauve

2026-07-26 00:15:13 -04:00

.gitignore

feat(docs-site): scaffold Astro Starlight site

2026-07-25 22:27:55 -04:00

astro.config.mjs

docs: update site title and canonical URL

2026-07-26 15:34:08 -04:00

package-lock.json

feat(docs-site): scaffold Astro Starlight site

2026-07-25 22:27:55 -04:00

package.json

feat(docs-site): scaffold Astro Starlight site

2026-07-25 22:27:55 -04:00

README.md

docs(site): replace starter README and title synopsis fences

2026-07-26 05:01:01 -04:00

tsconfig.json

feat(docs-site): scaffold Astro Starlight site

2026-07-25 22:27:55 -04:00

README.md

fish-config docs site

Starlight site for the fish-config manual.

Generated, not authored

Everything under src/content/docs/ is generated — do not edit it directly, changes will be overwritten. The sources are:

docs/manual/** — prose for every section except the functions reference
functions/*.fish comment headers — the functions reference (Section 5)

Regenerate from the repo root:

python3 docs/build-manual.py --site

docs/verify-manual.py validates both sources before you build; run it first if you've touched a header or a manual page.

Development

cd docs/site
npm install
npm run dev

Deploy

Built and deployed to Cloudflare Pages by the Gitea Actions workflow on every push to main — there's no manual deploy step.