Create the Docs Microservice #2746
Labels
developer experience
Helping the Developer Experience
type: documentation (docs)
Improvements or additions to documentation
type: enhancement
New feature or request
type: nice to have
Feature that'd be nice to have, but not a priority
Milestone
What is the idea?
We started loving docs again and will be spawning a great number of new docs:
and more to come...
We can create a microservice for our docs and containerize the web application where our docs will live. Such an idea has been brewing since 2019 #290
How would it look like? (if applicable)
We kind of started working on this for Telescope 2.0, so we have some sort of MDX implementation (for the About Us page). Let us move the MDX stuff into its own microservice since it's not really related to the main Telescope app. This microservice will live in /src/api/docs so when we visit https://telescope.cdot.systems/docs, we can easily find whatever document we need instead of going to the /docs directory in the Telescope repo
What existing technologies need to be used? (if applicable)
I want to try this stack to build this web app.
What areas will have to be worked on? (issue labels of type
area
) Describe which, how, and why.What does the idea solve?
Documentation for our documentation because who is enjoying Telescope's bowl of spaghetti docs?
We can have docs for developers. Docs for users. Docs for Windows, Docs for Mac. Docs for Linux... Docs for everyone. While this may seem like a 'nice-to-have' feature, it should really be 'fun-to-have' because it will be FUN. F-U-N. Fun. Just to further prove how fun this can be, I'm willing to help get this started (once the team has approved this proposal), and whoever wants to jump in can jump in. I'm also okay with munching on this solo if no one else shows interest since I don't see this blocking anything in progress.
The text was updated successfully, but these errors were encountered: