website layout, organization, and navigation

[thescientist13]

Type of Change

• New Feature Request
• Documentation / Website
• Improvement / Suggestion
• Bug
• Other (please clarify below)

Summary

As we plan to grow the website with more content and updates, like

• GraphQL (Apollo) data as its own package #278
• articulate Greenwood's vision / value through the home page #268
• Documentation for Netlify CMS  #313 / Create a guide for hosting a Greenwood site with GitHub Pages #320

We should think if there any sitewide changes / redesigns we would want to take.

Details

TBD

[thescientist13]

This might be a helpful resource on the topic

[thescientist13]

should also absorb #278 and #268 ?

[thescientist13]

Stripe docs are pretty next level 🤯

[thescientist13]

Had some thoughts on layout / structure

• Rename
  • Menu -> Collections / Groups
  • Templates -> Layouts (make docs file naming consistent as well)
  • page.html -> default.html
  • devServer -> server
• Sort docs/ side nav better?
  • I think it should be progressive in sequence of need to know. Right now it jumps right into component model, but maybe should go from least to most advanced? e.g. go from Build -> Layouts -> Markdown -> FM -> Components -> Styles -> etc (flow through a general order of
  • Or should either be alpha sorted?
• Formatting for guides should have consistent structure / format
• Add dedicated examples on content authoring, e.g. static vs dynamic
  • pages are just components, right?
  • dynamic as a "page" tag in the template HTML (markdown can be empty!)
  • dynamic as a "page" tag in the markdown

[thescientist13]

will be carried out in a discussion first in #503