normally docsify using the _sidebar.md to render the sidebar..
what if needed when user click a sidebar node (article) to go to new sidebar content ?
here comes the nested sidebars is play. Because the documentation is little it blurry..
currently lets say the content of main _sidebar.md is like that :
to create a nested sidebar :
based of the above, the /test/_sidebar.md, to have back functionality can be :
references :
https://docsify.js.org/#/more-pages?id=nested-sidebars
sample - https://randygaul.github.io/cute_framework/#/getting_started (click the Topics and Tutorials)
what if needed when user click a sidebar node (article) to go to new sidebar content ?
here comes the nested sidebars is play. Because the documentation is little it blurry..
currently lets say the content of main _sidebar.md is like that :
Code:
* [Applications]
* [Internet](/application/internet.md)
* [Bookmarks](/application/internetBookmarks.md)
to create a nested sidebar :
- new folder required
- a md file required ( in our example readme.md )
- a newfolder/_sidebar.md required
Code:
* [Applications]
* [test](/test/readme.md)
* [Internet](/application/internet.md)
* [Bookmarks](/application/internetBookmarks.md)
based of the above, the /test/_sidebar.md, to have back functionality can be :
Code:
- [Back](./)
* [Cabal]
* [Android](/application/android.md)
* [Freewares](/application/freewares.md)
references :
https://docsify.js.org/#/more-pages?id=nested-sidebars
sample - https://randygaul.github.io/cute_framework/#/getting_started (click the Topics and Tutorials)