chore(blog): add blogpost about gatsbyjs.org redesign #12337
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
marcysutton
suggested changes
Mar 8, 2019
| @@ -0,0 +1,139 @@ | |||
| --- | |||
| title: ".org Prototype Test Blogpost" | |||
There was a problem hiding this comment.
I think this title could be improved a bit, perhaps something like "Prototype Testing for Gatsby.org"?
| - What is the purpose of the homepage? | ||
| - How do we know if we’re succeeding in that purpose? | ||
|
|
||
| It is important to the Gatsby community to solve these problems, because tons of new visitors come to the gatsbyjs.org homepage each month. 130,000 in January alone! We want to make sure we’re accurately representing Gatsby’s value there and helping more developers experience Gatsby’s value by clicking the “get started” button. |
There was a problem hiding this comment.
This would become a complete sentence with a colon instead of a period: "each month: 130,000 in January alone!"
|
|
||
| ### Review design requirements | ||
|
|
||
| We briefly reminded ourselves of what the current homepage looks like on mobile, and then review the following information on the requirements for redesigning the homepage: |
There was a problem hiding this comment.
Verb tenses should match if possible: then reviewed the following
|
|
||
| We left the prototype workshop with a few concerns that could be validated through testing: | ||
|
|
||
| - Logos of companies could turn off developers b/c it’s cliche and sometimes meaningless or they could provide social proof that world-class engineers use Gatsby. We’ll test this. Possibility is to combine the logos with case studies so they aren’t in the classic “logos floating on white space” design that most startups use. |
There was a problem hiding this comment.
Love the self-awareness here. 👍
|
|
||
| ### Settled concerns: | ||
|
|
||
| "Install Gatsby" is an more specific call to action, so better than “Get Started” probably. |
There was a problem hiding this comment.
Better than "Get Started" how? It seems like the inverse is true for .org homepage messaging...?
|  | ||
| [Move diagram above card and change explanatory text](https://github.com/gatsbyjs/gatsby/pull/12236) | ||
|
|
||
| And then refined those changes by changing the headline and subheadline. |
There was a problem hiding this comment.
This should be a complete sentence: "Then we refined those changes by modifying..."
|
@marcysutton great feedback! since @shannonbux is out I took the liberty of incorporating it into the PR, and will approve and merge so it can go live on Monday morning! |
calcsam
changed the title
|
Thanks all for the help getting this merged while I was offline on a plane
and then out of town. Appreciate it! I went back in a couple days ago to do
minor polishing.
…On Sat, Mar 9, 2019 at 1:52 PM Sam Bhagwat ***@***.***> wrote:
***@***.**** approved this pull request.
Great post @shannonbux <https://github.com/shannonbux>!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#12337 (review)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ae9o2hrwveZHJZVgvQtH4eEIkvDBmdT8ks5vVC00gaJpZM4bfswG>
.
|
|
Thanks!
…On Sat, Mar 9, 2019 at 2:07 PM Sam Bhagwat ***@***.***> wrote:
Merged #12337 <#12337> into master.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#12337 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/Ae9o2tU5dh_aswi_a3C3MnR2GTPE_64pks5vVDCGgaJpZM4bfswG>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When is a good date to publish this one, @lindaleebumblebee?