Impact Theme

Impact is Responsive Blog with a dark background and blue accents. The project page says so plainly, and I have never seen a reason to soften it: same layout, same twelve block regions, same configurable jQuery Cycle slideshow, same sidebar handling. What changed was the palette and some styling on the header.

Releasing it as a separate project was the wrong call, and it is the clearest mistake in this catalogue. Responsive Blog already shipped two colour schemes; Impact should have been a third. Instead it became a second project node, a second issue queue, a second release cycle and a second set of installers to keep in step — all for a difference a settings form could have expressed. Every fix to the shared layout after May 2013 had to be applied twice or, more honestly, applied once and forgotten in the other.

That is exactly the failure mode white-label platform work is built to prevent. When a customer wants their own look, the answer cannot be a fork of the product, because the second fork is where your release process quietly dies. It has to be configuration served per tenant from one codebase — branding, palette, typography, assets — with a single deployment path underneath. I learned that on a free Drupal theme, which is a much better place to learn it than on a platform with paying tenants.

Nearly five hundred sites still run Impact, and it is still listed as maintained. It also only ever had one release, which is precisely what you would predict.