Roadmap

Chukfi CMS — Feature Roadmap

Features discussed and prioritized for future implementation.

What else can we implement from Bun? They currently offer their Runtime, Package Manager, Bundler, Test Running… and now Bun Image. (https://bun.com/docs/runtime/image)
Check to see if these actually fit into our tech stack before implementing. This would be great if it could replace Cloudflare Image Compression.

A way to define environment-specific settings (staging vs prod API URLs, feature flags) without hardcoding.
Fits naturally as a Settings sub-section and pairs well with your draft preview work.

Full attendee management for events — dependent on public user authentication and payment processing being established first.

Public-facing registration flow with customizable per-event fields (built on Form Builder foundation)
Attendee authentication — public user accounts separate from admin users (requires its own auth system)
Payment processing integration (Stripe or similar) for paid/ticketed events with fee tiers and promo codes
Registrations inbox per event: attendee list, check-in status, CSV export
Automated confirmation and reminder emails via the newsletter plugin’s email providers
Capacity limits and waitlist management

A review queue so authors can submit content for editorial sign-off before it goes live.

New post status: in_review (sits between draft and published)
Authors can only move records to in_review; editors/admins can approve (→ published) or reject (→ draft with a note)
In-app notification badge for editors when reviews are pending
Rejection notes stored in a review_notes column

Basic traffic and engagement metrics surfaced inside the admin without a third-party dashboard.

Use Cloudflare Workers Analytics Engine to record page views via a lightweight GET /api/track?path=... pixel
Dashboard page: top content by views (7d/30d), subscriber growth over time, form submission volume
No PII collected — only path + date + rough geo (country)

Translate collection records into multiple languages while keeping them linked as variants of the same content.

New locale column on supported collections; composite unique key (slug, locale)
Language picker in the record editor to switch between or create locale variants
API: GET /api/posts?locale=fr returns locale-specific records, falls back to default locale
Locale list configured in Settings (e.g. en, fr, de)

Drag-and-drop tree of links (internal pages or external URLs) outputting a navigation JSON structure for the frontend to consume.

Array-type field where each item is a group of sub-fields (e.g. a “sections” array on a page, each section having heading + body + image).