Discussion - guides (solutions / walkthroughs / etc.) and blog

[jeremydw]

I'd like to create a place on our documentation site where we can provide guides in addition to our reference documentation. These guides would include content that tells a narrated story – some thoughts on sample content include:

• How to host assets in Google Cloud Storage and use an extension for image transformation
• How to produce a multilingual blog site
• Each step required to build a static Grow site, integrate with CI, and launch on App Engine or Firebase
• Managing workflows with stakeholders (e.g. staging, live, LQA)

In addition to guides like this, I'd also like our site to have a place where we can show off great examples of open source Grow sites (such as ampproject.org). All this content would also serve to help people discover Grow through organic searches and learn about its features.

Open question: do we lump all this into a blog with post categories, or do we to separate it out into some new guides? section in the documentation site?

Maybe we do the following:

• Create a blog (I like DigitalOcean's blog) for narrative announcement content and website highlights
• Expand the current "Workflow" section of the documentation to "Guides" and place "evergreen" guide content there

Thoughts? @Zoramite @uxder @adelaidemt @stevenle

[Zoramite]

I personally like the idea of the guides being separate from a blog. The blog could be used to highlight them when something major happens or we add new guides, but overall having them be a part of the documentation is a great idea.

I'd like to also add in getting the yeoman grow generator working better so that we can use it in the guides for creating / adding functionality and extensions.

[jeremydw]

Some more notes:

• We have an original launch blog post to incorporate into the blog (http://web.archive.org/web/20140421025932/http://about.grow.io/blog/all-i-want-to-do-is-build-a-web-site/)
• @adelaidemt is working on localization and staging information that we can include with @uxder's handbook and include all of it in these guides too

[jeremydw]

A little more thinking:

• Move current Codelab / Getting Started content into a featured/promoted top-level guide
• All other guides can show up as tiles beneath the main "Getting Started" guide (we can add tagging, etc. at some point)
• Rewrite current "Workflow" content into individual guides for each topic
• Rework site structure to:
  • Homepage
  • Docs (Reference)
  • Guides
  • Blog