Correct Hugo markdown parser config#15931
Merged
Merged
Conversation
✅ Deploy Preview for devopsdays-web ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
nimbinatus
approved these changes
May 29, 2026
Member
nimbinatus
left a comment
nimbinatus
left a comment
There was a problem hiding this comment.
https://gohugo.io/content-management/markdown-attributes/#block-elements matches so approved from me
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
3 participants
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.
#15903 had a typo and so it never actually enabled block and title attributes (because the name should be singular). This PR corrects that.
One thing to note: The preview site build will need thorough checking. The previous PR was merged because there were no adverse effects... but that's because it didn't do anything (due to typo). This fix should enable the feature properly and might cause unwanted issues. If any negative effects are seen, we should roll back #15903 and add a comment to the Hugo config to document.