-
-
Notifications
You must be signed in to change notification settings - Fork 1
chore: update navigation structure #5
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
|
And I also cleaned up a bit the pages that shouldn’t be included |
|
The order I’m proposing doesn’t have to be final, and it can be changed as we iterate. |
|
the |
| "index", | ||
| "quickstart", | ||
| "development" | ||
| "index" |
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.
@AugustinMauroy are you referring to this route?
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 think.
I'
Yeah Mintlify is supposed to replace the whole website, so the homepage will need to be customizable. We do need a designer tho. Or simply can do something similar to Node.js |
We can like just an hero section + an example/illustration |
Summary
The goal of this PR is to bring over the menu that already exists on the official website to make navigation easier, and to add pages. It does not attempt to add new content.
The documentation section contains the concepts and configuration, the API section contains only the API, the guides section contains the guides, the loaders section contains the loaders, and the plugins section contains the plugins (here the webpack and webpack-contrib plugins were unified, with community plugins listed last). I think this structure makes it easier to manage the menu so it doesn’t become too long.
The item names will match the title of each page. Since some pages don’t exist yet, the route name is used instead, which is why you see names like index