Repository-native rendering beyond Markdown

[AmedeoPelliccia]

🏷️ Discussion Type

Product Feedback
Hi GitHub team,

I would like to ask whether GitHub has any plans to support richer repository-native rendering beyond Markdown.

Markdown rendering is very useful, especially for README.md files and repository documentation. However, many repositories now contain richer documentation artefacts, such as HTML pages, structured documentation outputs, SVG-based views, technical publication files, or lightweight digital pages.

Would GitHub consider supporting optional rendering of additional formats directly inside repositories?

For example:

• static HTML rendering without JavaScript
• sandboxed documentation previews
• repository-defined documentation entrypoints
• richer browsing for technical documentation repositories

This would be useful for engineering documentation, research frameworks, technical publication structures, educational repositories, and digital product documentation.

Additional context:

One concrete use case is technical documentation repositories where the content is not only Markdown, but also structured digital documentation artefacts.

For example, aerospace technical publications, S1000D/IETP-like structures, digital product passport documentation, and architecture/taxonomy repositories may need richer navigation and rendered views while still remaining repository-native.

The request is not necessarily to execute arbitrary web applications inside GitHub. I understand that security and sandboxing are important concerns, especially for HTML and JavaScript. Even a static, sandboxed, no-JavaScript rendering mode for selected documentation entrypoints would already be valuable.

Is GitHub Pages intended to remain the only supported solution for rendered web documentation, or could repository-native rendering be expanded in the future?

Thank you.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐