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

[EPIC] v1.0 .org redesign - Ecosystems page #8768

Closed
2 tasks
shannonbux opened this issue Oct 3, 2018 · 0 comments
Closed
2 tasks

[EPIC] v1.0 .org redesign - Ecosystems page #8768

shannonbux opened this issue Oct 3, 2018 · 0 comments
Assignees

Comments

@shannonbux
Copy link
Contributor

shannonbux commented Oct 3, 2018

Who will own this?

Area of Responsibility:

Ecosystem

Responsibility Names
AoR owner @amberleyromo
Domain owner @amberleyromo
Project manager @marisamorby
Tech lead @amberleyromo
Contributors @fk @greglobinski @amberleyromo @marisamorby

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 "Ecosystem" in the top nav bar:

Review to see if these will be included

  • Community
  • Themes
  • Creator Showcase

Ecosystems Page Design

How will this impact Gatsby?

Domains

Primary: gatsbyjs.org
Secondary: starter library, plug-in library, .org docs

Components

  • Algolia (contextual search engine)

Goals

  1. Clean up navigation architecture
  2. Creating the landing page

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...

  • continue to find each ecosystem item through google search
  • continue to be able to bookmark and share each ecosystem item

Metrics to Measure Success
Metrics

  1. increase the number of page views for ecosystem tools
  2. increase the number of contributions to ecosystem tools
  3. increase how much people use our ecosystem tools (install a starter, hire someone to build a Gatsby site, etc.)

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

bild von ios hochgeladen

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants