The Multi-Site Content Challenge
Running one blog is straightforward. Running ten is a coordination nightmare. You need separate content calendars, different SEO strategies for each audience, unique templates, and per-domain analytics -- all while maintaining consistent publishing velocity.
AIKit solves this with its multi-site content orchestration layer -- a single plugin dashboard that manages blogs across 10-plus domains with per-site configuration, shared templates, and centralized analytics.
How Multi-Site Works in AIKit
AIKit's architecture treats each site as an isolated content namespace within the same Astro + D1 backend. Each site gets:
- **Its own D1 database namespace** -- content, revisions, SEO metadata are scoped per site
- **Independent publishing queues** -- per-site cron schedules and rate limits
- **Separate plugin configurations** -- different LLM providers, templates, and workflows per site
- **Shared asset library** -- images, templates, and layouts are reusable across sites
Site Configuration
```yaml
per-site AIKit configuration
site:
domain: devtools-blog.example.com
locale: en
timezone: America/Chicago
publishing_schedule: "0 6,12,18 * * 1-5"
plugins:
- auto-blog-seo
- webhook-subscriptions
- analytics
llm:
provider: openrouter
model: openai/gpt-4o
temperature: 0.7
templates:
blog_post: templates/technical-tutorial.hbs
release_notes: templates/release-notes.hbs
```
Content Calendar Orchestration
The multi-site dashboard includes a unified content calendar that shows all sites' posts in a single view. You can filter by site, category, status, or date range:
| Site | Posts This Week | Published | Drafts | Next Scheduled |
|------|-----------------|-----------|--------|----------------|
| devtools-blog | 12 | 8 | 4 | 2026-05-12 |
| crypto-docs | 7 | 5 | 2 | 2026-05-13 |
| marketing-site | 15 | 10 | 5 | 2026-05-14 |
| api-reference | 5 | 4 | 1 | 2026-05-15 |
Each calendar entry shows title, status, scheduled time, and which queue position it occupies. Drag-and-drop rescheduling reorders the publishing queue per site.
Template Inheritance
Instead of duplicating templates across sites, AIKit supports a template inheritance hierarchy:
1. **Global templates** -- shared across all sites (boilerplate, headers, footers)
2. **Site templates** -- override specific sections per domain
3. **Content-type templates** -- per-format templates (blog post, tutorial, release notes, case study)
This inheritance model means updating a global template automatically propagates to all 10 sites, while each site keeps its unique voice through targeted overrides.
Cross-Site Content Repurposing
One of the most powerful features is cross-site repurposing. When you publish a technical deep-dive on your main blog, AIKit can:
1. **Summarize** it into a shorter post for your marketing site
2. **Translate** it for your international domains (en to ja, ko, zh)
3. **Reformat** it as a tutorial for your docs site
4. **Schedule** each version according to that site's publishing calendar
This turns every piece of source content into 3-5 derivatives across your content network -- multiplying your output without multiplying effort.
Analytics Aggregation
The dashboard aggregates metrics across all sites:
- **Total content output** -- posts published per day/week/month across all sites
- **Channel distribution** -- which sites get the most engagement
- **Topic overlap** -- identify where content clusters overlap between sites (merge or differentiate)
- **SEO score trends** -- per-site average SEO score over time
- **Generation costs** -- per-site LLM token consumption and cost tracking
Real-World Setup
A typical multi-site deployment looks like:
```bash
Deploy a new site under AIKit management
npx emdash create-site new-project-docs \
--domain docs.newproject.com \
--template technical-docs \
--locale en \
--schedule "0 8 * * 1-5"
The site inherits global templates, gets its own queue,
and appears in the unified dashboard immediately.
```
The entire process -- from running the command to having the first post scheduled -- takes under 5 minutes.
Key Takeaways
- AIKit's multi-site orchestration manages 10-plus blogs from one dashboard
- Template inheritance eliminates duplicate work across sites
- Cross-site repurposing turns one source post into 3-5 derivatives
- Unified analytics gives you site-level and aggregate content metrics
- New sites deploy in under 5 minutes with per-site configuration
For teams managing multiple audience-facing properties, AIKit's multi-site orchestration transforms a coordination nightmare into a single-dashboard workflow.## The Content Network Strategy
Why run multiple blogs instead of one? Three reasons:
1. **Audience segmentation** -- Developer docs belong on docs.yourproduct.com, marketing content on blog.yourproduct.com, community content on community.yourproduct.com. Each audience has different expectations for tone, depth, and format.
2. **SEO domain authority** -- Separate domains build independent authority profiles. A deep technical tutorial on one site does not dilute the marketing-focused keyword strategy on another site.
3. **Content velocity scaling** -- Running 10 blogs at 3 posts per week gives you 30 posts per week total output. The aggregate content volume builds total brand presence faster than any single blog could.
Queue Management Across Sites
Each site gets its own publishing queue with independent priorities. The dashboard shows a unified view with site filters:
```
QUEUE OVERVIEW (10 sites, 45 queued posts)
devtools-blog (5 queued, 2 due today)
[1] How to Deploy... ⏰ 2026-05-09 08:00
[2] API Versioning Guide ⏰ 2026-05-09 12:00
[3] Architecture Deep Dive ⏰ 2026-05-10 06:00
crypto-docs (12 queued, 0 due today)
[1] Smart Contract Audit ⏰ 2026-05-11 06:00
[2] Yield Farming Guide ⏰ 2026-05-11 12:00
```
Queue items can be reordered, rescheduled, or reassigned to a different site with drag-and-drop.
Localization Workflow
For international audiences, AIKit automates translation across your site network:
1. Write the source post in English on the primary site
2. Flag it for localization
3. AIKit generates localized versions (ja, ko, zh, es, pt) using your configured LLM
4. Each localized version enters its site's queue at the appropriate timezone
5. Translations maintain the original's SEO metadata structure and keyword targeting
This workflow turns a single English post into 5-6 localized posts across your international sites with no translation team needed.
Cost Efficiency
Multi-site does not mean multi-cost. AIKit's shared infrastructure means:
- One Cloudflare Workers instance serves all sites
- One D1 database with namespaced tables (no per-site DB cost)
- Shared LLM API key across all sites (pooled token usage)
- One wrangler configuration for all deployments
The cost to add a 10th site is near-zero marginal infrastructure expense. Your only scaling cost is LLM token consumption for content generation.
Getting Started
To add a new site to your AIKit network:
1. Add the domain to your AIKit dashboard
2. Choose a template theme (tech, crypto, marketing, docs)
3. Configure per-site publishing schedule and LLM model
4. Approve the default template set for your content type
5. Start the queue -- AIKit generates and schedules the first batch automatically
The entire onboarding takes under 10 minutes for a new site.
Conclusion
AIKit's multi-site orchestration turns content network management from a coordination burden into a scalable, single-dashboard operation. Whether you are running 3 blogs or 30, the architecture scales linearly with near-zero marginal cost.