Boundless is primarily developed by Evan Scott and Enigma's FE team. The CHANGELOG will be updated with each release and a git tag will be created.
If a component deviates from the spec outlined in its documentation (README.md), then that errant behavior is a bug.
Create a new entry in the repository issue tracker.
The Boundless team is committed to fixing verified bugs as soon as possible. Depending on the complexity of the issue, a release to address it could be cut the same day, but time must be allowed to add regression testing and verify the fix in all supported browsers.
Boundless addresses a specific need: to normalize behavior in common UI patterns and provide easily-composable components that do not require significant rewriting or tweaking for every new project.
If you have an idea for functionality or a new component to be added to the kit, we welcome such requests in our issue tracker. If the request is too specific to your project's implementation, it will likely be rejected.
Community pull requests (PRs) will only be considered for bug fixes and performance-related improvements.
At this time, we are not accepting PRs for new components or functionality. Instead, follow the feature request procedure and, if it makes sense, we will include it in our roadmap.
Commit messages should be written in present tense. For example, "Replace Foo with Bar" instead of "Replaced Foo with Bar".
Adhere to the 70/120 rule when writing commit messages:
- The title line should be no more than 70 characters
- Separate the title and body with an empty newline
- The commit message body can be as long as you want, hard-wrapped at 120 characters per line
Example:
Site / README updates
Adding User Interface Guideline suggestions (thanks Eris!) and tweaking
some of the styles and demos.
Boundless follows a variant of the AirBnB JS style guide. Lint your submission via npm run lint
to ensure that you are in compliance before sending a PR.