Where jekcms stands mid-2026 and where it is heading: editorial transparency, content-similarity protection, migration tooling, more themes — plus what we are exploring without promising, and what we are deliberately not building.
Where the Product Stands
JekCMS v1.5 manages 12 production sites and runs on shared hosting plans that cost $4-10/month. Shipped and in daily use: a WYSIWYG editor with first-class image editing, a guided content wizard, a content quality gate in front of every automated publish path with a full audit trail, complete revisions with snapshot restore, a WordPress importer built for large migrations, a built-in SEO analyzer, story highlights, web push and IndexNow, and a REST API with n8n integration.
What We Are Working On
- Editorial transparency: per-post source lists (emitted as schema citations), original-contribution notes, AI-usage disclosure, and YMYL flags — so a site can prove how its content is made.
- Content-similarity protection: the quality gate now measures body-level overlap with already-published posts and blocks near-duplicates before they hurt a site.
- Migration tooling: the WordPress import wizard keeps getting hardened on real, large sites — resumable runs, image handling, redirect safety.
- Theme catalog: more niche-specific themes, all driven by the same customizer schema.
- Commerce polish: smoother licensing, updates, and regional payment options for buyers.
Exploring — Not Promising
For decoupled frontends we are evaluating deeper headless support: a query interface that avoids over-fetching, webhook-driven rebuild notifications for static sites, an authenticated draft-preview API, and language-aware content delivery. These are explorations; they ship when they earn their place, not on a slide’s schedule.
What We Are NOT Building
Equally important is what we skip: no built-in e-commerce core, no page-builder bloat, no attempt to clone a 60,000-plugin ecosystem, and no hands-off “content factory” automation — publishing always stays behind a quality gate and your decision. A small product that does the publishing job extremely well beats a big one that does everything poorly.
