536 html tags visible in technical specification pages - #201
Merged
jpherr merged 2 commits intoJul 10, 2026
Conversation
We currently have a number of instances where html tags are being output to the page inside description blocks instead of displaying active links. This is due to Jinja escaping HTML. This change flags the html as safe and allows the tags to be rendered on the page without escaping.
Previously links themselves were broken due to html tags being escaped by Jinja. They were fixed in a previous commit (a8990bd) but numerous anchor links are out of data and no longer works. This change corrects the links.
jpherr
force-pushed
the
536-html-tags-visible-in-technical-specification-pages
branch
from
July 3, 2026 07:45
76f9e47 to
0b58257
Compare
jpherr
deleted the
536-html-tags-visible-in-technical-specification-pages
branch
July 10, 2026 07:48
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this? (check all applicable)
Description
Enable links in description blocks.
We currently have a number of instances where html tags are being output to the page inside description blocks instead of displaying active links.
Example: https://digital-land.github.io/specification/specification/tree-preservation-order/
This is due to Jinja escaping HTML. This change flags the html as safe and allows the tags to be rendered on the page without escaping.
There is also a change to rectify broken anchors since IDs were out of date.
Note: This change was attempted by Pedro previously, but applied to the html files which are generated during the build step. So whilst the change was merged, all the changes were overwritten during the build because the source markdown files had not been updated.
Related Tickets & Documents
QA Instructions, Screenshots, Recordings
Added/updated tests?
We encourage you to keep the code coverage percentage at 80% and above. Please refer to the Digital Land Testing Guidance for more information.
[optional] Are there any post deployment tasks we need to perform?
[optional] Are there any dependencies on other PRs or Work?