Links And Emphasis
How to make links, strong text, and calls to action feel deliberate inside the DevDocs docs shell.
We want links to feel like guidance, not like low-contrast footnotes. The docs theme now gives inline references more visual weight so important navigation reads as part of the content system.
What a strong link should do
A strong docs link should:
- tell the reader why it matters
- stand out without looking like a button
- connect cleanly to the broader docs structure
That is why references like release proof, content primitives, and Fumadocs reference docs now read with heavier weight and a clearer underline.
When to use bold text instead
Use strong emphasis when you want to increase contrast on an idea that does not need navigation. Use a link when the next action truly helps the reader.
Pattern examples
Inline references are best for stitching a concept across pages without breaking the reading flow.
Use cards when the reader should choose between a few strong paths, like Delivery versus Components.
Use callouts when the destination needs framing first, especially for preview-safe or control-plane details.
Good examples in this docs set
Preview Environments
An example of links used to move from architecture into operational detail.
Navigation Showcase
An example of component-driven docs navigation that still reads like a product story.
Tone guidelines
Make links pull their weight
Link text should describe the destination and its value. Avoid vague copy like “click here” or “learn more” when the page can say something precise instead.