Patchwork content management system and blogging platform built on Git and GitHub. It's a loose collection of applications, each meant to handle one piece of content management.
The current collection includes:
You only really need three pieces: a content repo, Thread, and Quilt. Once you have it set up, Thread reads the content repo, parses the markdown files, and updates a database, an IndexTank API-compatible search index, and uploads specified assets to an Amazon S3 bucket. Quilt then serves the content.
You can also set up a post-receive webhook on the content repo, so whenever you push new content to that repo, the resulting site served by Quilt automatically gets updated.
We hate web-based text editors. We like to use our own text editors. We also like Git and GitHub. For a content store, a simple directory structure with markdown files is simple and easy to understand. Storing content in a Git repo also offers the added bonus of version control for your content.
Why not just use Jekyll?
Jekyll is great! It was one of the inspirations for this project. But there are a few things we don't like about it:
- Static sites are fast and easy to understand, but somewhat inflexible.
- It's not easy to set up on a modern PaaS.
- The content is mixed up with code, configuration, and metadata, which makes collaboration less than straightforward.
We were kind of tired of large, monolithic frameworks. We wanted a logical separation of concerns that would allow us to switch out different pieces for different purposes.
We're @joebadmo & @davidkofahl. We're learning as we go.