-
Notifications
You must be signed in to change notification settings - Fork 3
Docs site improvements #4
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
base: main
Are you sure you want to change the base?
Conversation
# Conflicts: # RFC-by-stage/1-approved/docs-site.md
|
Completely agree, I'd like to move the docs as part of the same repo. DTA has already done some work adding the designsystem using Gatsby, if we wanted to roll our own. Alternatively, Docusaurus is also an option, but we'd have to do a bit of work to add a AUDS skin. |
|
I think I will propose nextjs site that we statically build and host on github pages. Will look into it further soon. |
RFC-by-stage/1-approved/docs-site.md
Outdated
|
|
||
| Prior art here: https://github.com/dominikwilkowski/ds-workshop | ||
|
|
||
| MORE DETAILS COMING 😬 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Eleventy could be a good option here, they support vanilla + React, that would work with the design.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I want to first and foremost support no-js in the docs and eleventy no matter how hip it currently is will not allow us to do this. I think the best course of action here is to use nextjs and export it to static HTML and CSS
|
This is a good idea 💯 I'm principally in agreement to doing this. This work is very much dependent on #2 occurring first. |
No description provided.