Shipping fast.
Without pretending nothing changed.

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