Introduction

This article tests all markdown components to ensure the Financial Times-style UI renders everything perfectly. We will cover text formatting, images, blockquotes, lists, tables, and more.

Text Formatting

Regular paragraph text should be rendered in 18px serif font with 1.6 line height for optimal readability. This creates a professional, publication-quality reading experience.

Bold text should stand out clearly, while italic text provides emphasis. You can also combine them with bold italic text* for maximum impact.

Subsection Heading

Subsection headings use a smaller size but maintain the serif font hierarchy. They help organize content into digestible sections.

This is a blockquote testing the blue left border styling. Blockquotes should have ample padding and stand out from regular text while maintaining readability. The Economist-style blue accent adds visual interest.

Lists and Organization

Unordered List

Key findings from our analysis:

• Commercial revenue increased 23% year-over-year
• Broadcast deals remained stable despite economic uncertainty
• Match day income exceeded pre-pandemic levels
• Digital engagement reached all-time highs

Ordered List

Steps to understand the data:

1. Review the historical context
2. Analyze current trends
3. Project future scenarios
4. Draw actionable conclusions

Images and Captions

Modern stadiums generate significant revenue through multiple streams including tickets, hospitality, and commercial partnerships.

The image above demonstrates proper caption formatting with 4px spacing and left-aligned text.

Data Tables

Financial performance of top Premier League clubs:

Tables should render with clean borders and good spacing.

Links and References

For more details, see the Premier League Annual Report which provides comprehensive financial data.

Links should appear in Foxhams blue with proper hover states.

---

Horizontal Rules

Horizontal rules (like the one above) provide visual breaks between major sections.

Code Blocks

Inline code like calculateRevenue() should be monospaced. Full code blocks:

const analyzeFinancials = (revenue, expenses) => {
  const profit = revenue - expenses;
  const margin = (profit / revenue) * 100;
  return { profit, margin };
};

Conclusion

This comprehensive test ensures all markdown components render correctly with proper typography, spacing, and styling consistent with premium financial publications.

All data is sourced from publicly available financial statements and regulatory filings.