Developers
Roadmap & limits
Timber is young (v1). Releases are numbered simply v1, v2, v3… Here's what it doesn't do yet, so you can decide with open eyes.
Current limits#
| Area | Limit |
|---|---|
| Users | Three roles (administrator, editor, read-only) — but no per-page permissions, "edit only my own posts", approval workflow or audit log |
| Storage | JSON files — comfortable to a few thousand records and modest write traffic |
| Concurrency | Last write wins if two tabs edit the same record |
| Revisions | No per-post history (only file-level backups when you edit data directly) |
| Media | Originals only: no thumbnails, srcset or WebP/AVIF conversion |
| Search | No on-site search |
| Comments | None |
| Languages | English admin and defaults; one language per site |
| Updates | Manual file copy; no auto-updater |
| Migration | WordPress only; posts and pages (not custom post types, comments or users) |
| E-commerce | Not a goal |
Where it's going#
Near term — polish and trust
- Installer hardening: an optional install key and an exposed-
data/check before writing anything. - A one-click updater with a pre-update backup.
- A test suite for storage, auth, routing, forms, installer and the migrator, run in CI.
- An image pipeline: resize on upload,
srcset, WebP, EXIF stripping. - Post revisions with an "undo".
Medium term — fuller
- More granular permissions (authors who edit only their own posts, approval workflow), two-factor sign-in and an audit log.
- On-site search.
- A static page cache for extreme speed.
- Install themes from a
.zip; more starter themes. - Custom content types declared in a schema file.
- A newsletter / email list.
Long term — scale
- An optional SQLite storage driver with a one-command migration from JSON.
- A small event/hook system so extensions don't edit core.
- Multilingual content and admin.
Principles that won't change#
No build step. No required third-party service. Everything the owner might change is a setting or record. A fresh install stays a single upload and a one-minute setup.
Want to help shape it? See Open source & contributing.