[EPIC] v3.0 .org redesign (Community page)

[shannonbux]

Who will own this?

Area of Responsibility:

• Admin
• Cloud
• Customer Success
• Dashboard
• Developer Relations
• OSS
• Ecosystem
• Learning
• Marketing
• Sales

Responsibility	Contributor(s)
AoR owner	@amberleyromo
Domain owner	@KyleAMathews
Project manager	@name
Tech lead	@name
Contributors	@fk

Summary

We want to make room for www.gatsbyjs.org to grow. We're going to create a landing page for these items that need room and call them "Community" in the top nav bar:

• Code of Conduct
• How to Contribute
• SWAG (is this where it fits?)
• How to Connect (Gatsby Days and other meetups)

How will this impact Gatsby?

Domains

gatsbyjs.org

Components

List the impacted Components here

Goals

1. increase the number of page views to gatsbyjs.org
2. increase the number of contributions to gatsbyjs.org
3. increase how much people use Gatsby to build sites

How will we know this epic is a success?

This project is successful once the user can statements below are true.

User Can Statement

User can...

• find each community item from the homepage
• know how to contribute
• buy swag from the Gatsby store

Metrics to Measure Success

• Same as goals above

Additional Description

@fk has developed designs in #7544 (comment)

And has sketched out the pros of the second solution:

1. Priority nav plus More button with drop-down menu
2. Reduce nav items to 5, reorganize them and create landing pages

What are the risks to the epic?

• We could make pages harder to find
• We could lose people who like the current navigation

What questions do we still need to answer, or what resources do we need?

• How much planning future .org changes are required in order to not go down the wrong road?

How will we complete the epic?

We will complete the issues as they are assigned below this Epic.

How else could we accomplish the same goal?

We could go with @fk's first option:

1. Priority nav plus More button with drop-down menu

[marisamorby]

@amberleyromo: This will be affected by the OSS Process Automation work in issue #9634 for OSS Dashboard Spec. We'll want to be sure to consider the OSS Process as we're building out this page.

[gatsbot]

Old issues will be closed after 30 days of inactivity. This issue has been quiet for 20 days and is being marked as stale. Reply here or add the label "not stale" to keep this issue open!

[gatsbot]

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!