Change the docs-only section to clearly state, why you should delete index page
See original GitHub issueš Documentation
Now the (docs-only section) states that:
You should delete the existing homepage at ./src/pages/index.js, or else there will be two files mapping to the same route!
. But as I found out, you can keep the file at ./src/pages/index.js, but some markdown features like syntax highlighting wont work.
I propose to change it to something like this: You should delete the existing homepage at ./src/pages/index.js, or else some features like syntax highlighting wont work
Have you read the Contributing Guidelines on issues?
Yes
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
How to Remove All the Index Entries | CreativePro Network
That is frustrating! Fortunately, Find/Change comes to the rescue. Open all the documents (the ones you want to strip of index entries) at...
Read more >Dynamically ADDING and REMOVING Components in Angular
I have created a demo to show the dynamic add and remove process. Parent component creates the child components dynamically and removes themĀ ......
Read more >Drop and rebuild an index - Azure Cognitive Search
This app will back up your index to a series of JSON files, and then recreate the index in a search service you...
Read more >Delete index API | Elasticsearch Guide [8.5] | Elastic
If the Elasticsearch security features are enabled, you must have the delete_index or manage index privilege for the target index. Descriptionedit. Deleting anĀ ......
Read more >13.1.27 DROP INDEX Statement - MySQL :: Developer Zone
See Section 13.1.9, āALTER TABLE Statementā. To drop a primary key, the index name is always PRIMARY , which must be specified as...
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
@svict4 Iām going to make a release as soon as possible and it should fix this issue. On the new release, you wonāt ever have a doc home with no navbar/sidebar (this is definitively a bug that shouldnāt have happened in the first place).
If you keep the file in /pages/index.js, it will keep showing the homepage consistently (just checked, it does), and you should be able to figure out yourself that you need to delete it.
Not this release, but the next one, will also show an exception/error/warning when such route conflict happens (WIP: https://github.com/facebook/docusaurus/pull/3083)
I think the code will itself prevent users from doing the wrong thing. Wonder whatās your opinion. If you feel we need to make the doc more clear, PRs are welcome
Just want to add that there have been multiple questions about missing sidebars/headers/footers (from myself included) on Discord that relates to forgetting to remove the
./src/pages/index.js
file when in docs-only mode