-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use absolute slug for packages documentations #23712
Conversation
Isn't it because the parent https://github.com/go-gitea/gitea/blob/main/docs/content/doc/packages.en-us.md is |
Maybe, let me change it. |
Done. But for hugo, it will not join the parent slug maybe docusaurus will. |
This was intended to be a small followup for #23712, but...here we are. 1. Our docs currently use `slug` as the entire URL, which makes refactoring tricky (see #23712). Instead, this PR attempts to make future refactoring easier by using slugs as an extension of the section. (Hugo terminology) - What the above boils down to is this PR attempts to use directory organization as URL management. e.g. `usage/comparison.en-us.md` -> `en-us/usage/comparison/`, `usage/packages/overview.en-us.md` -> `en-us/usage/packages/overview/` - Technically we could even remove `slug`, as Hugo defaults to using filename, however at least with this PR it means `slug` only needs to be the name for the **current file** rather than an entire URL 2. This PR adds appropriate aliases (redirects) for pages, so anything on the internet that links to our docs should hopefully not break. 3. A minor nit I've had for a while, renaming `seek-help` to `support`. It's a minor thing, but `seek-help` has a strange connotation to it. 4. The commits are split such that you can review the first which is the "actual" change, and the second is added redirects so that the first doesn't break links elsewhere. --------- Signed-off-by: jolheiser <john.olheiser@gmail.com>
replaced by #23752 |
Look like there is a duplicated
packages
in https://docs.gitea.com/packages/usage/packages/cargo , It maybe caused by the relative slug in packages documentations.