Home

Audience
Contributors

Contributing

• Styleguide - documentation around how the source code should be styled.
• Accessibility

Generic Functionality

HelixUI should be built in a way that any component can be use in any web application. As such, you should avoid implementing any business logic (no API calls, no permission/authorization logic, no URLs, etc.) into new features.

Semantic Versioning

<Major>.<Minor>.<Patch>[-<Revision>]

• Major: Breaking Change
  • A developer will need to modify their application code to consume new APIs.
• Minor: New Feature
  • Library assets should be backward-compatible with existing application code.
  • A developer may need to modify their application code to address bug fixes shipped alongside new features.
• Patch: Bug Fixes
  • A developer may need to modify their application code to address a correction in the library APIs.
• Revision: same-day bug fix (optional)
  • A developer may need to modify their application code to address a correction in the library APIs.

Reference

NOTE: these should be moved to proper API docs at some point.

• Position Utility
• Writing Documentation
• Custom Layouts

Bootstrap Theme

The Helix theme of Bootstrap 3 was meant to be a stepping stone in the evolution of HelixUI. It has fallen out of sync with official Helix specifications. We strongly recommend that consumers avoid using the Bootstrap theme.

• Helix Bootstrap Theme (CDN): DEPRECATED - Will be removed from CDN shortly after release of HelixUI v1.0.0.