I haven't looked at all at styling, or any of the text beyond the end of "2. Introduction". Numbers need removing from titles, the tables need converting from HTML to Asciidoc, and it's just the default style for both HTML and PDF.
Commits to the asciidoc branch will automatically cause a new build and deploy, if you merge this to master someone will need to update the branch used by Jenkins.
I've made a new branch https://github.com/gbif/effective-nodes-guidance/tree/asciidoc with an Asciidoc example:
pandoc -f Markdown -t asciidoc
) everything to Asciidoc.introduction
was used several timesI haven't looked at all at styling, or any of the text beyond the end of "2. Introduction". Numbers need removing from titles, the tables need converting from HTML to Asciidoc, and it's just the default style for both HTML and PDF.
Commits to the
asciidoc
branch will automatically cause a new build and deploy, if you merge this to master someone will need to update the branch used by Jenkins.