> All templates, forms etc in the database also means you don't have a file lying around. Which means you cannot point your favorite text editor you it. That w

> All templates, forms etc in the database also means you don't have a file lying around. Which means you cannot point your favorite text editor you it. That was indeed true, but no more. With the advent of themes from v4.7.0, you can export template files and CSS to the filesystem for version control or whatever purposes you require. Textpattern still reads all its template/tag data from the database by default, but you can import/export the files however you see fit to suit your workflow, or bundle them up to share/reuse. Auto-sync of files<->database during development is supported by a plugin. The reason it's not a core feature is because we've separated the live/dev workflow in the latest version so you can iterate/revamp/update/overhaul your sites on the live server without needing to do the separate staging server dance. See: https://textpattern.com/weblog/424/the-end-of-the-web-development-staging-server https://textpattern.com/weblog/424/the-end-of-the-web-develo... There are so many ways this could be utilised, we felt it better to leave workflow decisions to the site admin. > It would be great if SQLite was officially supported, or anything but MySQL We support MySQL clones such as MariaDB and Percona. Not tried any others yet. PDO support is on the list, but it requires some refactorisation internally so we've been putting it off!