This post covers high-value authoring patterns often used in Obsidian workflows.

Callouts

Callouts are structured note blocks.

> [!NOTE]
> Helpful context for readers.

> [!TIP]
> A quick shortcut or best practice.

> [!WARNING]
> Something that can break content or workflow.

Use callouts to reduce wall-of-text and improve scanning.

Foldable Callouts

> [!FAQ]- Why is this collapsed?
> You can hide long details until needed.

Useful for optional detail, troubleshooting, and FAQs.

Transclusion (Embed Existing Content)

![[about]]
![[2026-03-17_webgrid-intro_1_welcome-to-webgrid]]

This reuses existing content instead of duplicating it.

Partial Transclusion (Section or Block)

Section-style usage (when supported):

![[about#Header]]

Block-reference style usage (when supported):

![[about#^block-id]]

How to create a block with an ID:

This sentence is the reusable block content. ^pricing-note

Then transclude it from another file:

![[about#^pricing-note]]

Practical Composition Pattern

Use this stack for long pages:

1. Intro paragraph
2. Key callout (NOTE, TIP, or WARNING)
3. Transcluded reusable section
4. Local page-specific details

Compatibility Note

Callout/transclusion behavior can vary between editor preview and static rendering unless parser support is implemented. Keep critical content understandable even if a specific enhancement is not rendered.

What’s Next

Next post: code blocks, math, raw HTML, and advanced authoring safety checks.

---

← Links, Images, and Attachments · Next: Code, Math, and HTML →