Fix UI bugs and improve documentation readability

[shah95rukh]

Summary

This PR fixes several UI bugs and improves the overall readability and visual consistency of the documentation.

Bug fixes:

• Fixed architecture diagram text visibility in dark mode by removing color overrides
• Added missing semicolon in .cta-buttons color property

UI improvements:

• Added Client Features overview page matching Server Features structure
• Unified About page theme with rest of documentation (removed inconsistent purple styling)
• Modernized stat cards with hover effects and link indicators
• Updated step numbers to rounded rectangles for better visibility
• Enhanced CTA buttons with subtle animations and improved contrast

Content improvements:

• Replaced line breaks with commas in Server Concepts table examples for better mobile rendering
• Added table padding and improved vertical alignment for better readability

Motivation and Context

The documentation had several visual inconsistencies and readability issues that affected user experience:

• Architecture diagrams were invisible in dark mode, making them unusable for users
• The About page used a purple color scheme that was inconsistent with the rest of the documentation
• Tables were too dense with poor spacing, making content difficult to read
• Mobile layouts had content alignment issues on smaller screens
• Server Concepts examples with line breaks rendered poorly on mobile devices

These changes improve the overall polish and professionalism of the documentation while maintaining accessibility across all devices and themes.

How Has This Been Tested?

• ✅ Tested locally with npm run serve:docs
• ✅ Verified responsive design on mobile viewports
• ✅ Tested dark mode compatibility across all changed pages
• ✅ Ran npm run format - all formatting checks pass
• ✅ Verified navigation structure and new Client Features overview page

Breaking Changes

None - all changes are purely visual/CSS improvements and documentation additions. No API changes or configuration updates required.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

Screenshots showing before/after comparisons for bug fixes and UI improvements will be added below.

Screenshots

Before:

After:

---

Fixes Examples column in the table

Before:

After:

---

Makes About page styles consistent with the remaining docs

Before:

After:

[jonathanhefner]

I am not sure we want to make all of these changes. Would you mind splitting the changes into separate PRs so that they can be reviewed individually?

[shah95rukh]

@jonathanhefner Thats a fair point.

Heres what's in the current PR:

Bug fixes:

• Dark mode architecture diagram visibility
• Missing CSS semicolon

Subjective improvements (open to discussion):

• Table padding/readability
• About page redesign (theme consistency, modern styling)
• Server Concepts table formatting (line breaks → commas for mobile)
• Client Features overview page (mirroring Server Features structure)

I can split these into 4 separate PRs if needed:

1. Bug Fixes
2. Table Readability & Server Concepts
3. Client Features Overview
4. About Page Redesign

Let me know if I should go ahead with all four, or just start with the bug fixes?

Happy to proceed however fits best with the project’s workflow

[jonathanhefner]

Let me know if I should go ahead with all four, or just start with the bug fixes?

Starting with the bug fixes sounds good! 🙏

[shah95rukh]

New PR raised at #1628 to address the UI bugs (dark mode diagram visibility and CSS semicolon).

I'm closing this PR since it contained a mix of bug fixes and subjective improvements. Please let me know if you'd like me to create separate PRs for any of the other improvements included in this PR.

Thanks for the feedback!