Lunny Xiao
362878dfba
## Problem `https://docs.gitea.com/help/seek-help` returns 404. It is still linked as the *Support* item of the blog.gitea.com navbar, and it is not the only url in that state: `/usage/webhooks`, `/usage/agit`, `/usage/protected-tags` and `/usage/repo-mirror` are linked from gitea itself and 404 as well. ## Root cause Not a rendering problem of the new site: those pages were moved years ago. `docs/help/seek-help.md` became `docs/help/support.md` in 2023 (`slug: support`), and the flat `/usage/<page>`, `/advanced/<page>`, `/developers/<page>` layout of 1.19 and 1.20 was reorganized into `usage/repository/`, `administration/` and `development/`. The old urls kept working because the site was published to S3 with `aws s3 sync` **without** `--delete`: every page built before a move stayed in the bucket and CloudFront kept serving it. The archived copy of `/help/seek-help` still carries `last-modified: Wed, 12 Jul 2023` - the file was six years stale but reachable. The Astro deployment publishes to Cloudflare Pages, which only serves what the current build emits, so all of those leftovers disappeared at once. I crawled the urls the Wayback Machine has for `docs.gitea.com` and checked them against the live site: 335 non-removed-version urls 404 today, and they are all of this kind. ## Fix 301s in `cloudflare/_redirects`, from every legacy url that has a current equivalent to that page, generated for the root, the `zh-cn` and `zh-tw` prefixes and the `next` (develop) version. Also the runner docs that were published under a full version number (`/runner/0.2.11/`, `/runner/1.0.8/`) and `/runner/next/`, which is `/runner/develop/` now. Checked while generating them, against a full local build: - no rule shadows a page that exists today - the zh translations of `usage/agit` and `usage/profile-readme` were never moved, so they are still served at the old path and are left alone - every target resolves to a page that exists, in the language and version the rule redirects within - no duplicated source, 417 static and 10 dynamic rules, well inside the Cloudflare Pages limits (2100 / 100) ## Out of scope - `/contributing/*`, `/developers/guidelines-*` and `/developers/hacking-on-gitea` 404 too, but those pages moved to the gitea repository, there is nothing on docs.gitea.com to point them at. - The `aliases:` frontmatter of the sources (`/en-us/seek-help`, `/webhooks`, ...) is a leftover of the Hugo site. Docusaurus ignored it and so does the Astro build; those urls have been 404 for years and are not resurrected here. - The blog.gitea.com navbar should link to `/help/support` directly, that needs a pull request against gitea/blog. Reviewed-on: https://gitea.com/gitea/docs/pulls/507 Reviewed-by: bircni <[email protected]> Co-authored-by: Lunny Xiao <[email protected]>
Gitea Docs 
The sources of docs.gitea.com, built with Astro and Starlight.
The site covers three products, all served from this repository:
| Product | Content | Versions | Languages |
|---|---|---|---|
| Docs | docs/, versioned_docs/, i18n/ |
next, 1.27 … 1.22 | English, 简体中文, 繁體中文 |
| API | static/swagger-*.json |
next, 1.27 … 1.22 | English |
| Runner | runner-docs/, runner-docs_versioned_docs/ |
develop, 3 … 0 | English |
The enterprise documentation is built and deployed from its own repository and
reached through /enterprise/, which a Cloudflare worker maintained elsewhere
routes to that deployment.
Development
make install # pnpm install
make serve-fast # english, the version served at the root, starts in seconds
make serve # the whole matrix, every version and language
make build # production build into sites/docs/dist
make check # type checks the site and its components
Search is built by Pagefind while the site is built, so it only answers on the
built site: use make serve-built to try it. With the Algolia credentials
(PUBLIC_DOCSEARCH_APP_ID, PUBLIC_DOCSEARCH_API_KEY) set, DocSearch is used
instead and works in make serve too.
GITEA_DOCS_PRODUCTS, GITEA_DOCS_VERSIONS and GITEA_DOCS_LOCALES (comma
separated) restrict what is built, which is what make serve-fast uses.
GITEA_DOCS_STRICT_LINKS=true turns the warnings about unresolved relative
markdown links into a build error.
sites/docs/README.md documents how the sources are mapped onto the site.
Writing
Pages are plain markdown with the same frontmatter and admonitions as before:
frontmatter slug, sidebar_position and sidebar_label keep working, and so
do the :::note style admonitions and the @version@ style release variables.
Relative *.md links are rewritten to urls while the site is built.
The order of the top level sidebar groups comes from sidebars.js (and
versioned_sidebars/ for released versions), the label and order of every other
group from the _category_.json of its directory.
Cutting a version
make cut-version PRODUCT=docs VERSION=1.28
make cut-version PRODUCT=runner VERSION=4
This freezes the current tree, its translations and its sidebar. The label of
the version, its release variables (@version@, @dockerVersion@, ...) and
which version is served at the root live in
packages/content-loader/src/products.ts and are edited by hand afterwards.
That file is the single source of truth for the product, version and language
matrix.
API docs
The swagger definitions rendered under /api/ live in
static/swagger-latest.json (gitea main) and static/swagger-<minor>.json
(released versions).
make update-api-docs # refresh latest + every released version
make update-api-docs-latest # refresh only static/swagger-latest.json
static/swagger-latest.json is refreshed automatically: the update swagger files workflow runs every 12 hours and opens a pull request whenever gitea main
changed. Released versions are updated by hand when a new gitea version is
documented.
Runner docs
| Version | Content | URL |
|---|---|---|
| develop | runner-docs/ |
/runner/develop/ |
| current series | runner-docs_versioned_docs/version-3/ |
/runner/ |
| older series | runner-docs_versioned_docs/version-2/ |
/runner/2/ |
A version directory covers a whole release series (version-3 documents every
3.x release), so a patch release only needs a content update, not a new
folder. Use floating image tags (gitea/runner:3) and links to the runner's
main branch in those pages to keep them valid across patch releases.
Its sidebar is written by hand: runner-sidebars.js for develop, and
runner-docs_versioned_sidebars/version-<version>-sidebars.json per documented
version.
The pages under reference/ are generated from the runner sources — the command
line reference from --help, the example configuration from generate-config:
make update-runner-docs # develop docs, from the main branch of gitea/runner
make update-runner-docs-released # every series, from its newest stable tag
./update_runner_docs.sh v3.0.2 runner-docs_versioned_docs/version-3/reference
These are refreshed automatically as well: the update runner reference
workflow runs weekly and opens a pull request whenever the runner's CLI or
example configuration changed. Generating them needs Go, since the script builds
the runner binary.
Deployment
main is built and published by the Build and Publish Docs site workflow, to
S3/CloudFront and to Cloudflare Pages. cloudflare/_headers sets the cache
policy and cloudflare/_redirects keeps the urls the site used to serve; both
are copied next to the build output by that workflow.
cloudflare/docsearch-crawler.json is the Algolia crawler configuration.
/enterprise/ is served by another deployment and routed to it by a Cloudflare
worker that lives outside this repository.