SiteForge CMS Planner
bharat-krishna-verma/kanopi-cms-blueprint
Terraform para estratégia de conteúdo: planeje sites com IA como arquitetura-como-código
Ver no GitHubFerramenta CLI com IA para gerar blueprints inteligentes de projetos web, transformando requisitos em arquiteturas de conteúdo estruturadas e versionáveis. Integra-se com APIs Claude/OpenAI para sugerir modelos de conteúdo, taxonomias e dependências técnicas, gerando diagramas Mermaid e documentação multi-formato.
Instalação
npx convez-ai bharat-krishna-verma/kanopi-cms-blueprint1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Gerar roadmaps de desenvolvimento web estruturados a partir de briefings
- Modelar arquiteturas de conteúdo com sugestões inteligentes de taxonomias
- Visualizar dependências técnicas e caminhos críticos em projetos CMS
- Exportar planos em múltiplos formatos (HTML, PDF, GraphML, CSV) para stakeholders
- Versionr planos de projeto em Git como código vivo e colaborativo
Veredito

Plugin maduro para equipes que precisam rigor arquitetural em projetos CMS. Combina IA com versionamento Git para transformar planejamento em artefato vivo—ideal para agências Kanopi e times que valorizam specs documentadas. Curva de aprendizado moderada, valor alto para projetos complexos.
README
A tradução para o português deste README ainda está na fila.
SiteForge CMS Planner – Intelligent Web Development Planning Suite
SEO Title: SiteForge CMS Planner: AI-Powered Web Development Planning Tool for Modern Teams
Download & Quick Start
🧭 What Is SiteForge CMS Planner?
Imagine having a master architect for your website who never sleeps, never forgets a requirement, and can speak every CMS language fluently. That's SiteForge CMS Planner—an open-source, AI-augmented command-line tool that transforms chaotic web development planning into a precise, repeatable, and collaborative blueprint machine.
Inspired by the planning capabilities of Claude Code plugins and the Kanopi CMS ecosystem, SiteForge CMS Planner reimagines project initialization as a living document generator. Instead of static spreadsheets or scattered Notion pages, you get a version-controlled, machine-readable, human-beautiful planning artifact that evolves with your project.
🎯 Core Philosophy: The Blueprint Approach
Every great website starts with a blueprint. But most planning tools treat blueprints as static PDFs—dead documents the moment they're created. SiteForge CMS Planner treats planning as code: modular, testable, automatable, and AI-ready.
Think of it as Terraform for content strategy—you define your site architecture, content types, user journeys, and technical requirements in structured configuration files, then let the planner generate interactive roadmaps, dependency graphs, and exportable specifications.
🔧 Technology Stack
| Component | Technology | Purpose |
|---|---|---|
| Core Engine | Node.js + TypeScript | Cross-platform runtime with type safety |
| AI Integration | OpenAI GPT-4o, Claude API (3.5 Sonnet/Opus) | Intelligent suggestion, content modeling, dependency detection |
| Data Serialization | YAML, JSON, Markdown | Human-readable configuration with machine-parsable structure |
| Visualization | Mermaid.js | Dynamic diagram generation for architecture, workflows, and timelines |
| CLI Framework | Commander.js + Inquirer | Professional command-line experience with guided wizard |
| Output Formats | HTML, PDF, GraphML, CSV | Multi-format export for stakeholder audiences |
| Version Control | Git-native | Automatic branching strategies for planning phases |
🧩 Feature Deep-Dive
1. 🤖 AI-Assisted Content Architecture
SiteForge doesn't just store your content types—it suggests them. Feed it a project brief, and the planner uses OpenAI or Claude APIs to analyze your requirements and propose:
- Optimal content models (pages, posts, custom post types)
- Taxonomy hierarchies (categories, tags, custom taxonomies)
- Field types with validation rules
- Relationships between content entities
- SEO metadata structures
2. 🔗 Dependency Graph Generator (Visual)
Web development is a web of dependencies. SiteForge CMS Planner automatically generates Mermaid dependency diagrams that show:
- Critical path for page templates
- Content type inheritance chains
- API endpoint dependencies
- Third-party plugin/module integration order
- Deployment sequence optimizations
graph TD
A[Project Brief] --> B[Content Audit]
A --> C[Technical Requirements]
B --> D[Content Model]
B --> E[Taxonomy Structure]
C --> F[Theme Selection]
C --> G[Plugin Ecosystem]
D --> H[Template Architecture]
E --> H
F --> H
G --> H
H --> I[Development Sprints]
I --> J[QA Milestones]
J --> K[Deployment]
K --> L[Post-Launch Optimization]
3. 🌐 Multilingual Content Strategy (Built-in)
Modern websites are global. SiteForge CMS Planner includes first-class multilingual support:
- Language matrix generation (source → target languages)
- Translation workflow automation (human or AI-assisted)
- Hreflang tag planning
- Locale-specific content variations
- Right-to-left (RTL) language warnings
4. 📱 Responsive UI Planning
Not just for themes—the planner generates breakpoint-specific content visibility rules, responsive image strategy, and device-optimized user flows.
5. 🕒 24/7 Automated Planning Mode
Use with CI/CD pipelines. Run siteforge plan --continuous to set up a background watcher that:
- Monitors your project directory for changes
- Recalculates dependency graphs on every file save
- Sends Slack/Teams notifications for critical path changes
- Automatically archives outdated planning artifacts
6. 🧪 QA-Ready Test Plan Generation
Every site needs testing. SiteForge CMS Planner converts your content models into automated QA checklists:
- Content completeness checks (required fields, character limits)
- Cross-browser rendering scenarios
- Accessibility compliance (WCAG 2.2 AA/AAA)
- Performance budget calculations
📋 Example Profile Configuration
Create a .siteforge-profile.yaml file in your project root:
# siteforge-profile.yaml
project:
name: "Acme Global Redesign 2026"
client: "Acme Corporation"
start_date: "2026-01-15"
target_launch: "2026-06-30"
budget_hours: 3200
team_size: 8
cms:
engine: "drupal" # options: drupal, wordpress, strapi, payload, custom
version: "11.x"
multilingual: true
source_language: "en-US"
target_languages:
- "es-MX"
- "fr-FR"
- "de-DE"
- "ja-JP"
content_model:
core_types:
- name: "Landing Page"
fields:
- { name: "hero_title", type: "string", required: true, max_length: 120 }
- { name: "hero_subtitle", type: "text", required: false }
- { name: "call_to_action", type: "link", required: true }
- { name: "body_content", type: "wysiwyg", required: true }
seo:
focus_keyword: true
meta_description_max: 160
og_image_required: true
taxonomies:
- name: "Product Category"
hierarchy: 3
multi_select: false
ai_assist:
provider: "claude" # options: openai, claude, gemini
model: "claude-3-5-sonnet-20241022"
suggestion_style: "concise"
auto_approve_threshold: 0.85
integrations:
slack_webhook: "${SLACK_WEBHOOK_URL}"
jira_project: "ACME2026"
github_issues: true
figma_tokens: "${FIGMA_ACCESS_TOKEN}"
🖥️ Example Console Invocation
Basic Project Initialization
# Start a new planning session
npx siteforge-cms-planner init --profile ./my-project.yaml
# Or use the interactive wizard
npx siteforge-cms-planner wizard
AI-Augmented Planning
# Generate content model from a project brief
siteforge plan --brief ./docs/requirements.md --ai-suggest
# Output: ./planning/content-model.yaml + ./planning/dependencies.mmd
Export & Share
# Export for stakeholder review
siteforge export --format html --output ./planning/report.html
# Generate markdown for documentation site
siteforge export --format markdown --split-by-type
Continuous Planning Mode
# Watch directory and auto-update
siteforge plan --watch ./src --continuous --notify-slack
🖥️ Emoji OS Compatibility Table
| Operating System | CLI Support | GUI (Experimental) | AI Features | Mermaid Export |
|---|---|---|---|---|
| 🐧 Linux (Ubuntu 22.04+) | ✅ Full | ✅ Partial | ✅ Full | ✅ Full |
| 🍏 macOS (14 Sonoma+) | ✅ Full | ✅ Full | ✅ Full | ✅ Full |
| 🪟 Windows 11 (WSL2) | ✅ Full | ❌ Not Available | ✅ Full | ✅ Full |
| 🪟 Windows 11 (Native) | ✅ Full | ❌ Not Available | ⚠️ Requires WSL2 | ✅ Full |
| 🐳 Docker Container | ✅ Full | ❌ Not Available | ✅ Full | ✅ Full |
| 🍏 macOS (Intel, 12+) | ✅ Full | ✅ Partial | ✅ Full | ✅ Full |
| 🐧 Linux (ARM64) | ✅ Full | ❌ Not Available | ✅ Full | ✅ Full |
Note: GUI mode on Windows requires WSL2 for AI API proxying. All CLI features work natively across platforms.
🔑 SEO-Friendly Keyword Integration
SiteForge CMS Planner is built with search discovery in mind—both for your projects and for the tool itself. The planner generates:
- SEO metadata templates for every content type (Open Graph, Twitter Cards, Schema.org)
- Keyword clustering suggestions based on content structure
- Internal linking blueprints that follow silo architecture principles
- Breadcrumb navigation patterns optimized for crawl efficiency
- XML sitemap priority scoring based on content hierarchy
When you run siteforge plan --seo-audit, it cross-references your content model against 2026 SEO best practices, including Core Web Vitals alignment, entity-based optimization, and EEAT framework compliance for Google's search guidelines.
🤖 OpenAI API & Claude API Integration
Dual-Engine Intelligence
SiteForge CMS Planner is provider-agnostic by design. You can use:
| Provider | Models Supported | Best For |
|---|---|---|
| OpenAI | GPT-4o, GPT-4 Turbo, GPT-3.5 Turbo | Rapid content generation, large-scale taxonomy suggestions |
| Anthropic Claude | Claude 3.5 Sonnet, Claude 3 Opus | Nuanced architecture decisions, safety-first content modeling, complex dependency analysis |
Configuration Example for Dual AI
ai_assist:
primary_provider: "claude"
primary_model: "claude-3-5-sonnet-20241022"
secondary_provider: "openai"
secondary_model: "gpt-4o"
fallback_strategy: "auto" # automatically switch if primary fails
budget:
monthly_token_limit: 5000000
alert_at_percentage: 80
custom_prompts:
- role: "system"
content: "You are a senior technical architect specializing in Drupal and Next.js integration. Focus on decoupled architectures."
API Key Setup
# Set your AI provider keys (choose one or both)
export OPENAI_API_KEY="sk-..."
export ANTHROPIC_API_KEY="sk-ant-..."
# Or use the .env file
echo "OPENAI_API_KEY=sk-..." >> .env
echo "ANTHROPIC_API_KEY=sk-ant-..." >> .env
The planner automatically selects the best model for each task—Claude for architectural reasoning, GPT-4o for content generation—and falls back gracefully if one provider is unavailable.
🌟 Key Features Summary
| Feature | Description | Availability |
|---|---|---|
| ⚡ Responsive UI Planning | Generate breakpoint-specific content rules, responsive image strategies, device-optimized workflows | 2026 Q1 |
| 🌍 Multilingual Support | Full language matrix, translation workflows, hreflang planning, RTL detection | 2026 Q1 |
| 🕐 24/7 Customer Support | Automated CI/CD mode with Slack/Teams notifications, issue creation, plan archiving | 2026 Q2 |
| 🔒 Offline-First Architecture | All AI features work with local fallback models (via Ollama) | 2026 Q2 |
| 📊 Resource Allocation Engine | Auto-calculates developer hours per content type, based on complexity | 2026 Q1 |
| 🔄 Git-Integrated Versioning | Every plan change is a commit; diff any two versions of your architecture | 2026 Q1 |
| 🧪 Automated QA Checklist | Generate test cases from content models, export to TestRail or CSV | 2026 Q2 |
| 🎨 Figma Token Import | Sync design tokens (colors, spacing, typography) directly into your content model | 2026 Q3 |
| 📈 Performance Budget Calculator | Predict page weight and load times based on content model complexity | 2026 Q2 |
🚀 Getting Started (Quick Reference)
-
Install globally:
npm install -g siteforge-cms-planner -
Initialize a new project:
siteforge init --name "MyProject" -
Configure your AI provider:
siteforge config set ai.provider claude siteforge config set ai.key YOUR_KEY_HERE -
Generate your first planning artifact:
siteforge plan --brief "Corporate website with blog, careers, and product catalog" -
Visualize dependencies:
siteforge diagram --format mermaid | pbcopy # macOS siteforge diagram --format mermaid > dependencies.md
⚠️ Disclaimer
SiteForge CMS Planner is an open-source tool provided "as is", without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose, and noninfringement.
The AI-generated suggestions (from OpenAI, Claude, or other providers) should be reviewed by a qualified human professional before implementation. The authors and contributors assume no responsibility for any errors, omissions, or damages arising from the use of this software or its outputs.
This tool does not store or transmit your API keys—all credentials remain on your local machine. However, please review your AI provider's data usage policies regarding content sent to their APIs.
Use in production environments is at your own risk. Always maintain backups of your planning data.
📄 License
This project is licensed under the MIT License – see the LICENSE file for details.
📦 Download & Installation
Package Managers
# npm (recommended)
npm install -g siteforge-cms-planner
# yarn
yarn global add siteforge-cms-planner
# pnpm
pnpm add -g siteforge-cms-planner
Docker
docker pull kanopi/siteforge-cms-planner:latest
docker run -it --rm -v $(pwd):/workspace kanopi/siteforge-cms-planner init
Built for teams who build the web. SiteForge CMS Planner – because great websites aren't born, they're architected.