hirebrian.ai

Under the hood

The system behind
an AI-ready website.

An AI agent makes the edit. GitHub records the change. Cloudflare publishes the approved website.

By Brian Carrion · Updated

  1. 01 / Request

    AI agent

    A typed or spoken change becomes an edit to the website files.

    Codex or Claude Code
  2. 02 / Record

    GitHub

    A branch holds the changes and their history for review.

    Business-owned repository
  3. 03 / Review

    Preview

    A separate version makes the result visible before approval.

    Check, refine, approve
  4. 04 / Publish

    Cloudflare

    Approved production changes trigger a build and deployment.

    Live website + custom domain
Source code lives in GitHub. The live website is hosted on Cloudflare. Approval separates an edit from a public release.

What gets built

The deliverable is both the website and the system that lets an AI agent maintain it: the repository, authorized agent connection, project instructions, preview setup and automatic publishing workflow.

Website
Responsive pages, reusable styles, migrated content, metadata, redirects and analytics.
Editing system
A connected coding agent with access to the correct project, build instructions and a repeatable update process.
Release system
GitHub change history, a review branch, preview deployment and a Cloudflare production connection.
Handoff
Client-owned accounts, hands-on training, written instructions and a video guide.

The standard package covers up to 30 pages, a two-week turnaround and one integration, such as a contact form. Extra integrations are $499 each. Custom applications and more extensive business workflows are scoped separately.

The AI-to-GitHub connection

The agent needs authorized access to the website’s actual files. A local workflow opens a working copy of the GitHub repository; a connected cloud workflow works with the repository through the agent’s supported GitHub integration. Account permissions determine which repositories and actions are available.

ChatGPT can help write and plan updates. Applying them requires a connected editing workflow, such as Codex with GitHub access. Claude Code can read and edit project files, run checks and work with development tools. A normal chat or a read-only repository connection is not enough to publish changes.

Project instructions describe the file structure, approved business facts, visual rules, test commands and publishing process. Files such as AGENTS.md or CLAUDE.md keep those instructions alongside the project. Written instructions support the workflow; account permissions and branch rules enforce access.

The connection setup is the work: configuring existing agent, GitHub and hosting capabilities into a usable system. It does not require inventing a new AI model or a proprietary hosting platform.

From edit to live website

  1. Request. A clear instruction identifies the page and the change. Voice input can be used when supported by the chosen app or device.
  2. Edit and check. The agent changes files on a working branch, runs the project’s checks and saves a commit. Git records the revision and its differences.
  3. Preview. The configured Cloudflare Pages integration builds a preview from the branch. A pull request groups the proposed changes for review.
  4. Approve. The preview is checked for content, layout, links and any affected integration. Approval authorizes merging that revision into the configured production branch, commonly main.
  5. Deploy and verify. Cloudflare detects the production change, runs the configured build and publishes the successful output. The live page is checked after deployment.

Cloudflare’s GitHub integration provides automatic deployments and branch controls. The build command, output directory, runtime version and production branch are configured for the actual site. A static HTML site and a framework-based site can have different build requirements.

Routine edits can appear immediately in a local preview. Public updates still depend on approval and the hosting build completing; deployment is not guaranteed to be instantaneous.

Accounts, hosting and domain

The business owns the GitHub repository, Cloudflare account and domain registration. GitHub stores source code and version history. Cloudflare serves the deployed website on its network. Domain records connect the public address to the hosting project; HTTPS is configured for that domain.

Domain registration can stay with the existing registrar. Existing email records must be preserved or deliberately migrated during the hosting change. Hosting, domain renewals, AI subscriptions and paid connected services have their own ongoing costs and provider limits.

Forms, integrations and data

One integration is included, for example a contact form connected to an agreed delivery destination. Each extra integration is $499. Third-party subscription and usage fees are separate from the implementation fee; the exact connection is agreed before development.

A static website does not itself process email or store customer records. A form service, API or server-side function handles that work. Form submissions belong in the selected service, not in the GitHub repository.

Private API keys stay in server-side secret storage. Cloudflare Pages Functions supports secret bindings for server-side code. Browser JavaScript and generated HTML are public, so private values must never be embedded in the page or exposed through a build-time variable that gets bundled into client code.

Previews, permissions and recovery

Repository access is limited to the required project. Production permissions and supported branch protection rules are configured around the approval process. Availability of specific rules depends on the GitHub account, plan and repository settings; an agent instruction alone is not an enforced approval gate.

Cloudflare preview deployments have separate addresses and do not replace the live site. Preview URLs are public by default; Cloudflare Access can restrict them. Private customer data and credentials do not belong in an unprotected preview.

Git history preserves earlier source revisions. Cloudflare can roll back to a previous successful production deployment. After a rollback, the repository also needs the appropriate revert or repair so the next release does not reintroduce the problem. Website rollback does not restore external form data, databases or provider settings; those need separate recovery plans.

A working example

The Best Lesson Ever case study documents a move from WordPress and Elementor to local development, GitHub source control and Cloudflare publishing. It shows the kind of website and maintenance workflow this system supports.

For individual editing walkthroughs, read the ChatGPT and Codex guide, the Claude Code guide or the general website update guide.

A website with the update system included.

Up to 30 pages. Two-week turnaround. One integration included; extra integrations are $499 each. See the complete package.

Submit a website
Book a website consultation