Full Examples
A complete article page built by combining Blog Post Layout, Table of Contents - Pill, Key Takeaways, and Blog Section into one working example

VellumUp6 min readMost teams don't lose organic traffic overnight — it erodes quietly, one skipped week at a time.
Every published article is a small bet on relevance. Skip a month, and competitors who kept publishing quietly absorb the rankings you left on the table.
The fix isn't writing more. It's writing on a schedule you can actually keep. A realistic cadence — even one solid article every two weeks — beats an ambitious plan that collapses after a month.
What to measure instead: total traffic hides the real signal. Track how many articles are still gaining impressions six months after publishing — that number tells you whether your content strategy compounds or just resets every quarter.
None of this works if the content itself is thin. A weekly cadence of shallow, generic posts still loses to a slower competitor publishing something genuinely useful — consistency is a multiplier on quality, not a substitute for it.
The teams that pull ahead treat the first few months as infrastructure work: building topic clusters, fixing internal links, and letting early articles mature, rather than chasing quick wins that don't compound.
Don't start with a topic list — start with a cadence you can actually sustain past week four. Pick one publishing day, block the time on your calendar before you touch a single headline, and treat that slot as non-negotiable for the first month. Momentum is what turns a content plan into a content habit.


The full page file, with each component already wired to the others.
The one non-obvious wiring step: pointing the table of contents at the article body it should track
This page is four catalog components composed together, not a new one: Blog Post Layout provides the hero/title/byline shell and children slot for the body, Table of Contents - Pill floats over that body and scrollspy-tracks it, Key Takeaways drops in near the top of the body like any other block, and Blog Section renders after the article closes to surface more posts. Copy each component from its own catalog entry, then wire them together like the page below.
The one piece that isn't obvious from any single props table: PillTableOfContents needs a contentRef pointing at the exact element that contains the id="..." sections it tracks — so the same ref goes on both the PillTableOfContents prop and the wrapping <div> around the body markup: