After using Slim on the Fringe site and Jade in a handful of wireframing sites, some devs on the team wanted to try the templating engine in their project. With a little magic from Sinatra and some extra weekend time, the Slim Gym was produced.
Leveraging CodeMirror, the micro app is designed to be an interactive sandbox for Slim. It's not bulletproof and easily chokes on large copy-and-pastes, but the scratchpad is the perfect place to get a grasp on the engine's quirks and delights.
After diving into syntax and "standards"—something that was never a concern as an independent freelancer—I fell into the wormhole of linters and automatic checking. There were so many linters available, but there was no unified way to use them. After hacking with Rails-less Ruby for a few weekends, I presented the project to FINE's technical director, and he approved the project as an official FINE initiative.
The command line allows supreme flexibility: linter-specific configuration is not lost, and more advanced front-end tooling (such as performance tests with phantomas) is also available.
Built out of necessity for FINE's workflow, I spun up a hubot instance and finagled Bitbucket's API to send a message to our Slack channel whenever a pull request is created, commented, declined, merged, updated, approved or unapproved. The package is available from the Hubot scripts organization.