Order of documents vary between development and production builds
See original GitHub issueBug Report
Describe the bug
The order of the menu is different between the development and production version of the same set of files.
Development Version Production Version
From what I can see, it is based on the file names rather than the order. My file structure looks like
but when I change the folder names to be 1-brand
and 2-atoms
they order correctly. To then get the documents to arrange correctly, I have to do the order ascending (without setting the order: ‘ascending’ option as that does nothing) and then work with it looking strange in the dev version
- OS: OSX 10.3.4
- Node/npm version: 10.1.0/5.6.0
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Technical Documentation in Software Development: Types, ...
And different types of documents are created through the whole software development lifecycle (SDLC). Documentation exists to explain product ...
Read more >What is an Engineering Change Order (ECO)?
An engineering change order (ECO) is a document that specifies either new product design details or proposed changes to existing products. ECOs provide...
Read more >5 Steps to a Successful Release Management Process
Build release. With the release plan finalized, you can start designing and building the product for release. This is the actual “development” of...
Read more >Deployment environment
Architectures. Deployment architectures vary significantly, but, broadly, the tiers are bookended by starting at development (DEV) and ending at production ( ...
Read more >What is Product Development? The 6 Stage Process ...
The product development process is a six-stage plan that involves taking a product from initial concept to final market launch.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Can be a good choice, but I have some points:
.mdx
directly can be bad because we’ll need to transpile they after import to read and this can be a performance leakyAnother solution that I’m thinking about is using an export const instead of a front matter to define document settings, so we can easily import the menu and using on the definition, like that:
What do you thinking about that @mAAdhaTTah?
I think defining the menu & submenu items via a multi-dimensional array, rather in the front-matter of the pages, would be better. The annoying thing is wanting to rearrange the location of a page on the list and needing to change every single page in order to get it into the right place.
First thought is something like this:
Even better if we could maybe import the files:
Thoughts?