Code of Conduct
We welcome pull requests from everyone. By participating in this project, you agree to abide by the thoughtbot code of conduct.
We expect everyone to follow the code of conduct anywhere in thoughtbot's project codebases, issue trackers, chat-rooms, and mailing lists.
Administrate is a Rails Engine, but ships with everything needed to contribute and test new changes.
To maintain compatibility with multiple dependency versions, we use Appraisal.
Opening a PR
- Fork the repo,
./bin/setupto install the base dependencies and setup a local database,
- Run the test suite:
bundle exec rspec && bundle exec appraisal rspec,
- Make your changes,
- Push your fork and open a pull request.
A good PR will solve the smallest problem it possibly can, have good test coverage and (where necessary) have internationalisation support.
Running the application locally
Administrate's demo application can be run like any Rails application:
bundle exec rails s
This will start the application defined in
- The gem's source code lives in the
- The demo app is nested within
- The guides as seen at https://administrate-demo.herokuapp.com live
as Markdown files in the
Rails configuration files have been changed to recognize the app in the new location, so running the server or deploying to Heroku works normally.
With this structure, developing a typical feature looks like:
- Add tests in
- Implement a feature in
- Exercise the feature using the demo rails app (
This project uses:
- BEM-style CSS selectors, with namespaces
- SCSS-Lint, with Hound
- A variety of CSS units:
emfor typographical-related elements
remfor lengths related to components
pxfor borders, text shadows, etc.
vhfor lengths that should be relational to the viewport
Issues and PRs are split into two levels of labels, at the higher level:
feature: new functionality that’s not yet implemented,
bug: breakages in functionality that is implemented,
maintenance: to keep up with changes around us
…and then to more specific themes:
namespacing: models with a namespace,
installing: initial setup, first-run experience, generators,
i18n: translations and language support,
views-and-styles: how administrate looks and is interacted with,
dashboards: how administrate presents fields and displays data,
search: finding things through our models,
sorting: ordering things on dashboards,
pagination: how we handle lots of data in small chunks,
security: controlling data access through authorisation,
fields: new fields, displaying and editing data,
models: models, associations and fetching the underlying data,
documentation: how to use Administrate, examples and common usage,
dependencies: changes or issues relating to a dependency
See the security policy.
New releases (and the time period between them) is arbitrary, but usually motivated by a new Rails release or enough bug fixes or features that there's significant enough changes.
A new release involves cutting and pushing a new version to Ruby Gems and
then deploying that version of the example application and documentation. This
means that the demo application always matches the current release,
whilst the pre-release application will track current