nostalgic-css/NES.css

Make a roadmap!

Open

#166 opened on Dec 11, 2018

View on GitHub
 (15 comments) (5 reactions) (0 assignees)CSS (15,232 stars) (1,294 forks)batch import
discussionhelp wanted

Description

As @BcRikko said recently in #152:

Sorry, there is no roadmap. 😢

So I think we should change that! Let's discuss what other components we'd like to have added to the framework next. Once we have a list of components we want to add, we should create an issue for each component. Once that's done, we can add the good first issue label to each of them. That may encourage more contributors to come help us expand the framework.

So, here are the components that I'd like to see the most:

  • <input type="range" /> (as mentioned by @BcRikko in #152)
  • <code /> and <pre />
  • <dialog />
  • <kbd />
  • <meter />

@nostalgic-css/nes-css and other contributors, what else would you like to see added to NES.css?

Contributor guide

Tech stack
css
Domain
frontend
Issue type
research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
The issue proposes creating a roadmap by listing desired components for NES.css. The community has suggested components like <input type='range'>, <code>, <pre>, <kbd>, <meter>. The next step is to reach a consensus on components and create individual issues for each. Involved files are none; the discussion is in comments. Maintainers need to finalize the list and create good first issues.