Bloomineasy is an AI-first CMS starter project for people who want a real content management system without starting from a blank app or reaching for WordPress by default.
It is built with Next.js 15, React 19, Convex, Better Auth, Tailwind CSS, the Vercel AI SDK, and OpenAI. It gives you a working admin CMS, a public content site, an authenticated publishing API, a structured taxonomy engine, widgets, SEO tooling, translations, and AI-assisted editorial workflows.
Search is not an afterthought. Bloomineasy is built with SEO in mind from the content model upward: taxonomy-aware URLs, canonical metadata, Open Graph controls, hreflang-ready translations, sitemap routes, article digests, and internal link suggestions are all part of the starter.
The short version: Bloomineasy is the WordPress of AI. A CMS built for AI-assisted publishing, by AI-assisted development, and designed from the start for search visibility.
A CMS Built For AI-Assisted Publishing
Most CMS products were designed around manual publishing. An editor logs in, writes an article, chooses a category, fills in SEO fields, and presses publish. That workflow still matters, and Bloomineasy supports it.
But modern content operations often include agents, scripts, imports, AI-generated drafts, translation workflows, and external publishing tools. Bloomineasy is designed for that reality.
Articles can be created through the admin interface or pushed in through the Content11 Articles API. Once content lands in the CMS, AI can help categorize it, suggest where the taxonomy needs to grow, translate it, and find internal linking opportunities.
That matters for SEO because the CMS is not just storing posts. It is helping shape the information architecture, URL structure, language variants, metadata, and internal links that search engines and readers use to understand a site.
The system does not treat AI as a novelty feature. AI is part of the editorial workflow.
Technology Stack
The Admin CMS
Bloomineasy includes a real admin area, not just a set of public templates. The admin sidebar covers articles, categories, internal links, widgets, widget sitemap, sitemap, form submissions, settings, API keys, and users.
The article editor supports the details a working content site needs: title, slug, body, excerpt, status, subtitle, language code, read time, publication date, featured images, thumbnail images, social images, author details, SEO title, SEO description, canonical URL, Open Graph overrides, taxonomy selection, version history, widget assignments, and internal link suggestions.
The article table supports bulk actions, including status updates, deletion, and bulk AI categorization. That matters when you are importing a content library or publishing generated articles at scale.
What It Includes
Structured Taxonomy
Bloomineasy uses a three-level taxonomy: categories, sectors, and sub-sectors.
That structure powers more than admin organization. It creates search-friendly, human-readable public URLs such as:
/category/sector/sub-sector/article-slugThe taxonomy system includes create, update, delete, reorder, full hierarchy queries, stats, backfills, and path resolution. It also connects directly to the AI categorization workflow, so imported content can become part of a coherent SEO structure instead of sitting in a flat blog archive.
AI Categorization
When an article is created or edited, Bloomineasy can analyze the article and assign it to the best category, sector, and sub-sector from the existing taxonomy.
It returns confidence scores for each level and validates that the selected hierarchy is legal before anything is applied. If the existing taxonomy is not a strong fit, Bloomineasy can suggest new taxonomy items.
For larger libraries, Bloomineasy includes bulk AI categorization. You can categorize all uncategorized articles from the sitemap page or categorize selected articles from the articles table. Uncertain matches go through review instead of being blindly applied.
The CMS can tell you not only where an article belongs, but also when your current structure may be missing something.
AI Taxonomy Generation
Bloomineasy also includes an AI category wizard. Give it a natural language prompt describing the site, and it can generate categories, sectors, and sub-sectors.
You can choose the depth: categories only, categories with sectors, or a full three-level hierarchy. That makes the starter project much faster to adapt. A new clone can start with a domain-specific content structure rather than an empty CMS.
AI Translation
Translation is built into the API. Bloomineasy can translate an article into a target language, preserve HTML formatting, and store the translation separately from the source article.
The source article is never modified by the translation process. Translations can be created, updated, deleted, and toggled active or inactive. Translated pages get their own SEO metadata and can participate in hreflang workflows.
Internal Link Suggestions
Internal links are one of the most valuable parts of a growing content site, and one of the easiest to neglect. Bloomineasy uses article embeddings and GPT-assisted anchor text detection to suggest internal links between related articles.
Admins can review suggestions, accept them, dismiss them, bulk accept, or bulk dismiss. Accepted suggestions can inject links into article content, and the article versioning system can snapshot content around link operations.
This is one of the most SEO-focused parts of the product: Bloomineasy treats internal linking as an ongoing CMS workflow, not a manual cleanup task you remember after the content library is already too large.
That makes internal linking a reviewable workflow instead of a risky automated rewrite.
Widgets Across The Content Hierarchy
Bloomineasy includes a hierarchical widget system. Widgets can be assigned at the category, sector, sub-sector, or article level. They can render above content, below content, or in the sidebar.
Each assignment can use one of four modes:
This means a site can show different calls to action, forms, banners, snippets, calculators, or custom embeds depending on where the reader is in the content structure. A finance category could have one CTA, a mortgage sub-sector could have a calculator, and a specific article could override both.
API-First Content
The Content11 Articles API lets external systems create, update, and delete articles by slug. It supports API key authentication through either an x-api-key header or an Authorization bearer token.
API keys are created and revoked in the admin UI, stored as hashes, and audited when used. The API also supports preview links, hierarchical URL generation, URL clearing, translation, health checks, and cache revalidation.
This makes Bloomineasy practical for AI agents and content pipelines. You can build content somewhere else, then publish it into the CMS through a stable HTTP interface.
Built With SEO In Mind
Bloomineasy is built with SEO in mind, not just SEO fields added at the end. The CMS combines content structure, metadata, public routing, translations, structured data, sitemaps, and internal links so every article has a better chance of fitting into a search-friendly site architecture.
It includes the SEO basics a content CMS needs: dynamic metadata, SEO title and description fields, canonical URLs, Open Graph overrides, JSON-LD structured data, hreflang tags, a dynamic sitemap, a sitemap index, robots route, hierarchical canonical URLs, and article digests for efficient public listings.
It also includes Google Analytics and AdSense settings, social links, contact email, Twitter handle, and default Open Graph image configuration.
The point is not just to publish articles. The point is to publish articles into a CMS that understands structure, discoverability, metadata, and internal paths from day one.
Auth Built For A Private Admin CMS
Bloomineasy uses Better Auth with Convex. It is email/password only. There is no public sign-up. The first admin is created through a bootstrap script, and additional admins are provisioned from the admin user management page.
This is intentional. Bloomineasy is a CMS admin, not a public membership site. Public sign-up is rejected at both the Next.js and Convex boundaries, sign-in attempts are rate limited, and role management includes last-admin protection.
Built To Be Cloned
A major part of Bloomineasy is that it is a starter project. You clone it, install dependencies, create your Convex deployment, configure Better Auth, set your own Convex site URL, bootstrap the first admin, and begin customizing.
It includes guardrails for clone safety. Production builds reject stale Clerk environment variables because the project has moved to Better Auth. Server-backed write paths fail closed if the Convex site URL is missing or appears to point at the wrong deployment.
These details matter because a starter CMS should not accidentally leak into the template author's backend.
Who Bloomineasy Is For
Bloomineasy is useful for developers, AI builders, agencies, SEO teams, and founders who need a working content platform they can own.
It is especially useful when the content workflow includes imports, agents, translations, AI-generated drafts, internal link optimization, or multiple content verticals.
If you need a static blog, Bloomineasy may be more than you need. If you need a CMS foundation that already understands API publishing, taxonomy, AI workflows, SEO, widgets, and admin operations, Bloomineasy gives you the starting point.
Final Takeaway
Bloomineasy is a modern CMS starter for the AI publishing era. It gives you the admin, backend, API, auth, content model, AI workflows, widgets, SEO-minded site architecture, and clone-safety checks needed to launch a real content site quickly.
It is not trying to be another WordPress clone. It is trying to be the CMS starter you reach for when the content workflow starts with AI, APIs, and structured publishing.