-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Explore frontend hosting options for better content accessibility #87
Comments
Some additional alternatives to consider: Documentation-Focused SolutionsMkDocs
GitBook
Docusaurus
Any of these could be valid alternatives to a custom Next.js solution. They'd require less development effort since they're purpose-built for documentation, but might be slightly less flexible for custom features. They all support keeping GitHub as the source of truth while providing a more user-friendly interface for content consumption. |
Nice one! So if i Understand right: this issue replaces this one? #75 If so, here some inspiration: And fi so @ichoosetoaccept feel free to close #75 |
Hey! No it is not meant to replace a "prompt directory". #75 could end up being a section of this new docs site. What I mean with this issue is to have the content displayed in a more inviting form. Examples:
Instead of having the content live in a static README.md we could set up a full documentation site like in these examples and have the content be sourced from this Github repo. It would make the content easier and nicer to look at, faster, easier to use etc. The added benefit here would be that people would be more likely to actually use this resource and, in turn, find it useful. |
Overview
Exploring options to create a more user-friendly frontend interface for the repository content while maintaining GitHub as the backend for contributions.
Current Situation
Potential Solutions to Explore
Next.js + Cloudflare Pages
Key Requirements
Next Steps
Notes
This would provide a more polished experience for content consumers while keeping the straightforward GitHub-based workflow for contributors. The dual approach (GitHub for contributions, frontend for consumption) could offer the best of both worlds.
The text was updated successfully, but these errors were encountered: