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

.org redesign: homepage [design] overview issue #9526

Closed
2 of 8 tasks
amberleyromo opened this issue Oct 29, 2018 · 16 comments
Closed
2 of 8 tasks

.org redesign: homepage [design] overview issue #9526

amberleyromo opened this issue Oct 29, 2018 · 16 comments
Assignees
Labels
stale? Issue that may be closed soon due to the original author not responding any more. status: blocked This issue/PR can't be solved at the moment and shouldn't be closed/merged

Comments

@amberleyromo
Copy link
Contributor

amberleyromo commented Oct 29, 2018

(This issue is design-focused, not implementation-focused.)

The below represent the components of the homepage that require design attention for the .org redesign effort:

Blocked / Requires discussion

Shelved

We will create separate issues for these subtasks as they are tackled.

@fk these capture the way you described separating out this work. Does this still look accurate?

@fk
Copy link
Contributor

fk commented Oct 29, 2018

Will break down components in a minute and add a couple.

Also just stumbled upon https://github.com/ichabod-cranes/mansion/issues/987, should we close this one?

@amberleyromo
Copy link
Contributor Author

Closing ichabod-cranes/mansion#987 -- thanks!

@fk
Copy link
Contributor

fk commented Nov 5, 2018

Argh, so much for "in a minute". Sorries! :(

@fk fk added the type: design label Nov 5, 2018
@fk
Copy link
Contributor

fk commented Nov 6, 2018

@amberleyromo @greglobinski Finally got to create bespoke issues for all work, and updated the issue description above.

While I'm treating those sections as separate components that do not require a certain order, it would be nice to define the content order. Apart from "hero content", IMO the positions/priority of "Features" and "Diagram" are pretty much set in stone—I'm wondering what your thoughts are in regards to the order of

  • Ecosystem
  • Blog section
  • Community / Creators
  • Showcase

@amberleyromo
Copy link
Contributor Author

I think this is more of a content / IA question for @shannonbux and @lindaleebumblebee. First blush I agree with the way you've ordered it in your comment.

@fk
Copy link
Contributor

fk commented Nov 6, 2018

IMO "Showcase" could also go well with the "Used by" section in case we wanted to move the latter out of the "hero/above the fold" section (as suggested in #9752).

Apologies again for doing the issue work only now.
Old enough now to know better.

@shannonbux
Copy link
Contributor

I will have all my UX research interviews on the homepage done by next Friday (Nov 16th) so will have a more informed opinion by then! As with every project, this is a balance of meeting two goals:

  • internal goals (what path do we want people to go down)?
  • user goals (what path do users want to go down and how can we help them get there?)

My first impression is that this is a lot for a homepage to fit and I'd recommend a simpler setup instead of trying to fit it all. I don't know who the ultimate decision maker is here so take this for what it's worth :)

@amberleyromo
Copy link
Contributor Author

If that's the case, then I think community/creators should drop off. We have a lot more work to do in that domain defining it before we can (in an informed way) think about how it might relate to the homepage.

Also, @KyleAMathews -- I think it was you who first suggested pulling featured Gatsby sites into the homepage. Do you have an opinion about where it goes? Now that I'm remembering that, I'm thinking it should go more to the top.

@fk
Copy link
Contributor

fk commented Nov 6, 2018

My first impression is that this is a lot for a homepage to fit and I'd recommend a simpler setup instead of trying to fit it all.

@shannonbux I can follow your concern.
FWIW here's the internal issue comment in which I initially captured the content of the homepage and I'm still basing the sections listed above on.
I did abandon this "more compact" version of the layout (trying to fit multiple subsections into row columns) because I felt it was too "dense."

@shannonbux
Copy link
Contributor

shannonbux commented Nov 6, 2018 via email

@lindaleebumblebee
Copy link
Contributor

I'm starting to lose track of all these issues about the .org homepage (a github newbie), but I will say that the 'above the fold' is the most important section of the homepage and we should keep it simple and have 1 CTA (with a possible 2nd CTA). Since our audience is developers, the 'Get Started' CTA still makes sense as we want people to build Gatsby sites!

@amberleyromo amberleyromo changed the title .org redesign: homepage design .org redesign: homepage [design] overview issue Nov 7, 2018
@fk
Copy link
Contributor

fk commented Nov 9, 2018

I just realized that we might want to tease the store on the new homepage!? 😓

@lindaleebumblebee
Copy link
Contributor

It's not a bad idea to let visitors of .com know that we have a swag store, but if we go that route, I'd like to keep it as very much a lower priority CTA (at the bottom of the page or elsewhere) as we need to keep the main CTA(s) above the fold. Thanks for thinking of it Flo!

@marisamorby
Copy link
Contributor

This is blocked on research and messaging, so I will pass this over once we are on to next steps.

@marisamorby marisamorby assigned marisamorby and unassigned fk Jan 9, 2019
@marisamorby marisamorby added status: blocked This issue/PR can't be solved at the moment and shouldn't be closed/merged no triage and removed no triage labels Jan 9, 2019
@gatsbot gatsbot bot added the stale? Issue that may be closed soon due to the original author not responding any more. label Feb 12, 2019
@gatsbot
Copy link

gatsbot bot commented Feb 12, 2019

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here.

If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

Thanks for being a part of the Gatsby community! 💪💜

@gatsbot
Copy link

gatsbot bot commented Feb 23, 2019

Hey again!

It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it.

Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m HUMAN_EMOTION_SORRY. Please feel free to reopen this issue or create a new one if you need anything else.

Thanks again for being part of the Gatsby community!

@gatsbot gatsbot bot closed this as completed Feb 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale? Issue that may be closed soon due to the original author not responding any more. status: blocked This issue/PR can't be solved at the moment and shouldn't be closed/merged
Projects
None yet
Development

No branches or pull requests

6 participants