-
Notifications
You must be signed in to change notification settings - Fork 119
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
feat: scaffolding for "v2" docs #2095
base: main
Are you sure you want to change the base?
Conversation
^ the new API is As for the rest of the questions...they're really good ones! Let's chat about them on Wednesday's migration call |
CLI flow is covered, but node & web are just stubs for now
df4615d
to
c13ea92
Compare
This is a very early pass at the new version of the docs site that covers w3up & friends.
So far, I've just copied over the existing content and taken a sledgehammer to it, removing things that obviously don't apply, e.g. Go client, the "query" how-to, etc. There are a great many TODOs sprinkled throughout, and the "net new" docs that didn't have an existing article are all outlines at best. Here be 🐉s, etc.
I'll take a pass this afternoon at mapping the TODOs to existing tickets in Notion and making new ones, with the primary goal of sorting out things that are immediately actionable (no API changes on the horizon, etc).
If anyone wants to click through the deploy preview, I've stuck the new stuff at the
/docs/v2
route, but it's not linked anywhere from the home page or the existing docs yet, so you need to add thev2
to the URL manually, or use this linkSome things to figure out:
cc @heyjay44 & @dchoi27 - don't know if this is worth reviewing in depth yet, but if you have any ideas about the Qs above, LMK :)