Pandoc publishing - the internal link names have I think changed
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 3
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Originally submitted by josephheenan (Joseph Heenan) on 2023-06-28
The pandoc output I think has different internal link names in the FAPI1 Errata to the current document. e.g. this form of link should continue to navigate to the right place:
https://openid.net/specs/openid-financial-api-part-2-1_0-final.html#rfc.section.8.6
(Also that note in FAPI2 and other things using the mmarkdown+xml2rfc pipeline I believe the links are in the same form but without the rfc. on the beginning.)
Bitbucket status: new
Bitbucket origin: issue 614
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 comparing the published FAPI1 Errata link for section 8.6 with the current document output, then inspect the Pandoc and markdown+xml2rfc publishing paths mentioned in the issue. Done means the legacy URL and the corresponding FAPI2 links navigate to the intended sections in the generated documents.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, markdown, xml
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100