![]() More infrastructure for us to build and maintain in the package compiler and IDE.Markdown is less accessible for some users than exporting to HTML from Word.We use Markdown for metadata content already (README.md, etc).Styling is external to Markdown so should be able to inherit from welcome page structure and more consistently.Markdown is lightweight, can embed html as needed. ![]() It would compile down to html for the package build, and would mean a single source file for both site and package.In the midst of my pursuit of life, liberty, and something else, I came up with this keyboard which vitally switches the position of the A and the B and in doing so. I wonder if using Markdown may be the answer with header metadata for styles, something like:. using the Keyman Engine for Web documentation generation tags – can we make them available in Keyman as well (greatly simplifying the help file if so)Ĭoming up with a solid solution is on our radar.including and excluding HTML headers as required. ![]() ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |