Web & CMS Builder

A goal-oriented workflow for web stacks, CMS projects and custom applications. Use the server state, project files and official documentation to plan a deployment—not a single generic install command.

Project inspection

Read source files, manifests and uploaded archives to identify the framework, runtime and required services.

CMS planning

Use relevant runbooks for WordPress, Drupal, Joomla and other documented CMS workflows. Check version requirements rather than assuming one recipe fits all.

Custom applications

Plan Python, PHP, Node.js or other stacks supported by the target host and tooling. Verify dependency installation before configuring a service.

Web & database setup

Inspect Nginx/Apache, application runtime, database accounts and document roots. Preserve unrelated websites and existing configuration.

Delivery & source control

Coordinate with Git workflows for a defined repository, branch and destination. Do not publish credentials or unrelated files.

Post-deployment evidence

Check the intended HTTP endpoint, service state and application logs; a successful package transaction alone is not a successful website.

Workflow

Inspect

Identify the project and the current host state.

Prepare

Resolve compatible runtimes, services and credentials.

Deploy

Apply the permitted files and service configuration.

Test

Verify the target URL, logs and intended application behavior.

Example prompts

@web01 inspect the attached project and identify its dependencies before changing the server.
@web01 deploy a test WordPress site to the agreed directory, preserve existing sites and verify its local URL.
@web01 diagnose why the Drupal article page returns 200 but the article body is missing.

Evidence

  • Project and dependency inventory
  • Deployment path and service configuration
  • HTTP and log checks
  • Unresolved setup or application errors

Prerequisites

  • An enrolled host with suitable OS privileges and package access.
  • A clear hostname, target directory and database plan.
  • Any required license, registry access, secrets or application-specific inputs.

Boundaries

CMS coverage is documentation-driven and extensible, not a model trained on every product. Licensed software, interactive installers or missing credentials can be real blockers. Production content must be backed up.