Fix broken internal links in concept files
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- markdown
- Domain
- documentation
Research direction
Open concepts/progressive-trust.md and concepts/public-participation-profile-examples.md at the cited lines and compare each link with the target concept filenames. Fix the four listed references, then review the warning in public-participation-profile-examples.md for any additional broken links. Done means the named internal links resolve to xid.md and progressive-trust.md.
Written by the indexing model from the issue text.
Description
Description
Several concept files have broken internal links that need to be fixed:
Files with broken links:
-
concepts/progressive-trust.md (line 457)
- Current:
[XID Fundamentals](xid-fundamentals.md) - Should be:
[XID Fundamentals](xid.md)
- Current:
-
concepts/public-participation-profile-examples.md (lines 17, 409)
- Line 17:
progressive-trust-lifecycle.md→ should beprogressive-trust.md - Line 409:
progressive-trust-lifecycle.md→ should beprogressive-trust.md - Line 409:
xid-fundamentals.md→ should bexid.md
- Line 17:
Note
The public-participation-profile-examples.md file also has a warning at the top indicating it hasn't been fully checked and proofed, so it may need additional review beyond just fixing the broken links.
Related PRs
This follows up on the documentation improvements made in:
- PR #9: Improved concepts/README.md
- PR #10: Synced main README.md with concepts improvements
- PR #11: Fixed broken links in LEARNING_PATH.md
- Dominant language
- Shell
- Stars
- 6
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
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.
Similar issues
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
chore
Difficulty 1/5 Under an hour Newbie friendliness 91/100
alunduil/alunduil-chezmoi#792 ·
-
area: compat bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
zenhub-dev
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OpenLiberty/ci.docker#747 ·