Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Proposal: auto generate sidebar

Aperta
#1,290 9 commenti 17 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 8 giorni

@sy-records ci sta già lavorando.

Dal 28/7/2025.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

enhancement pinned

Auto-generate sidebar

Summary

Auto-generate and update the sidebar i.e _sidebar.md by looking into the folders/files

Motivation

If you have a big project or a project having many markdown files. It is kind of extra work look for each file and writes the path and the file name and the text to display it.
Maximum projects I have seen take each .md file as a single page and .md files under a folder inside the docs directory is a sub-page. So if we go with usual lookups through each file/folder. This is quite easy to achieve.

Detailed Design

No changes are required in the core. Only needs changes in cli. New command probably

If we have directories like this

|- <root>
       |- README.md
       |- index.html
       |- _sidebar.md
       |- a.md
       |- guide
            |- guide-a.md
       |- b.md

The sidebar command should generate the following

- [a](./a.md)
- guide
  - [a](./guide/guide-a.md)
- [b](./b.md)

We need to traverse through the directory and create an object or tree and then just print the tree as a list in the markdown.

Documentation

Update the docs in the main docs site as a separate page and create docs for the command in the cli and do a remote rendering of the page in the main docs

Drawbacks

Few

  • It won't know whether markdown file should be in the heading or in subheading if it goes out of our prediction.
  • cant do the operation for the .html files.

Backwards Compatibility Analysis

Not required as no changes in the core is being done.

Alternatives

Do the manual entry in the _sidebar.md

Open Questions

  • Should we wait for or put this in v5 ?
  • Any volunteers for taking this ?

Help Needed

None.

Frequently Asked Questions

None

Related Discussions

Couldnt find any.

Lingua principale
JavaScript
Stelle
31.6k
Fork
5.8k
Merge medio
7g 18h
PR unite (30g)
9

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di docsifyjs/docsify

Tutte le issue di docsifyjs/docsify

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.