Standardizing headers, tweaked wording

[shannonbux]

While re-reading this, I'm thinking the order of sections could be a bit hard to digest. (components, global styles, typography.js, plugins. @amberleyromo what order is sensible to you? Usually the most basic pathway is the best, so is there anything else we ought to cut out or re-order to make it more basic?

[KyleAMathews]

Looks great!

[gatsbybot]

Deploy preview for gatsbygram ready!

Built with commit 97c2757

https://deploy-preview-4375--gatsbygram.netlify.com

[amberleyromo]

@shannonbux re: the sensible order, some tweaks along the following lines are what make sense to me. This is mostly a very slight reordering, and a very slight change of focus in the way it's explained.

0. Development environment (by getting in place all of the necessary pieces, which would include succinct explanations of concepts (what is a terminal, and why do you need to interface with it, etc).
1. Introduction to gatsby: goal to scaffold out the starter from the gatsby cli, and have a high-level tour of what ships with it -- what are all these pieces?
2. Thinking in components: here introducing the concepts of components and layouts, again by pointing to the concrete example of the starter scaffold.
3. Styling: Here we can introduce some CSS concepts, probably starting with some plain css, and then making the jump to libraries like Typography.js, etc.
4. Data flow: Instead of making it about learning GraphQL, start with -- the problem we're solving is how to get data from point A to point B. A high-level introduction to the Gatsby style data flow, then some nitty gritty with GraphQL. GraphQL is the tool -- focus on the why, first.

[shannonbux]

@amberleyromo I like those ideas! Especially the tour of what ships with the starter, and the focus on data flow. One thing I've been thinking more and more about is how the really awesome things people can accomplish with Gatsby are data specific--i.e. if someone is an awesome photographer, they can share their work with the world thru Gatsby. If someone has really important election data to share or important research to share, they can share it with Gatsby. I feel really excited about focusing on the why first. Totally on board with all of this. Another thought: data is not going to be an abstract concept for many people. It will be very real and very important to them. So GraphQL is just a way they can get the data they care about out into the world; GraphQL is not an end in and of itself for many people (unless they just really like it :)

…

On Mon, Mar 5, 2018 at 9:30 PM, Amberley ***@***.***> wrote: @shannonbux <https://github.com/shannonbux> re: the sensible order, some tweaks along the following lines are what make sense to me. This is mostly a very slight reordering, and a very slight change of focus in the way it's explained. 1. Development environment (by getting in place all of the necessary pieces, which would include succinct explanations of concepts (what is a terminal, and why do you need to interface with it, etc). 2. Introduction to gatsby: goal to scaffold out the starter from the gatsby cli, and have a high-level tour of what ships with it -- what are all these pieces? 3. Thinking in components: here introducing the concepts of components and layouts, again by pointing to the concrete example of the starter scaffold. 4. Styling: Here we can introduce some CSS concepts, probably starting with some plain css, and *then* making the jump to libraries like Typography.js, etc. 5. Data flow: Instead of making it about learning GraphQL, start with -- the problem we're solving is how to get data from point A to point B. A high-level introduction to the Gatsby style data flow, then some nitty gritty with GraphQL. GraphQL is the tool -- focus on the why, first. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4375 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Ae9o2leJfGy9IwQ_s19FhqiO5Yiy9PlRks5tbh7jgaJpZM4Sdn84> .

[amberleyromo]

Exactly. The problem we're solving is handling data. The tool is GraphQL :)

[shannonbux]

so what would be the next best step here @amberleyromo? I'm not familiar with the ideal github workflow. I'll plan on incorporating these suggestions tomorrow, add those as commits, and then you can comment on things. Unless there is a more ideal workflow (like merging this and then you creating a new PR or something)

…

On Wed, Mar 7, 2018 at 5:34 PM, Amberley ***@***.***> wrote: Exactly. The problem we're solving is handling data. The tool is GraphQL :) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4375 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Ae9o2lglX5mcHMzPHVFepw5pXa5iv0nYks5tcIqsgaJpZM4Sdn84> .

[m-allanson]

Hey @shannonbux does this still need to go in, or was the work covered in your other recent PRs?

[amberleyromo]

@shannonbux these changes don't touch what we discussed today (some minimal in the intro). I think go ahead and merge, and we'll just do fresh changes from there.

[shannonbux]

Thanks everybody!

[gatsbybot]

Deploy preview for using-drupal ready!

Built with commit 97c2757

https://deploy-preview-4375--using-drupal.netlify.com