Skip to content
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

[Enhancement] Extend Gridsome.org Appearance #205

Open
R9980 opened this issue Jun 11, 2019 · 3 comments
Open

[Enhancement] Extend Gridsome.org Appearance #205

R9980 opened this issue Jun 11, 2019 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@R9980
Copy link

R9980 commented Jun 11, 2019

This's a suggestion for enhance gridsome.org sidebar. It'll definitely helpful for others who want to be Gridsome Users

Sidebar

Current
No menu levels. just single topic list under each category.

Expect
Multiple menu levels(groups)/nested children
https://vuepress.vuejs.org/default-theme-config/#sidebar
vuejs/vuepress#1497
https://github.com/timaschew/vuepress-nested-sidebar-demo (source)
https://hungry-yonath-bfd0a1.netlify.com

(Keep exist gridsome sidebar ui and effects. just like it and better than vuepress)


If no consideration for extend default gridsome documentation as mentioned above, atleast prefer request for add proper guide, tutorial for necessary users to follow.

@robaxelsen robaxelsen added the enhancement New feature or request label Jul 24, 2019
@R9980
Copy link
Author

R9980 commented Aug 2, 2019

https://docdock.netlify.com (That's better than above resources)
https://github.com/vjeantet/hugo-theme-docdock

image

@samuelhorn
Copy link
Member

samuelhorn commented Oct 14, 2019

I think the current structure works good as is. But maybe we could scan trough the MD files, adding h2s as new foldable sub anchors under existing first level links. By doing that, templates (https://gridsome.org/docs/templates/) for example becomes:

  • Templates ▼ (link to page with folding arrow)
    -- Setup templates (anchor on page)
    -- Add data to a template (anchor on page)
    -- Node fields as meta info (anchor on page)

I don't think deeper level than that is needed?

If that sound good I could fix it.

@TerabyteTiger
Copy link
Member

Is this similar to #514 (and associated PR #532)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants