Download the PHP package tavp/cms without Composer
On this page you can find all versions of the php package tavp/cms. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package cms
TAVP CMS
A content management system built on the TAVP Stack. WordPress-familiar, Voyager-style admin, thin and fast — with pluggable storage, headless API, and a feature set that works out of the box.
Version: 0.5.2 — ZeroVer
0.MINOR.PATCH.
What it is
Thin. Light. Not bloated. TAVP CMS is a standalone CMS that runs on top
of tavp/core only. No external auth packages, no admin panel packages, no
component libraries required — it ships with its own implementations.
| Concern | Implementation |
|---|---|
| Foundation (routing, ORM, Volt) | tavp/core |
| Admin auth (OTP email) | AdminAuth (built-in) |
| Admin UI | PHP templates + Tailwind (built-in) |
| BREAD CRUD | BreadManager (built-in) |
| Storage | DatabaseStore or FlatFileStore (pluggable) |
Pluggable storage
You are not locked into a database. Choose the driver in config/cms.php:
- database — WordPress/Voyager style, single
contentstable with JSON data column - flatfile — Statamic style, Markdown + YAML front matter per record
The rest of the CMS behaves identically regardless of driver.
Features (what actually works)
Core
- BREAD — generic Browse/Read/Edit/Add/Delete for any content type
- Pages & Posts — built-in content types with fields, validation, slug generation
- OTP passwordless admin — email code via Mailpit/SMTP, session-based
- Content revisions — automatic version history on every save, one-click rollback
- Full-text search — search across all content types from admin UI and API
- Headless REST API — full CRUD + pagination + search + taxonomy via
/api/cms - Taxonomy — categories (hierarchical) + tags (flat), attached to any content type
- SEO sitemap — auto-generated
sitemap.xmlfrom published content - RBAC-lite — email-to-role mapping with wildcard permission patterns
- Cached storage — read-through cache (file or in-memory) wrapping the storage layer
- Field validation — server-side rules (required, min, max, email, unique, etc.)
- Blog routes —
/blog,/blog/{slug},/category/{slug},/tag/{slug} - Theme system — Volt templates under
/themes, active theme configurable
Planned (not yet implemented)
- Media library admin UI (storage layer ready in
src/Media/) - Menu builder admin UI (tree logic ready in
src/Menu/) - Settings admin UI (storage layer ready in
src/Settings/) - Scheduled publishing (
cms:publishCLI) - Per-record SEO meta fields
Requirements
- PHP 8.3+
- Phalcon 5.16+ (compiled extension)
tavp/core^1.1
Install
Quick start
1. Configure
2. Run migrations
3. Admin
Visit /admin, sign in with your allowed email via OTP.
4. Headless API
Content types
Define content types in config/cms.php or use the admin BREAD UI:
Admin (Voyager-style)
Login at /admin with an allowed e-mail — a one-time code is sent to it
(Mailpit/SMTP). From there you manage content (BREAD CRUD), taxonomy,
media, menus, users, SEO, analytics, and contact-form messages.
Building the admin (self-hosted, no CDN)
Admin templates in resources/admin/ are styled with Tailwind CSS. To avoid
the render-blocking Google Fonts / jsdelivr / browser-JIT Tailwind CDN, ship
static assets. In your application webroot carry:
| Asset | Path (webroot) |
|---|---|
| Tailwind build | public/assets/admin.css |
| Font faces | public/assets/fonts.css + /fonts/*.woff2 |
| Alpine | public/js/alpine.min.js |
| EasyMDE | public/js/easymde.min.js, public/css/easymde.min.css |
| Prism + languages | public/js/prism*.min.js, public/css/prism-tomorrow.min.css |
Build the Tailwind file from source while scanning the CMS admin templates:
(The tailwind.admin.config.js + resources/css/admin.css live in the
consuming app — see the tavp-web-id repo for the reference setup.)
Structure
API Reference
All endpoints require a Bearer token via Authorization: Bearer <token>.
| Method | Endpoint | Description |
|---|---|---|
| GET | /api/cms/types |
List content types |
| GET | /api/cms/{type} |
Browse records (paginated) |
| GET | /api/cms/{type}/{id} |
Read a record |
| POST | /api/cms/{type} |
Create a record |
| PUT | /api/cms/{type}/{id} |
Update a record |
| DELETE | /api/cms/{type}/{id} |
Delete a record |
| GET | /api/cms/search?q={query} |
Full-text search |
| GET | /api/cms/taxonomy/{type} |
List taxonomy terms |
| POST | /api/cms/taxonomy |
Create a taxonomy term |
| GET | /api/cms/{type}/{id}/revisions |
Revision history |
| POST | /api/cms/{type}/{id}/rollback/{ts} |
Rollback to revision |
License
MIT
