How I set up a website that ChatGPT can edit

This website is deliberately simple.

It is a static site. The source code lives in Git, the content is mostly Markdown, and changes go through a review and deployment workflow.

The main reason I built it this way is that I can edit the website conversationally through ChatGPT, including from my phone.

I can ask for a change, review what was changed, leave comments, request another revision and decide whether it should go live without opening a code editor.

The basic setup

At a high level:

ChatGPT → Git repository → static site → deployment

The repository is the source of truth.

Instead of editing pages through an admin dashboard, the site is generated from source files: components, styles and Markdown.

ChatGPT can inspect and change those files.

So I can say:

Add a blog section to the website.

It can inspect the existing implementation first and make the change through version control.

I still get a diff to review before anything is accepted.

Why I didn’t use a CMS

I don’t need multiple editors, complex permissions or a publishing dashboard.

A blog post can just be a Markdown file:

title: "How I set up a website that ChatGPT can edit"
description: "How I maintain my website conversationally through ChatGPT."
type: build
status: draft
tags:
  - AI
  - GitHub
  - Automation

The site turns that file into a page during the build.

Drafts can stay in the repository without appearing publicly. Publishing is an explicit status change.

GitHub for content production

I keep rough ideas separate from articles.

An issue can hold notes, evidence, links, research and open questions.

When the idea is developed enough, it becomes a Markdown draft.

The flow is:

Issue = research and planning

Markdown = article

The Markdown file becomes the canonical version and isn’t regenerated over later edits.

The blog itself uses this workflow

This blog was added through ChatGPT.

I discussed how it should fit into the existing site, reviewed the implementation, commented on changes and iterated on the article you’re reading now.

I can do the same thing from my phone.

That is the main benefit for me.

Instead of sitting at a computer, opening the repository, finding the right files and editing them manually, I can make requests conversationally while I’m away from my desk.

The underlying result is still normal code and Markdown that I can inspect later.

ChatGPT is just a conversational layer on top

ChatGPT participates in the development workflow rather than bypassing it.

Changes remain version-controlled and reviewable before they reach the live website.

That also means the website is not dependent on ChatGPT. If I stop using it, I still have an ordinary static site and Git repository.

ChatGPT is simply a conversational interface on top of the codebase.

For me, that changes how maintaining a website works.

I can take out my phone and say:

Add this idea to the blog.

Change this section.

Review the latest implementation.

This paragraph is too long. Shorten it.

And those conversations can become actual, reviewable changes to the website.