Simple Form Materialize

Simple Form Materialize is here to help generate your configuration needed to using simple form with materialized styles. This gem is not intended to live forever in your gemfile. It must be in your gemfile to load the resources needed from the generator. Below in the installation section will detail out which gems to install for all to work.

Change Log



  • Upgrade circleci to support 2.6 ruby testing
  • Drop 2.2 support for ruby
  • Overall Repo updates


  • Update Ralities support to be upto version 7 (#7)



  • Upgrade circleci to support 2.5, 2.4, 2.3, and 2.2 ruby testing



  • Various Enhancements to the repo (#4)


  • Fix Input upload (#3)
  • Resolve dependency Issues (#1)


  • Fix ReadMe typos



  • Generate Materialize Configuration for Simple Form
    • Javascript File
    • Simple_form components File
    • Simple_form configuration File

Add these lines to your application’s Gemfile:

# Required gems so you don't have to add files manually
gem "materialize-sass"
gem "material_icons"
gem "simple_form"

gem "simple_form_materialize", "~>1.2.0"

simple_form, materialize-sass and material_icons are required in your gemfile to enable the views to generate without error and in the proper style.

< rails g simple_form_materialize:install

This will generate your two config files and javascript file of initializers

├─ app/
|   └─ assets/
|       └─ javascript/
|           └─
└─ config/
    └─ initializers/
        ├─ simple_form_components.rb
        └─ simple_form_materialize.rb

First and for most thank you for taking the time to look to contribute to Simple Form Materialize, any help is apprciated to make Simple Form Materialize better and stronger!

Code of Conduct

This project and everyone participating in it is governed by the Simplecov Material Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to

How can I Contribute

Reporting Bugs

Before submitting a bug report

This section guides you through submitting a bug report for Simple Form Materialize. Following these guidelines helps maintainers and the community understand your report 📝, reproduce the behavior 💻 💻, and find related reports 🔎.

Before creating bug reports, please check this list as you might find out that you don’t need to create one. When you are creating a bug report, please include as many details as possible. Fill out the required template , the information it asks for helps us resolve issues faster.

Note: If you find a Closed issue that seems like it is the same thing that you’re experiencing, open a new issue and include a link to the original issue in the body of your new one.

Suggesting Enhancements

This section guides you through submitting an enhancement suggestion for Simple Form Materialize, including completely new features and minor improvements to existing functionality. Following these guidelines helps maintainers and the community understand your suggestion 📝 and find related suggestions 🔎.

Before creating enhancement suggestions, please check this list as you might find out that you don’t need to create one. When you are creating an enhancement suggestion, please include as many details as possible. Fill in the template , including the steps that you imagine you would take if the feature you’re requesting existed.

Code Contributions

Looking to contribute to Simplecov? You can look for any tickets tagged with help-wanted

Pull Requests

The process described here has several goals:

  • Maintain Simple Form Materialize’s quality
  • Fix problems that are important to users
  • Engage the community in working toward the best possible Simple Form Materialize Interaction
  • Enable a sustainable system for Simple Form Materialize’s maintainers to review contributions

Please follow these steps to have your contribution considered by the maintainers:

  • Follow all instructions in the template
  • After you submit your pull request, verify that all status checks are passing
    What if the status checks are failing? If a status check is failing, and you believe that the failure is unrelated to your change, please leave a comment on the pull request explaining why you believe the failure is unrelated. A maintainer will re-run the status check for you. If we conclude that the failure was a false positive, then we will open an issue to track that problem with our status check suite.

While the prerequisites above must be satisfied prior to having your pull request reviewed, the reviewer(s) may ask you to complete additional design work, tests, or other changes before your pull request can be ultimately accepted.

Additional Notes

Issue and Pull Request Labels

This section lists the labels we use to help us track and manage issues and pull requests.

GitHub search makes it easy to use labels for finding groups of issues or pull requests you’re interested in. For example, you might be interested in opening an Issue or perhaps opening a pull request. To help you find issues and pull requests, each label is listed with search links for finding open items with that label in Simple Form Materialize. We encourage you to read about other search filters which will help you write more focused queries.

Type of Issue and Issue State

Label Name Description
enhancement Feature requests.
bug Confirmed bugs or reports that are very likely to be bugs.
question Questions more than bug reports or feature requests (e.g. how do I do X).
feedback General feedback more than bug reports or feature requests.
help-wanted The Simple Form Materialize team would appreciate help from the community in resolving these issues.
more-information-needed More information needs to be collected about these problems or feature requests (e.g. steps to reproduce).
needs-reproduction Likely bugs, but haven’t been reliably reproduced.
blocked Issues blocked on other issues.
duplicate Issues which are duplicates of other issues, i.e. they have been reported before.
wontfix The Simple Form Materialize team has decided not to fix these issues for now, either because they’re working as intended or for some other reason.
invalid Issues which aren’t valid (e.g. user errors).
new Tagged on Issues that are new and have not been reviewed.
tech debt Items to clean up / refactor / restructure

Pull Request Labels

Label Name Description
work-in-progress Pull Requests which are still being worked on, more changes will follow.
needs-review Pull Requests which need code review, and approval from maintainers.
under-review Pull Requests being reviewed by maintainers.
requires-changes Pull Requests which need to be updated based on review comments and then reviewed again.
needs-testing Pull Requests which need manual testing.

© Chiefpansancolt & Christopher Pezza All rights reserved.