Refactor automatic section numbers #29
Open
Conversation
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
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.
This change should make the automatic section numbering easier to understand.
The usage of
weightin the output formats is a small hack, so that the template that adds the section numbers to.Page.Storeis executed before everything else.This change should be backward compatible if automatic section numbering is not activated. Otherwise the
hugo.tomlmust be updated to include thesectionnumberoutput format (seeREADME)The change from
config.tomltohugo.tomlin theREADMEjust follows the current recommendations of Hugo. Both will work just the same.