From 64801a8a932a7cfe0c7705862d413d0418c5c29a Mon Sep 17 00:00:00 2001 From: Justin Mclean Date: Tue, 13 Oct 2026 23:58:35 +1100 Subject: [PATCH] Fix broken internal links and anchors Correct 15 links: mismatched permalink anchors, missing # and https://, wrong page names and anchor typos. --- content/pages/asf-pelican-gettingstarted.md | 2 +- content/pages/asf-pelican-local.md | 2 +- content/pages/committers.md | 2 +- content/pages/doc.md | 2 +- content/pages/git-primer.md | 6 +++--- content/pages/infra-contact.md | 4 ++-- content/pages/new-committers-guide.md | 2 +- content/pages/openpgp.md | 8 ++++---- content/pages/services.md | 2 +- 9 files changed, 15 insertions(+), 15 deletions(-) diff --git a/content/pages/asf-pelican-gettingstarted.md b/content/pages/asf-pelican-gettingstarted.md index 02d50f803..e2c99e3ed 100644 --- a/content/pages/asf-pelican-gettingstarted.md +++ b/content/pages/asf-pelican-gettingstarted.md @@ -50,7 +50,7 @@ staging: 13. When you are ready to publish the site, create a pull request to merge the content in staging into the trunk of the repo. That will trigger a build of the live site. 14. Visit `YourProject.apache.org` after every update to make sure it displays and functions correctly. -**Note**: we strongly suggest that you do your site development in a [branch](apache-pelican-branches.html) rather than the trunk of the repository, and then merge the branch into the trunk when you are sure that everything is working as you would like it. Each commit to the trunk triggers an automatic build to update your live site; this is great for trivial changes like correcting typos, but more of a challenge if you are making major changes and it turns out that there is an error in your code that disables your live site. +**Note**: we strongly suggest that you do your site development in a [branch](asf-pelican-branches.html) rather than the trunk of the repository, and then merge the branch into the trunk when you are sure that everything is working as you would like it. Each commit to the trunk triggers an automatic build to update your live site; this is great for trivial changes like correcting typos, but more of a challenge if you are making major changes and it turns out that there is an error in your code that disables your live site. ### Frameworks diff --git a/content/pages/asf-pelican-local.md b/content/pages/asf-pelican-local.md index e338312aa..ec2ddb9b5 100644 --- a/content/pages/asf-pelican-local.md +++ b/content/pages/asf-pelican-local.md @@ -3,7 +3,7 @@ license: https://www.apache.org/licenses/LICENSE-2.0 **Note** In 2019 Infra created ASF-Pelican as a structure and template for projects to use to build their websites, and for the ASF's own website. -In 2024, Infra moved from ASF-Pelican to the ASF Infrastructure Pelican Action GitHub Action to perform the same functions without being closely tied to BuildBot. The repository for this GHA is github.com/apache/infrastructure-actions/tree/main/pelican. +In 2024, Infra moved from ASF-Pelican to the ASF Infrastructure Pelican Action GitHub Action to perform the same functions without being closely tied to BuildBot. The repository for this GHA is github.com/apache/infrastructure-actions/tree/main/pelican. The material below relates to the 2019 ASF-Pelican and is **not relevant** to the Pelican GitHub Action. diff --git a/content/pages/committers.md b/content/pages/committers.md index c2bd30707..022344aaf 100644 --- a/content/pages/committers.md +++ b/content/pages/committers.md @@ -20,7 +20,7 @@ If you are not an Apache committer, but wish to become one, see General -

What is Community Over Code?

+

What is Community Over Code?

The Apache Software Foundation periodically organizes conferences focusing on software developed at The ASF and on the way that ASF projects develops software. Learn about what's happening at The ASF, hack code and meet the faces associated with the names! diff --git a/content/pages/doc.md b/content/pages/doc.md index 17de6657a..946265a67 100644 --- a/content/pages/doc.md +++ b/content/pages/doc.md @@ -44,7 +44,7 @@ Infra provides a library of resources that is constantly evolving to reflect the - Here is how one project did the migration. - A [project site template](asf-pelican.html) written in Pelican is available to smooth migration away from the CMS, and to support creation of new project sites. - [Managing your project website](project-site.html) -- [Project blog](project-blog.html) +- [Project blog](project-blogs.html) - Managing permissions on your project's Confluence space. #### Other #### diff --git a/content/pages/git-primer.md b/content/pages/git-primer.md index c9ce240ab..cf2fda00c 100644 --- a/content/pages/git-primer.md +++ b/content/pages/git-primer.md @@ -7,8 +7,8 @@ This document is a primer on using Git for an Apache Software Foundation project - Repository types - Public and private repositories - - Repository checkout - - Using .asf.yaml + - Repository checkout + - Using .asf.yaml - Committers: getting started - Windows users - Line endings @@ -56,7 +56,7 @@ https://gitbox.apache.org/repos/asf/reponame.git - **Non-Committers**: `$ git clone http://gitbox.apache.org/repos/asf/reponame.git` -

Using .asf.yaml

+

Using .asf.yaml

`.asf.yaml` is a branch-specific YAML configuration file that a project may create (using a text editor of your choice) and put in the root of a Git repository to control features such as diff --git a/content/pages/infra-contact.md b/content/pages/infra-contact.md index 889381abb..3f3d07e19 100644 --- a/content/pages/infra-contact.md +++ b/content/pages/infra-contact.md @@ -41,7 +41,7 @@ That depends on your role and what you want to do. If this chart doesn't help, I discuss something publicly with Infra, or ask Infra a question - The #asfinfra Slack channel, or by taking part in a Roundtable (the end of each Roundtable session is an open-mic opportunity for your comments or questions). See https://infra.apache.org/roundtable.html. + The #asfinfra Slack channel, or by taking part in a Roundtable (the end of each Roundtable session is an open-mic opportunity for your comments or questions). See https://infra.apache.org/roundtable.html. Consider these semi-public forums which are not suitable for confidential information. @@ -193,7 +193,7 @@ Don't see here what you're looking for? See above for Other Requests -

What can I ask for?

+

What can I ask for?

See the list of [Services and tools](https://infra.apache.org/services.html) Infra provides for projects. If you want something that isn't listed, get in touch with a Jira ticket for Infra. It might be possible to support it, especially if the feature request includes a list of [volunteers](infra-volunteer.html) who will help maintain it hint, hint.

diff --git a/content/pages/new-committers-guide.md b/content/pages/new-committers-guide.md index b5e8bbcd6..8c1bc5b57 100644 --- a/content/pages/new-committers-guide.md +++ b/content/pages/new-committers-guide.md @@ -162,7 +162,7 @@ Please be aware that Apache Software Foundation committers are targets for ident Leaking your access to Apache can have very destructive consequences. **Never** disclose your ASF password to anyone. The Apache Infrastructure team is clueful about DNS maintenance: do **not** trust any redirection by IP address. Your access to Apache will be through the -machines serving the `svn.apache.org` domain. The SSH/SSL fingerprints of machines are listed on the machines page, and our SVN server fingerprints are also listed. +machines serving the `svn.apache.org` domain. The SSH/SSL fingerprints of machines are listed on the machines page, and our SVN server fingerprints are also listed. Please use caution. Do not hesitate to ask if you have doubts: post a question to infrastructure before taking any action. diff --git a/content/pages/openpgp.md b/content/pages/openpgp.md index 42a2b440e..c0aaa3121 100644 --- a/content/pages/openpgp.md +++ b/content/pages/openpgp.md @@ -409,11 +409,11 @@ Creating a different key with a matching identity is considered [infeasible](rel precise identity matters and that identity is specified on the command line, you should use the key ID to identify the key. Avoid using user ID or other information. -

Find a key ID from a trusted source

+

Find a key ID from a trusted source

The best way to find a key ID is to obtain it directly from a trusted source, for example, from a business card you obtain personally from the owner of the key. -

Find a key ID with its fingerprint

+

Find a key ID with its fingerprint

If you have a [fingerprint](release-signing.html#fingerprint), the key ID should be the last 8 digits. For example, the ID of the key with this fingerprint: @@ -565,7 +565,7 @@ For example, to export to the [command line](#export-option-output) with [ASCII $ gpg --export --armor AD741727 ``` -

Should I export all or some public keys"

+

Should I export all or some public keys"

This is often a tricky question. An import should not be trusted for key identification (see [discussion](#find-key-id)). So, for an import to be useful, usually the key ID of interest needs to be known. @@ -815,7 +815,7 @@ The suffix `.asc` is conventional for ASCII armored public key exports. So, for If your Apache home page contains details of your keys (recommended), update the [fingerprints](release-signing.html#fingerprint) and the [ASCII armored](release-signing.html#ascii) [public key](release-signing.html#public-private) [export](release-signing.html#export). Any browser with a suitable [OpenPGP](release-signing.html#openpgp) plugin (for example, Firefox with the FireGPG plugin) will let you download the key into the local keyring. -For example, this home page contains a section with fingerprints and a for exporting them. At the bottom, the export has been inlined so browsers with [OpenPGP](release-signing.html#opengpg) support can import the keys. +For example, this home page contains a section with fingerprints and a for exporting them. At the bottom, the export has been inlined so browsers with [OpenPGP](release-signing.html#openpgp) support can import the keys. To create an [ASCII armored](release-signing.html#ascii) [public key](release-signing.html#public-private) [export](release-signing.html#export): diff --git a/content/pages/services.md b/content/pages/services.md index 99b00069a..d86121968 100644 --- a/content/pages/services.md +++ b/content/pages/services.md @@ -241,7 +241,7 @@ Infra manages the ASF DNS, which is registered with Namecheap. URL shortener -

Infra Reporting Dashboard

+

Infra Reporting Dashboard

The ASF Infrastructure Reporting Dashboard contains a collection of reports on the overall health and activity of the infrastructure at the ASF. Some reports are available only for ASF Members and Infra team members.