v2.0.0

The main change in this release is that it introduces support for a Markdown-based syntax. Using that syntax, term definitions can now contain multiple paragraphs, bold/italic text, ordered/unordered lists, hyperlinks, images, code fragments, and more.

How to upgrade from v1 and switch to Markdown

1. Point the static assets to a version starting with @2.
2. When making changes, open Settings at the top of the page and switch the input syntax to Markdown.
3. Inspect all term definitions and correct the formatting where needed.

SRI Hashes

See static assets for how to use these.

• glossary.min.js: sha384-7nikk9RCnQwa++tJpc4NU4wVJtG10nfLDgS8prjf5nR0I7AdaFGz+IBMzYgzSt3G
• glossary.min.css: sha384-H/1aWzjvhZ3zJh2yPxKyN203P2fbFolaMPEu5kKQ2R25LQenWMWcg6G8PCRvviIh

Added

• Support a Markdown-based syntax for term descriptions.

  • This uses elm-markdown which implements GitHub Flavored Markdown.

• Add a "Settings" section on the list page which allows changing the following.

  • How "compact" the overall layout is by adjusting the card widths.
  • Whether a Markdown-based syntax is enabled.
  • Whether the "Export" menu should be shown.

Changed

• Switch to Source Sans 3 font. The Overpass font has undesired behaviour for backticks.
• Restrict item height and show a scrollbar for longer items, depending on overall layout determined by data-card-width.