Home

kohactive Development Guidelines

git/GitHub

• To get started on a project, fork it to your account.
• Always branch and prefix with feature_, bug_, refactor_, or release_
• Submit PRs from your fork to the main repo on the kohactive account.
• Each PR should be reviewed & approved by at least 1 other team member.

Documentation

• There's no such thing as too much documentation.
• Use the wiki on the GitHub repo for documenting components and other in-depth app intricacies.
• Generated README's are fine and usually quite helpful, but make sure to add project specifics and keep it up-to-date.
• Use draw.io for diagraming app schematics. The file(s) should be saved to the corresponding repo in /docs.

Design

• Use Google fonts whenever possible
• Sketch

Front-End

• Manhattan grid
• .scss(some older projects may use .sass)
• Ember, Ember Data, Ember CLI <3
• .hbs(some older projects may use Emblem.js)
  • If you really dig, you'll find some HAML in older Rails apps
• Static hosting on S3

Back-End

• Rails
• Heroku
  • Use pipelines with automatic deployment & review apps
• Common Rails API w/users setup
• Sinatra Microservice Project Setup

WordPress

• We use Pantheon for hosting, and strongly recommend it for our clients to use.
• Projects start from our sage-but-better repo, which is well-documented.
  • If you find a lapse in the docs, update them and submit a PR.
  • Same goes for any code updates: make the updates and submit a PR for discussion.