Shipping fast.
Without pretending nothing changed.

The calendar crossed the line from lightweight placeholder UI into something teams can actually plan work inside. Manual entries are easier to edit, source events are easier to inspect, and month view no longer hides crowded days behind guesswork.

• Clicking calendar events now opens a proper detail drawer instead of relying on browser prompts or redirect-only flows
• Manual events can be edited inline with richer fields like description, dates, all-day state, and color instead of just a title
• Month view now exposes crowded days more clearly with direct shortcuts into day view when events are hidden behind the two-item preview limit

MantleKit’s theme system now has more range at both ends: more visual variety for storefronts, and a cleaner mode-aware experience for teams who want a quieter default shell.

• Minimal now supports light, dark, and system mode with a native theme toggle in the shared shell
• Truffle landed as a premium dark editorial theme for richer storefront presentation
• Rebel joined the lineup as a harder black, white, and red storefront direction inspired by underground streetwear styling

Blog and CMS editing now feel much closer to a production publishing tool instead of a raw schema form. Content teams can tune search metadata, upload featured images directly, and manage richer post presentation without leaving the editor.

• CMS items now support SEO title and SEO description with a 160-character cap for cleaner search snippets
• Featured images can be uploaded or chosen inline from the editor instead of pasting raw asset URLs by hand
• Public blog metadata now actually respects those CMS SEO fields, so editorial changes carry through to the live site

MantleKit moved beyond a few hardcoded role names and into a real permission system. Teams can now create custom roles, assign them to members, and shape the dashboard around what each person should actually be allowed to do.

• Custom roles can now be created inside Teams with module-by-module permissions like CMS, Notes, Customers, Orders, and more
• Sidebar items and dashboard cards now grey out or disappear based on the active role instead of treating every logged-in user the same
• Direct page and API access now follows the same permission model, so guessed routes do not bypass the role system

The early setup flow is much less awkward now. New installs can claim the first admin account without manual SQL edits, and accounts can add TOTP-based two-factor authentication directly from settings.

• First-time installs now guide the initial authenticated user into an admin bootstrap flow instead of forcing a manual role promotion in Supabase
• TOTP-based two-factor authentication is available from account settings, with login and OAuth flows routing through a challenge screen when needed
• Protected routes now respect two-factor state, which makes the dashboard feel a lot more serious for real projects

MantleKit’s ecommerce layer is no longer just checkout plumbing. The dashboard now has a stronger operational spine for orders, customers, fulfilment, downloads, and the kind of admin workflows real projects need after launch.

• Orders gained a real dashboard view with fulfilment status, detail screens, and better operational follow-through
• Customers now have their own workspace, including notes, billing portal actions, and CSV exports for customer and order data
• Licence management and customer self-service now cover issued keys, download limits, purchase recovery, and account-level download access

MantleKit’s dashboard now helps teams prepare a project properly before launch, then flip the public site live or private without losing admin access behind the scenes.

• Project Health now checks environment setup, launch readiness, branding cleanup, and a real setup checklist instead of acting like a passive status widget
• Launch Mode can hide the public frontend behind a branded coming-soon page while keeping login, signup, and dashboard access available for admins
• Coming-soon pages now support richer copy, optional CTAs, and countdown timers so projects can launch with something intentional instead of a dead-end placeholder

Now that internal workspaces exist, MantleKit tightened the first wave of role boundaries so admins, managers, editors, and support users no longer all feel identical in the dashboard.

• Workspace management is now restricted to workspace admins instead of any dashboard user with team access
• Products are limited to admin and manager roles, while media uploads stay available to the content roles that actually need them
• Global controls like Launch and Comments now behave like platform-admin surfaces, and the sidebar/dashboard cards reflect those permissions more clearly

Comment moderation is no longer just hardcoded link rules (used to reject spam, swearing and links). MantleKit now ships a proper moderation inbox plus configurable review rules for different kinds of sites.

• New dashboard comments section with approve, reject, re-approve, and delete actions
• Configurable moderation rules for hold-all, links, profanity, rapid-fire posting, and hourly spam limits
• Rejected comments remain visible in the moderation queue so admins can safely review or restore them later

MantleKit’s dashboard now supports internal workspaces, scoped roles, and a real calendar layer for planning work across content, support, and operations.

• Teams can now be created, switched, invited into, and safely deleted with last-team protection
• AI, Kanban, tickets, forms, media, and CMS now scope to the active workspace
• Calendar ships with month, week, and day views plus manual events, Kanban dates, ticket follow-ups, and scheduled content

Refined the homepage copy, added a feature comparison table against ShipFast and MakerKit, and tightened pricing-led conversion paths.

• New comparison table focused on publicly documented built-in features
• Hero messaging updated to emphasize the full product surface area
• Sales CTAs now point more consistently toward pricing and theme preview flows

Frontend ticket intake now connects to a real admin triage flow instead of just a contact-style stub.

• Public support form creates tickets and initial customer messages
• Admin ticket inbox and ticket detail workflow added
• Internal notes, replies, status changes, and ticket metadata supported

The admin AI assistant now gets MantleKit-aware system context instead of behaving like a generic blank chatbot shell.

• Theme, enabled features, auth methods, and plan information are injected into the system prompt
• OpenAI, Anthropic, and OpenRouter flows all use the same MantleKit-aware prompt layer
• Answers are now much more grounded in the current project configuration

Dashboard protection now uses Supabase-backed admin roles rather than just treating any authenticated user as an admin.

• New profiles table with role support and auth user bootstrap trigger
• Dashboard and admin API routes now enforce admin-only access
• Robots disallow dashboard indexing by default

The website branch was simplified into a proper single-theme sales site instead of carrying around extra theme-switching clutter.

• Floating theme switcher removed
• Bold website branch trimmed to a clearer branded experience
• Theme preview moved into its own public preview flow

MantleKit moved further from a simple starter toward a fuller operating system for solo founders and agencies.

• Schema-driven CMS editor improvements for longer content workflows
• Form builder and media library surfaced as first-class product modules
• Kanban and dashboard tooling better reflected across marketing and pricing surfaces

The initial public Git history starts with a dense shipping sprint: pricing setup, support tickets, AI context, website UX work, and the split between the full product branch and the website sales branch.

• create-mantlekit tiering and 1.6.0 release prep landed in the first commit
• Support tickets, admin workflows, and public table hardening shipped the same day
• The website branch absorbed the full app feature set before being reshaped into a dedicated sales site

Before the visible shipping burst in April, the implementation plans and specs for the major systems were written in a concentrated design pass.

• Auth, database flag, MDX blog, and payments design docs landed on March 26
• Ecommerce and transactional email designs followed on March 27
• CLI stripper, support features, marketing site, and new theme planning rounded out the end of March

The earliest dated specs established MantleKit as a premium Next.js SaaS boilerplate with a theme system, a thin CLI stripper, and a wider product surface than typical launch kits.

• Initial design spec for the MantleKit product architecture was written
• Foundation plan for themes and shared layout architecture was documented
• The repo direction shifted toward a hybrid monorepo plus configurable buyer output

The project started as a planning and architecture push before any public Git history existed, focused on the product shape, tiering, and what would actually make MantleKit different from the usual starter kit.

• Core positioning around design quality plus broad built-in features took shape first
• Pricing tiers and feature gating were planned before implementation started
• The repo work that followed was driven by a pretty detailed roadmap rather than winging it