It's unreasonable to assume that all Titan applications will want to use a database. We should make this optional, and provide a clear signal on initialization of whether or not we're connecting to a database.

Get a basic website up and working using GitHub pages

I don't even know how to deploy the documentation site at the moment so there's some work to be done here.

We need a way to list the available migrations and see which of them have been applied.

Something like:

* migration-1
* migration-2
  migration-3

CI should test not just titan itself but also the example project[s]

Re-implement defcontroller with:

• policy
• presenter
• resource
• parser

Although I think templates are sort of a waste, we might as well provide a basic one to get people started.

Right now everything's tied to Postgres. That was good for my needs but not even slightly generalizable. Let's make things more general.

We should be able to instantly create migrations with an alias like:

lein new migration $migration_name

https://gist.github.com/venantius/295b73061fdde35e9a08728b08cf625d

See: weavejester/ragtime#100

This issue is here for tracking tactics for database migrations.

Right now we're pretty aggressive with migrations in the course of testing, which is an un-necessarily slow way of going about things. We could probably be much smarter by moving to a world in which migrations are run as a necessary pre-condition to tests and then only run during testing as necessary.