You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first solution I propose is to use a gatsby theme and automatically build the web documentation off of markdown files.
Here is the Apollo Documentation gatsby theme for example, however it is not needed to be used.
A second gatsby solution would be to make a custom documentation site, and still build the site from markdown. This would be a lot more complicated and would probably want to be done after the first solution is done as it could take a while.
If interested I can provide more information on either solution.
To complete that, I'd say that deploying via gatsby is probably not the hardest part.
The most important thing is to make sure everything is linked together and every classes references the correct classes etc.
Then it's mostly design tweaks and making sure it's nice to navigate and use.
Contribution for this specific issue is the most needed and the most important key for improvement.
PS: If anyone has a different suggestion, we are still open for discussion.
The requirements are as follow:
We already thought about a gatsby solution that could be promising.
(ping @VoidNulll )
The text was updated successfully, but these errors were encountered: