home-assistant-markdown-liquid-style

Use absolute links that ignore the source directory and the leading underscore of the first folder. For example, link to source/_integrations/date.markdown as /integrations/date/, using a trailing slash instead of file extensions like .markdown or .md.

Use the Liquid syntax {% term <term> %} with a term or alias defined in source/_data/glossary.yml. For multi-word terms, quote them, such as {% term "configuration.yaml" %}. If a term is missing, add it to the glossary file.

A My link opens a page directly in the reader's own Home Assistant installation, helping them follow a UI path. Use syntax like {% my integrations title="**Settings** > **Devices & services**" %} to reference common settings pages.

Markdown is preferred over HTML wherever possible. Exceptions include abbreviation tags for acronyms, the lite-youtube element for videos, and the p class='img' pattern for captioned images.

Use the lite-youtube element with the videoid attribute set to the part of the YouTube URL after watch?v=. Add videoStartAt only when playback should begin at a specific time, and include a videotitle.

Use caution for actions that may cause data loss or hard-to-reverse consequences. Use warning for risks that could compromise system security or integrity, or cause physical harm. Avoid overusing text boxes overall.