You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add support for referencing terms in YAML Frontmatter using Jekyll (or Hugo). Now that we have all the terms at the top in the YAML frontmatter, we can reference those terms when they appear in the Markdown body. Example (I put this file in the repo but it doesn't render correctly yet):
---title: "My Document"author: "John Doe"date: "2024-11-16"---# {{ page.title }}
Written by {{ page.author }} on {{ page.date }}.
The downside is most Markdown renderers don't support Jekyll natively. So far it looks like the best way to get the documents to render the content for viewing and printing is GitHub Pages. We could make a GitHub Pages site for our AOML protocols repository.
The text was updated successfully, but these errors were encountered:
It's ok if the YAML frontmatter has all the variable names, but the first term must be be mustache: ./vars.yaml (or whatever the YAML file is called) to prevent an error from being thrown. So, a simple script would be to 1- copy all the YAML frontmatter to vars.yaml, 2- add mustache: ./vars.yaml as the first term in the file, 3- run pandoc.
Add support for referencing terms in YAML Frontmatter using Jekyll (or Hugo). Now that we have all the terms at the top in the YAML frontmatter, we can reference those terms when they appear in the Markdown body. Example (I put this file in the repo but it doesn't render correctly yet):
The downside is most Markdown renderers don't support Jekyll natively. So far it looks like the best way to get the documents to render the content for viewing and printing is GitHub Pages. We could make a GitHub Pages site for our AOML protocols repository.
The text was updated successfully, but these errors were encountered: