[Post title — the working headline goes here]

[Deck / standfirst — one or two sentences that expand on the headline and set up the article. Replace with real copy before publishing.]

article cover · 1600×686

[Intro paragraph — open with the problem or the promise. This template shows the building blocks available to you; replace every bracketed block with real writing. Keep paragraphs tight and lead with the point.]

[First section heading]

[Body paragraph. Use inline links where they help the reader, bold for emphasis, and inline code for technical terms. Aim for one idea per paragraph.]

[Another paragraph continuing the section. Headings automatically populate the table of contents on the right and drive the reading-progress bar at the top of the page.]

Key takeaway

[Pull the single most important point into a callout like this so skimmers don't miss it.]

[Second section heading]

[Lead-in to a list. Use ordered lists for steps and unordered lists for unranked points.]

  • [List item — a discrete point or feature.]
  • [List item — keep these parallel in structure.]
  • [List item — three to five reads best.]
inline figure · diagram or screenshot
[Figure caption — explain what the reader is looking at.]

[Third section heading]

[Use a blockquote to highlight a quote, principle, or memorable line.]

[A short, quotable line that captures the article's core idea.] — [Attribution, if any]

[Where code is relevant, drop in a fenced block:]

// [example snippet]
input  -> reason -> act -> output

[Closing section / takeaways]

[Wrap up with the practical so-what: what should the reader do next? Tie it back to the opening promise.]

  1. [Actionable next step.]
  2. [Actionable next step.]
H
[Author name]
[Role · Hamzio]

[Short author bio — one or two sentences. Replace with a real bio, or remove the card if you'd rather not show an author.]