diff --git a/docs/content/administration/external-renderers.en-us.md b/docs/content/administration/external-renderers.en-us.md index 66941980a..b593a154c 100644 --- a/docs/content/administration/external-renderers.en-us.md +++ b/docs/content/administration/external-renderers.en-us.md @@ -24,7 +24,7 @@ it is just a matter of: - add some configuration to your `app.ini` file - restart your Gitea instance -This supports rendering of whole files. If you want to render code blocks in markdown you would need to do something with javascript. See some examples on the [Customizing Gitea](../customizing-gitea) page. +This supports rendering of whole files. If you want to render code blocks in markdown you would need to do something with javascript. See some examples on the [Customizing Gitea](administration/customizing-gitea.md) page. ## Installing external binaries diff --git a/docs/content/administration/https-support.en-us.md b/docs/content/administration/https-support.en-us.md index 6441663c8..4e18722dd 100644 --- a/docs/content/administration/https-support.en-us.md +++ b/docs/content/administration/https-support.en-us.md @@ -36,7 +36,7 @@ KEY_FILE = key.pem ``` Note that if your certificate is signed by a third party certificate authority (i.e. not self-signed), then cert.pem should contain the certificate chain. The server certificate must be the first entry in cert.pem, followed by the intermediaries in order (if any). The root certificate does not have to be included because the connecting client must already have it in order to estalbish the trust relationship. -To learn more about the config values, please checkout the [Config Cheat Sheet](../config-cheat-sheet#server-server). +To learn more about the config values, please checkout the [Config Cheat Sheet](administration/config-cheat-sheet.md#server-server). For the `CERT_FILE` or `KEY_FILE` field, the file path is relative to the `GITEA_CUSTOM` environment variable when it is a relative path. It can be an absolute path as well. @@ -85,11 +85,11 @@ ACME_DIRECTORY=https ACME_EMAIL=email@example.com ``` -To learn more about the config values, please checkout the [Config Cheat Sheet](../config-cheat-sheet#server-server). +To learn more about the config values, please checkout the [Config Cheat Sheet](administration/config-cheat-sheet.md#server-server). ## Using a reverse proxy -Setup up your reverse proxy as shown in the [reverse proxy guide](../reverse-proxies). +Setup up your reverse proxy as shown in the [reverse proxy guide](administration/reverse-proxies.md). After that, enable HTTPS by following one of these guides: diff --git a/docs/content/administration/https-support.zh-cn.md b/docs/content/administration/https-support.zh-cn.md index 124242f74..add7906cc 100644 --- a/docs/content/administration/https-support.zh-cn.md +++ b/docs/content/administration/https-support.zh-cn.md @@ -82,11 +82,11 @@ ACME_DIRECTORY=https ACME_EMAIL=email@example.com ``` -要了解关于配置, 请访问 [配置备忘单](../config-cheat-sheet#server-server)获取更多信息 +要了解关于配置, 请访问 [配置备忘单](administration/config-cheat-sheet.md#server-server)获取更多信息 ## 使用反向代理服务器 -按照 [reverse proxy guide](../reverse-proxies) 的规则设置你的反向代理服务器 +按照 [reverse proxy guide](administration/reverse-proxies.md) 的规则设置你的反向代理服务器 然后，按照下面的向导启用 HTTPS： diff --git a/docs/content/usage/labels.zh-cn.md b/docs/content/usage/labels.zh-cn.md index 27c7d84fb..b9cf39304 100644 --- a/docs/content/usage/labels.zh-cn.md +++ b/docs/content/usage/labels.zh-cn.md @@ -27,7 +27,7 @@ menu: 标签具有必填的名称和颜色，可选的描述，以及必须是独占的或非独占的（见下面的“作用域标签”）。 -当您创建一个仓库时，可以通过使用 `工单标签（Issue Labels）` 选项来选择标签集。该选项列出了一些在您的实例上 [全局配置的可用标签集](../administration/customizing-gitea/#labels)。在创建仓库时，这些标签也将被创建。 +当您创建一个仓库时，可以通过使用 `工单标签（Issue Labels）` 选项来选择标签集。该选项列出了一些在您的实例上 [全局配置的可用标签集](administration/customizing-gitea.md#labels)。在创建仓库时，这些标签也将被创建。 ## 作用域标签 diff --git a/docs/content/usage/linked-references.en-us.md b/docs/content/usage/linked-references.en-us.md index a05a07a95..a0acb0242 100644 --- a/docs/content/usage/linked-references.en-us.md +++ b/docs/content/usage/linked-references.en-us.md @@ -94,7 +94,7 @@ Sometimes a commit or pull request may fix or bring back a problem documented in a particular issue. Gitea supports closing and reopening the referenced issues by preceding the reference with a particular _keyword_. Common keywords include "closes", "fixes", "reopens", etc. This list can be -[customized]({{< ref "doc/administration/config-cheat-sheet.en-us.md" >}}) by the +[customized](administration/config-cheat-sheet.md) by the site administrator. Example: diff --git a/docs/content/usage/linked-references.zh-cn.md b/docs/content/usage/linked-references.zh-cn.md index 3cc8dca0b..4d63d7540 100644 --- a/docs/content/usage/linked-references.zh-cn.md +++ b/docs/content/usage/linked-references.zh-cn.md @@ -66,7 +66,7 @@ menu: ## 可操作的引用在合并请求和提交消息中 -有时，一个提交或合并请求可能会修复或重新出现在某个特定工单中。Gitea 支持在引用之前加上特定的“关键字”来关闭和重新打开被引用的工单。常见的关键字包括“closes”、“fixes”、“reopens”等。这个列表可以由站点管理员进行 [自定义]({{< ref "doc/administration/config-cheat-sheet.zh-cn.md" >}})。 +有时，一个提交或合并请求可能会修复或重新出现在某个特定工单中。Gitea 支持在引用之前加上特定的“关键字”来关闭和重新打开被引用的工单。常见的关键字包括“closes”、“fixes”、“reopens”等。这个列表可以由站点管理员进行 [自定义](administration/config-cheat-sheet.md)。 示例： diff --git a/docs/content/usage/multi-factor-authentication.en-us.md b/docs/content/usage/multi-factor-authentication.en-us.md index 16b57b7bd..30323f6de 100644 --- a/docs/content/usage/multi-factor-authentication.en-us.md +++ b/docs/content/usage/multi-factor-authentication.en-us.md @@ -1,6 +1,6 @@ --- date: "2023-08-22T14:21:00+08:00" -title: "Usage: Multi-factor Authentication (MFA)" +title: "Multi-factor Authentication (MFA)" slug: "multi-factor-authentication" weight: 15 toc: false diff --git a/docs/content/usage/pull-request.en-us.md b/docs/content/usage/pull-request.en-us.md index 8c94ee68c..0176d0af9 100644 --- a/docs/content/usage/pull-request.en-us.md +++ b/docs/content/usage/pull-request.en-us.md @@ -66,4 +66,4 @@ The first value of the list will be used in helpers. ## Pull Request Templates -You can find more information about pull request templates at the page [Issue and Pull Request templates](issue-pull-request-templates). +You can find more information about pull request templates at the page [Issue and Pull Request templates](usage/issue-pull-request-templates.md). diff --git a/docs/content/usage/pull-request.zh-cn.md b/docs/content/usage/pull-request.zh-cn.md index db5646f37..757bed280 100644 --- a/docs/content/usage/pull-request.zh-cn.md +++ b/docs/content/usage/pull-request.zh-cn.md @@ -30,4 +30,4 @@ WORK_IN_PROGRESS_PREFIXES=WIP:,[WIP] ## 合并请求模板 -有关合并请求模板的更多信息请您移步 : [工单与合并请求模板](issue-pull-request-templates) +有关合并请求模板的更多信息请您移步 : [工单与合并请求模板](usage/issue-pull-request-templates.md) diff --git a/docs/content/usage/pull-request.zh-tw.md b/docs/content/usage/pull-request.zh-tw.md index 14d1b4950..aeb5df523 100644 --- a/docs/content/usage/pull-request.zh-tw.md +++ b/docs/content/usage/pull-request.zh-tw.md @@ -31,4 +31,4 @@ WORK_IN_PROGRESS_PREFIXES=WIP:,[WIP] ## 合併請求範本 -您可以在[問題與合併請求範本](issue-pull-request-templates)找到更多關於合併請求範本的資訊。 +您可以在[問題與合併請求範本](usage/issue-pull-request-templates.md)找到更多關於合併請求範本的資訊。