Broken anchor tags
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 20
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 6
Description
[WARNING] Docusaurus found broken anchors!
Please check the pages of your site in the list below, and make sure you don't reference any anchor that does not exist.
Note: it's possible to ignore broken anchors with the 'onBrokenAnchors' Docusaurus configuration, and let the build pass.
Exhaustive list of all broken anchors found:
- Broken anchor on source page path = /articles/2021/10/08/improving-multistage-docker-builds-using-buildx:
-> linking to #ref1 (resolved as: /articles/2021/10/08/improving-multistage-docker-builds-using-buildx#ref1) - Broken anchor on source page path = /articles/2021/10/15/webpack-to-esbuild-part1:
-> linking to #ref1 (resolved as: /articles/2021/10/15/webpack-to-esbuild-part1#ref1) - Broken anchor on source page path = /articles/2021/10/29/how-learning-javascript-helped-me-better-understand-jobs:
-> linking to /documentation/get-started/terminology#message - Broken anchor on source page path = /articles/2022/09/19/auth-security:
-> linking to /documentation#openfn-v2-lightning-/ - Broken anchor on source page path = /documentation/legacy/getting-started/terminology:
-> linking to /documentation/legacy/portability#proposal-v2-latest - Broken anchor on source page path = /documentation/legacy/instant-openhie:
-> linking to /documentation/legacy/about-lightning#standards-and-compliance-matter - Broken anchor on source page path = /documentation/legacy/jobs/errors:
-> linking to #nodevm-limits (resolved as: /documentation/legacy/jobs/errors#nodevm-limits) - Broken anchor on source page path = /documentation/legacy/microservice/home:
-> linking to #Docker-run (resolved as: /documentation/legacy/microservice/home#Docker-run)
-> linking to #Development-up-and-running-guide (resolved as: /documentation/legacy/microservice/home#Development-up-and-running-guide) - Broken anchor on source page path = /documentation/legacy/openfn-roadmap:
-> linking to /documentation/legacy/about-lightning#standards-and-compliance-matter - Broken anchor on source page path = /documentation/cli-walkthrough:
-> linking to /documentation/build/triggers#flow-triggers - Broken anchor on source page path = /documentation/deploy/portability:
-> linking to /documentation/link-to-GitHub#structuring-your-github-repository - Broken anchor on source page path = /documentation/get-started/security:
-> linking to /documentation/design/design-overview#use-bpmn-for-standardized-documentation - Broken anchor on source page path = /documentation/jobs/job-writing-guide:
-> linking to #promise-like-operations (resolved as: /documentation/jobs/job-writing-guide#promise-like-operations) - Broken anchor on source page path = /documentation/release-notes:
-> linking to /documentation/build/triggers#message-filter-triggers
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the Docusaurus documentation build and inspect the listed source page paths, including the dated articles and legacy documentation pages. Trace each broken anchor to its target, then update or remove invalid references. Done means the build reports no broken anchors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100