An administration interface for editors
Everything is done in the browser, with nothing to install on your computer. A role based access control system decides who may read, create, edit and publish what. There is no built-in limit to the amount of content or the number of users; heavy traffic only needs more hardware. Editors can also work directly on the public site, without the administration interface at all.
Three steps to publish
- Find your place. Content lives in a tree. Browse it, use bookmarks, recent items or search. Move, copy or publish the same content in several locations.
- Create and edit. Pick a location and create content with the online editor.
- Publish. One click publishes, or starts a workflow that sends the draft for approval first, from a single approver to a chain of contributors, translators and editors.
Editing tools included
- Version control with rollback
- Drafts and preview
- Scheduled publishing and unpublishing
- Translation management
- Related content and embedded objects
- Automatic image conversion and scaling
- Readable URLs, for example example.com/products/exponential
- Link checking
- Trash with restore
Templates and channels
Once published, templates and stylesheets decide how content looks in each place: a teaser on the front page, the full article in its folder. Because content is separate from design you can redesign without touching the content, and reuse the same content in other channels: PDF export, feeds and the REST API.
Content types out of the box
- Content: articles, news, folders, information pages, products, comments, links.
- Media: images in all common formats, including WebP, plus audio and video.
- Documents: PDF and office documents.
Need something else? Define your own content classes, or extend the system with the development framework.
More publishing features
- Forums, galleries and blogs
- Polls, feedback and contact forms
- Newsletters and notifications
- Tip a friend and print views
Fast pages
- Caching at every level: rendered views, compiled templates, settings, roles and permissions are cached, so very little code runs per request.
- Static cache: fully static pages can be served without starting PHP.
- Scaling out: clustering for several web servers and database replication with read servers.
- Exponential Velocity: the bundled application server keeps the framework loaded between requests.
Publish from day one
There is nothing to assemble before your editors start: the publishing tools above come with the installation, and the request shield protects the login and forms from the first request.* Compare that with systems where publishing starts with plugins or programming: See the comparison and sources.
*No system is immune to every attack; Exponential ships the request shield and secure defaults so most common attacks are blocked before they reach your site, and 7x keeps it patched.