Content calendar
Plan upcoming articles, set reminders, and turn ideas into Blog drafts when you are ready to write.
Content publishing
Editors publish ahead of the next frontend release.
Give editors a path to create, review, publish and measure content. Deliver it through a frontend that stays yours.
Editorial states
Draft, schedule, publish, unpublish and archive with explicit workflow actions.
Authors
Maintain author profiles and connect them to published work.
Taxonomy
Organise the archive with categories and tags that have public routes.
Media and galleries
Manage project media metadata and build ordered post galleries.
Discovery
Expose featured posts, search and filtered author, category and tag feeds.
Measurement
Review post, category and tag performance plus search behavior.
Editorial clarity
Editors get a workflow. Developers get structured content.
Webtools keeps authoring and delivery separate. Editors stay out of frontend code. Your frontend stays free of a theme system.
- Content calendar with planned dates and reminders
- Rich post content with SEO metadata
- Explicit publish and schedule actions
- Featured posts and storefront search
- Public author, category and tag feeds
- Subscriber collection and unsubscribe flow
- Project-scoped permissions for content teams
Publish with control
A clean path from idea to audience.
- 01
Plan the calendar
Capture upcoming article ideas with a brief, planned date and optional reminder before anyone opens the editor.
- 02
Structure the archive
Create authors, categories and tags so content stays navigable as the library grows.
- 03
Prepare and publish
Turn a calendar item into a draft, attach media and a gallery, complete SEO fields, then publish now or schedule it.
- 04
Deliver and learn
Render the content in your frontend, surface search and featured posts, then review engagement in the dashboard.
Beyond publishing
Connect content to the rest of the Project.
The same workspace collects subscribers, receives customer enquiries, connects a verified domain and records project activity. Enable commerce later; the content system stays in place.
- Newsletter subscribers and status management
- Typed public enquiries for relevant calls to action
- Search-query logs and content analytics
- Media reused across posts and product records
- Member roles and effective permissions
- A Storefront API that serves multiple frontends
Start with one project
Publish once. Deliver it on the frontend you choose.
Bring catalogue, content, customer activity and project controls together behind it.