Hello, World
First post — and a smoke test for the dialect.
This post exists to verify that every feature of the iSolved engineering blog Markdown dialect renders correctly in both Hugo and TechDocs. If you see broken output on either side, file an issue.
Alerts
Note
This is a note. Use it for asides and clarifications.
Warning
This is a warning. Use it for things that will bite the reader.
Important
This is brand-pink-coded — use it sparingly, for stuff that must be read.
Code
A fenced block with a language tag:
def fib(n: int) -> int:
a, b = 0, 1
for _ in range(n):
a, b = b, a + b
return a
Inline code should also render with a subtle background.
Diagrams
flowchart LR
A[Author] -->|writes| B(Markdown post)
B --> C{visibility?}
C -->|public| D[Hugo build]
C -->|internal| E[TechDocs only]
D --> F[Front Door]
E --> G[Backstage]Sized images
Inline HTML for explicit sizing:
What this verifies
- Frontmatter parses (title, date, author handle, tags, visibility, summary)
- Author handle resolves via
data/authors.yaml - GitHub-style alerts render in both renderers
- Mermaid renders client-side via
mermaid.min.js - Sized
<img>survives Goldmark’sunsafemode - Code block with language tag picks up syntax highlighting
- Tags appear in the post footer and link to the tag archive