Documenting changes between releases
Improvements or additions to documentation
General thoughts and considerations on a topic
A new feature or enhancement request
New ideas and proposals to be evaluated and developed
Additional book contents proposal (text and/or code)
Things to check before merging new release.
From @roodyyogurt annotated PDF of Hugo Book
Contents changes that need to be documented
To be done right before 1st release on master branch
Issue requires approval by Ken Tessman
Issue requires decisions by maintainers
Task completed in dev branch, waiting to be merged into master.
Approved changes waiting to be implemented
Work in progress (possibly with tasks list).
TBD in the next release *after* the upcoming one
Policies: How to contribute to project and docs.
Policies: AsciiDoc formatting conventions.
Policies: How Book elements should be styled
Issues with conversion to HTML format
Issues with conversion to PDF format
Issues with online book via GitHub Pages
Tool: GitHub Pages project website
Tool: Highlight (syntax highlighter)
Issue requires further researching
Further information is requested