Feature Request: Enhance Changelog with Rich Content and Improved Discoverability

Title: Feature Request: Enhance Changelog with Rich Content and Improved Discoverability

Body:

Hi Claude Code Team,

First off, thank you for creating such a powerful and productive tool. I'm a big fan of its capabilities and how it integrates into my development workflow.

I'm writing to suggest an improvement to how new features and updates are communicated to users. Currently, the changelog is a CHANGELOG.md file in the GitHub repository. While functional, it feels out of step with the high quality of the product itself. The entries are very concise, lack release dates, and don't provide context or visuals for new features.

The Opportunity: A Modern, Rich Changelog

Many of your competitors have set a high bar for their changelogs, turning them into valuable resources for user education and engagement. They use dedicated, beautifully designed pages with rich content that helps users immediately understand and adopt new features.

Here are a few excellent examples:

• Cursor: cursor.com/changelog - Features detailed descriptions, embedded videos/GIFs for UI changes, and clear categorization.
• OpenAI Codex: developers.openai.com/codex/changelog - Includes screenshots, clear dates, and separates changes by platform (IDE, Web).
• Jules: jules.google/docs/changelog/ - Provides visuals, in-depth explanations of new agent capabilities, and a well-structured layout.

These changelogs effectively act as mini-blog posts for each release, making users excited about updates and reducing the learning curve for new functionality.

Suggestions for Improvement

I believe Claude Code could greatly benefit from adopting a similar approach. Here are two concrete suggestions:

1. Relocate the Changelog to the Official Docs Site

The current CHANGELOG.md on GitHub isn't easily discoverable for users who don't frequent the repository. Moving it to the official documentation site would make it much more visible and accessible.

A great location would be alongside the other excellent documentation at https://docs.anthropic.com/en/docs/claude-code/, perhaps at a new URL like https://docs.anthropic.com/en/docs/claude-code/changelog.

2. Enrich the Changelog Content

For each new version release, the changelog could be enhanced to include:

• Release Date: The specific date the version was published.
• Detailed Descriptions: Go beyond a single line to explain what a feature is, why it's valuable, and provide a quick example of how to use it. For example, the 1.0.81 release could have explained what "output styles" are and shown a quick /output-style explanatory example.
• Visual Aids: For any UI or workflow changes, include screenshots, GIFs, or short videos. This is incredibly effective for demonstrating new commands, settings menus, or IDE integrations.
• Links to Documentation: For major new features, link directly to the relevant, in-depth documentation page. The release note for 1.0.38 (hooks) does this well, and it would be great to see this consistently.

Conclusion

Investing in a richer changelog experience would significantly improve communication with your user base, drive faster adoption of new features, and reinforce the perception of Claude Code as a cutting-edge, user-focused product.

Thank you for your time and for considering this feedback. I'm excited to see how Claude Code continues to evolve