Sample blog post with default Markdown styling options

This post demonstrates a range of default Markdown styling options. You can add more; see https://cloudcannon.com/documentation/developer-articles/what-are-rich-text-editors/#the-wysiwyg-toolbar

Heading level two: for major sections

This is the primary heading level for main sections within blog posts. It provides clear visual hierarchy and helps readers scan content structure.

Heading level three: for subsections

Use this level for breaking down major sections into smaller, more specific topics. It maintains hierarchy while keeping content organized.

Heading level four: for detailed breakdowns

This heading level works well for specific examples, case studies, or detailed technical explanations within subsections.

Heading level five: rarely needed

Most blog posts won’t require this level of depth, but it’s available for extremely detailed technical documentation or comprehensive guides.

Heading level six: the smallest heading

This is the deepest heading level available. Use sparingly and only when truly necessary for content organization.

Text formatting options

Bold text is used for emphasis, important terms, or key concepts that deserve attention. Use it sparingly — overuse reduces impact.

Italic text provides subtle emphasis, often for technical terms, foreign words, or when you want to stress something without the weight of bold.

You can combine formatting: bold and italic together or bold and italic at once. These combinations should be used rarely and only when truly necessary for clarity.

Lists for organizing information

Numbered lists

Use numbered lists when order matters or you’re presenting sequential steps:

1. First item in the sequence
2. Second item follows logically
3. Third item continues the progression
4. Fourth item maintains the flow
5. Fifth item completes the sequence

Numbered lists work well for:

• Step-by-step instructions
• Ranked comparisons
• Chronological events
• Priority-ordered items

Bulleted lists

Use bulleted lists when order doesn’t matter:

• First point in the collection
• Second point of equal importance
• Third point, also unordered
• Fourth point in the set
• Fifth point completing the group

Bulleted lists work well for:

• Feature lists
• Unordered collections
• Options without hierarchy
• General information points

Nested lists

You can nest lists within lists for more complex structures:

1. Primary point requiring elaboration
   • Supporting detail for the primary point
   • Additional supporting information
   • Third supporting detail
2. Second primary point with sub-items
   • Nested detail under second point
   • Another nested item
3. Third primary point
   • Final nested detail
   • Concluding nested item

Blockquotes for emphasis

Blockquotes are excellent for highlighting important statements, customer testimonials, or key takeaways that deserve special attention. They provide visual break from regular text and draw the reader’s eye to critical information.

You can also use blockquotes for extended quotations:

“Our infrastructure performed flawlessly during the highest traffic event we’ve ever experienced. Jetstream’s team anticipated our needs and prepared the network before we even asked. That’s the kind of proactive engineering that makes them different from every other CDN provider we’ve evaluated.”

— Elena Rodriguez, CTO of StreamVault Media

Images in blog posts

Images should be used strategically to illustrate concepts, show data visualizations, or provide visual breaks in text-heavy content.

Figure 1: North American edge node distribution across Jetstream’s network infrastructure

When including images, always provide:

• Descriptive alt text for accessibility
• Clear captions explaining what the image shows
• Relevant context connecting the image to surrounding text

Links to related content

Links should be naturally integrated into sentences rather than presented as bare URLs. This maintains readability while providing navigation options.

You can link to:

• Blog posts for related content
• Anchors on pages when discussing features
• External resources when citing sources
• Documentation for technical details