A lean CMS built to stay understandable
AdAstro exists for teams that want modern publishing infrastructure without the usual plugin sprawl, hidden coupling, or day-one feature overload. It starts with a solid core and grows in deliberate steps.
Why it is built this way
AdAstro started from a simple question: what would a modern publishing stack look like if operational clarity mattered as much as features? The answer was not to add everything. It was to make the core strong enough that a team could launch with confidence before enabling more complex workflows.
That is why the base product focuses on posts, pages, reusable sections, media, SEO, themes, localization, setup guidance, and migration tooling. Those are the pieces most editorial teams need first, and they are also the parts that become difficult to maintain when they are spread across disconnected plugins and external services.
Advanced capabilities can still exist in the repo without being forced into production on day one. If your team is not ready to own AI output review, comment moderation, or newsletter operations, those features can stay off until you are.
What stays in the core
The core should be enough to launch and run a serious publishing site.
Content and structure
Posts, pages, reusable sections, taxonomy, scheduling, and SEO metadata live in one consistent model.
Media and delivery
Uploads, metadata, CDN-aware delivery, and editorial media workflows are built into the same admin surface.
Setup and operations
Hosted setup, deployment guidance, auth configuration boundaries, and migration tooling are treated as product surfaces, not afterthoughts.
Optional feature packs
These capabilities ship with the repo, but they should only be enabled when the workflow behind them is ready.
AI Suite
Draft assistance, editorial QA, image generation, AI alt text, locale-aware narration, provider controls, and usage reporting for teams that can review output well.
Comments
Public comments with moderation tooling for teams that are ready to own community response and abuse handling.
Newsletter
Subscriber capture, campaign management, provider-backed delivery, and unsubscribe handling once email operations are part of the publishing workflow.
Operating principles
AdAstro is shaped by a few rules that keep the system from drifting into a hard-to-own platform.
Fail closed on sensitive paths
Setup, auth, admin actions, and privileged automation are designed to prefer a hard stop over silent risk.
Keep public pages lean
The public site should stay fast because the architecture is disciplined, not because someone keeps adding rescue plugins later.
Let complexity arrive in phases
Features that require ownership, moderation, or quality review stay optional until the team has the process to support them.
What AdAstro is not
Positioning it correctly makes the project more credible.
Not a hosted SaaS CMS
AdAstro is a forkable stack you deploy and operate, not a closed platform you rent.
Not a plugin marketplace
The goal is a coherent codebase with feature contracts, not a growing dependency web of unrelated extensions.
Not pretending to be a huge enterprise suite
The project is maintained by one developer, with AI used as leverage for implementation, documentation, and regression work. That strength depends on staying honest about scope.
Want the deeper product walkthroughs?
The article library covers editorial workflow, performance, AI usage, and the origin story in more detail than this page should.
Browse articles