Markdown is not a viable delivery format

Markdown requires third-party tools to view properly and lacks features that a release would require.

Solution

Migrate over to HTML for development & web consumption; create PDF documents for releases.

Progress

• style="height: 1rem;" over height="18" for emoji (#1)
• Split document into two columns for PDF releases (single column for web view)
• Host "live document" rules on Github pages (maybe Gitbook for better mobile experience?)

Describe the issue
Some markdown renderers sanitize the style attribute within inline HTML, causing the emoji SVGs to appear at full size rather than match the text size.

Proposal to move web content to Gitbook.

Pros ✔️

• Automatic pagination
• Linking to specific content within a page
• Native support for tabs, callouts, and other useful elements not supported in markdown
• Easier to organize content

Cons ❌

• No custom CSS allowed
• Not as easy to edit directly
• No PDF export
• No offline access at all

⚠️ Todo

• Add an emoji CSS class to clean up emoji in the .md files
• Store emoji locally (custom emoji?)
• Custom sidebar with shields.io badge links (github, discord) and other "presets" expansions (fantasy, scifi)

❓ Optional

• Pagination through the docsify-pagination plugin
• Creative Commons link in footer
• Change header & body fonts (something classic-ttrpg but readable)

🚑 Issues

• docsify will not display logo and title simultaneously fixed via custom sidebar

https://developers.google.com/web/progressive-web-apps/

Proposal to separate Web and PDF work into separate branches. Web will have the most recent updates and content, but PDF will be organized as a book and accessible offline. This solves the need to format the web document like a PDF by making them separate projects entirely.

The license needs to be accessible in both PDF and web delivery formats, as well as licensing & attribution to resources used.

⚠️ Todo

• Add Creative Commons link to sidebar, bottom of PDF
• Attribution for Twemoji