-
Notifications
You must be signed in to change notification settings - Fork 6
Roadmap
Ryan Johnson edited this page Aug 24, 2018
·
4 revisions
- Document contribution guidelines
- glossary of terms (if needed)
- core maintainers
- review process
- etc.
- Initialize Wiki to document standards
- naming
- file structure
-
tabs vsspaces - etc.
- Prototype dev pipeline (How will a contributor add/update features?)
- React storybook (or equivalent library) to easily publish component documentation
- New features must be functional
- Unit tests are highly recommended (if possible)
- API consistency is recommended (if possible)
- As inconsistencies are identified, discussions will take place to define standards.
- Finalize dev pipeline
- Automated Unit Testing (TravisCI, CircleCI, etc.)
- Enzyme? Jest? Jasmine? Other?
- Automatic Linting (eslint)
- Continuous Deployment
-
master
branch for edge/unpublished,release
for stable/published
-
- Automated Unit Testing (TravisCI, CircleCI, etc.)
- Build component for every HelixUI element that emits custom events
- see "Custom Elements" docs for HelixUI
- React components built for all CSS-based HelixUI components (e.g., radio, select, pagination, etc.)
- Full list TBD