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] v2.0 Plugin library #7612

Closed
1 of 9 tasks
shannonbux opened this issue Aug 24, 2018 · 6 comments
Closed
1 of 9 tasks

[EPIC] v2.0 Plugin library #7612

shannonbux opened this issue Aug 24, 2018 · 6 comments
Labels
stale? Issue that may be closed soon due to the original author not responding any more.

Comments

@shannonbux
Copy link
Contributor

shannonbux commented Aug 24, 2018

Epic Template

Who will own this?

What Area of Responsibility does this fall into? Who will own the work, and who needs to be aware of the work?

Area of Responsibility:

Select the Area of Responsibility most impacted by this Epic

  • Community

  • Learning

  • Ecosystem

  • Gatsby Core

  • Enterprise

  • Design

  • Marketing

  • Company/Admin

  • Sales

    AoR owner @amberleyromo
    Domain owner @name
    Project manager @name
    Tech lead @name
    Contributors @name

Summary

This epic organizes enhanced sorting and filters for the plugin library.

How will this impact Gatsby?

Domains

Plugin Library

Components

List the impacted Components here

Goals

What are the top 3 goals you want to accomplish with this epic? All goals should be specific, measurable, actionable, realistic, and timebound.

  1. Increase usage of official plugins
  2. Measure baseline usability of library and improve baseline measurements (for example, on basic tasks like searching for a particular plugin). I'm guessing what we'll want to improve is the following: how easy it is to find a few official plugins, find more obscure plugins, choose between similar plugins, and author a plugin.
  3. Increase number of submitted plugins
  4. Decrease the number of incomplete READme files

How will we know this epic is a success?

Reaching the goals above!

User Can Statement

  • User can find the plugins they are looking for with fewer clicks than before
  • User can find installation instructions for any plugin
  • User can evaluate between similar plugins and choose one

Metrics to Measure Success

  • Same as goals above

Additional Description

We already did this work on the plugin library:

What are the risks to the epic?

The only things we give up are time devoted to the project. I can't think of any downsides yet.

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

We need to do 5 usability tests on the current plugin library to see how easy it is to find a few official plugins, find more obscure plugins, choose between similar plugins, and author a plugin.

How will we complete the epic?

Finish the issues and PR's in this epic.

How else could we accomplish the same goal?

Probably can't accomplish this any other way.

@shannonbux shannonbux self-assigned this Aug 24, 2018
@shannonbux shannonbux changed the title [EPIC] Plugin library phase 2 [EPIC] v2.0 Plugin library Aug 24, 2018
@calcsam calcsam added the type: documentation An issue or pull request for improving or updating Gatsby's documentation label Aug 29, 2018
@calcsam
Copy link
Contributor

calcsam commented Aug 29, 2018

@shannonbux what issues should fall under here?

@shannonbux
Copy link
Contributor Author

@calcsam updated with 3 issues that have been open for a long time, but not more than a stub still.

This isn't a high priority so I haven't taken the time to fill it out completely yet. Happy to do that if that's important.

@shannonbux shannonbux removed their assignment Sep 21, 2018
@shannonbux shannonbux removed type: documentation An issue or pull request for improving or updating Gatsby's documentation 🎯 Learning labels Sep 21, 2018
@gatsbot
Copy link

gatsbot bot commented Jan 14, 2019

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 gatsbot bot added the stale? Issue that may be closed soon due to the original author not responding any more. label Jan 14, 2019
@gatsbot
Copy link

gatsbot bot commented Jan 25, 2019

This issue is being closed due to inactivity. Is this a mistake? Please re-open this issue or create a new issue.

@gatsbot gatsbot bot closed this as completed Jan 25, 2019
@amberleyromo amberleyromo reopened this Jan 25, 2019
@amberleyromo amberleyromo added not stale and removed stale? Issue that may be closed soon due to the original author not responding any more. labels Jan 25, 2019
@amberleyromo amberleyromo removed their assignment Dec 4, 2019
@github-actions
Copy link

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!
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

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

@github-actions github-actions bot added the stale? Issue that may be closed soon due to the original author not responding any more. label Dec 25, 2019
@github-actions
Copy link

github-actions bot commented Jan 4, 2020

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.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

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

@github-actions github-actions bot closed this as completed Jan 4, 2020
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.
Projects
None yet
Development

No branches or pull requests

6 participants