# These variables are made globally available in the HTML templates. # Make sure that they do not conflict with HTML tag names. # You can override them on a per-note or per-directory basis by creating the # associated .yaml file. # Order is used by Emanote to determine the sidebar order of notes. order: 0 tags: [] # TODO: How to design this when generating RSS feeds? template: # Which template to use to render notes. The filepath without the .tpl extension. name: /templates/layouts/book # Layout specific settings layout: # For base.tpl base: # The class to apply for element when using base.tpl (used by note and book layouts) bodyClass: bg-gray-400 overflow-y-scroll note: containerClass: container mx-auto max-w-prose error: containerClass: container mx-auto max-w-prose uptree: # Class to apply for uptree's nodes nodeClass: text-gray-900 # List of available colors: https://v2.tailwindcss.com/docs/customizing-colors#default-color-palette theme: blue # Value of the tag. baseUrl: / # Change this to 'pretty' if you want URLs without the '.html' suffix. urlStrategy: direct iconUrl: ${ema:homeUrl}favicon.svg sidebar: # Whether this node in the sidebar tree should remain collapsed by default # (unless a route in it is active) collapsed: true # Weather this node should put folders before single notes folders-first: false stork: # https://stork-search.net/docs/config-ref#frontmatter_handling frontmatter-handling: omit pandoc: # Rewrite the class specified in Pandoc's Div and Span nodes. You can specify the class using # https://github.com/jgm/commonmark-hs/blob/master/commonmark-extensions/test/attributes.md # # This feature is useful when managing a "library" of CSS styling to use on # Markdown text, especially when using Tailwind. rewriteClass: # How to style inline tags. Tag-specific styles can be applied as well. emanote:inline-tag: font-bold bg-gray-100 py-0.5 px-2 rounded-lg # This style is used by `#a/red/tag` in addition to the generic style above. # As this class comes *after* the generic class, it can override the styles # in the generic class. emanote:inline-tag:a/red/tag: bg-red-100 emanote:placeholder-message: text-gray-400 border-t-2 inline-block pt-0.5 emanote:error: text-l bg-red-100 p-2 border-2 border-black m-2 font-mono emanote:error:aside: font-mono align-top text-xs mr-1 tracking-tighter opacity-50 hover:opacity-100 # You can also add your own class -> style mappings. We provide a sample below. sticky-note: px-3 py-1 rounded shadow bg-yellow-100 mx-2 transform -skew-y-1 scale-95 hover:scale-100 hover:border-yellow-400 hover:shadow-lg border-t-8 border-yellow-200 mb-8 mt-8 note: p-2 mb-3 rounded shadow bg-gray-100 w-full float-none md:float-right md:w-1/2 md:clear-both highlight-block: px-3 py-1 mb-3 rounded bg-${theme}-100 hover:border-${theme}-400 hover:shadow border-t-8 border-${theme}-200 highlight-inline: bg-yellow-200 px-2 py-0.5 rounded-xl center: flex justify-center items-center mx-auto # Put page-specific metadata here. Override them in Markdown frontmatter or # per-folder YAML as necessary. page: siteTitle: My Emanote Site # Desription is expected to be set on a per-page basis. # By default, the first paragraph is used for description. # Used for https://ogp.me/ description: "" # Image URL for previews. # By default, the first image URL is used. Note: wikilink are not yet # supported. # Used for https://ogp.me/ image: "" # Put anything that should go in of these routes here: # You can reference other metadata keys using # Or use the JS behaviour library below. headHtml: | # Put anything that should below the of these routes here: # You can reference other metadata keys using # Or use the JS behaviour library below. bodyHtml: | # Builtin JS behaviour library. Use them in `page.headHtml` of your .yaml or .md # frontmatter. js: # Syntax highlighting using prism.js prism: | # Syntax highlighting using highlight.js highlightjs: | highlightjs-ver: 11.6.0 # Ref: https://cdnjs.com/libraries/highlight.js # Diagrams using mermaid.js mermaid: | mathjax: | emanote: # Whether to automatically treat folder notes as a folgezettel parent of its contents folder-folgezettel: true