Contributing

Stay up to date on the development of Fuel UX and reach out to others in the community with these helpful resources.

• Before writing code, we suggest you search for issues or create a new one to confirm where your contribution fits into our roadmap.
• In lieu of a formal style guide, take care to maintain the existing coding style, including the following:
  • tabs
  • clarity over brevity
  • declarative markup
  • semicolons
  Be sure to add unit tests for any new or changed functionality. Lint and test your code using grunt.
• Read more about contributing to Fuel UX
• Please do not edit files in the dist directory, as we generate those files via grunt. Find source code in the respective js, less, and fonts directory.
• While grunt can run the included unit tests via PhantomJS, ensure that you run tests across a variety of browsers and environments. View the test page at https://localhost:8000/test/ in as many of the browsers listed in sauce_browsers.yml as you can before contributing.