← Back to the front page

Taking this site over

Written for someone who has never opened a terminal and doesn't intend to start.

Nothing here requires you to learn to code. The whole site is a handful of text files, and you can change any of them from a web browser in about two minutes.

If you read one section, make it "Changing something" below. The rest is reference for the day you need it.

What exists, and where

Three separate things keep this website online. They're independent, which is good — a problem with one doesn't take down the others.

The domain

GoDaddy

Owns the name abizertyabji.com and points it at the files. This is the only piece that costs money — roughly $20–25 a year.

The files

GitHub

Holds every page of this site as a text file, plus a complete history of every change ever made. Free. This is where you edit things.

The publishing

Netlify

Watches GitHub. The moment a file changes there, Netlify rebuilds the site and puts it online, usually within a minute. Free, and you will almost never need to log into it.

For the first year, all three accounts are Danny's and he's covering the domain. Around August 2027 — before the domain comes up for renewal — the plan is to move them to you. Nothing breaks if that slips; it just means asking him again.

Changing something

Say you want to fix a sentence, swap a link, or delete the letter at the top of the front page.

Step one

Open the repository on GitHub

Go to github.com and sign in, then open the repository named abizertyabji-site. You'll see a list of files: index.html, takeover.html, a folder called examples, and a few others.

The front page is index.html. Every file ending in .html is one page of the website.

Step two

Click the file, then click the pencil

Clicking a file shows you its contents. A small pencil icon near the top right switches it into an editor you can type in.

You'll see a mix of your words and things wrapped in angle brackets, like <p>. Those are formatting instructions. Type over the words; leave the bracketed bits alone.

Step three

Save it — GitHub calls this "commit"

Green Commit changes button at the top right. It asks for a short note describing what you did. Anything is fine: "fixed my email address." Then confirm.

Step four

Wait a minute, then look

Netlify notices the change on its own and republishes. Refresh abizertyabji.com after a minute and your edit is live. Nobody has to approve it.

You cannot permanently break this. GitHub keeps every version of every file. If a change goes wrong, the old version is still there under the "History" link on any file, and it can be put back.

Letting an AI do it for you

This is the realistic path, and it works well. Claude, ChatGPT, Gemini — any of them can rewrite these files correctly if you give them the file and tell them what you want.

The short version

Copy the file, paste it, describe the change

Open the file on GitHub, copy everything in it, paste it into the AI, and say what you want. Then paste what it gives you back over the original, using the pencil-icon steps above.

A prompt that works:

This is one page of my personal website, abizertyabji.com.
It's a plain HTML file with the styling in a separate stylesheet.

Please make these changes and give me back the complete file,
ready to paste in and replace the original:

  1. Change my contact link to beezer@example.com
  2. Delete the letter block at the top
  3. Add a short paragraph about my consulting work

Keep the existing structure and CSS class names exactly as they are.
Don't add any new libraries or external links.

That last line matters. Left alone, an AI will happily add frameworks and fonts this site doesn't need and can't load. Telling it not to keeps the site fast and unbreakable.

If you'd rather it just did the whole thing: some AI tools connect directly to GitHub. Point one at the abizertyabji-site repository, describe what you want, and it can make the edits itself. Ask Danny to help set that up the first time.

Once a year

One thing needs a human, and it's the domain renewal.

If something looks wrong

The deeper documentation

Inside the repository there's a docs folder with two files written for whoever maintains this next, human or AI: ARCHITECTURE.md explains how it's put together and who owns what, and ROADMAP.md has the handoff plan with dates on it.

If you ever hand this site to a developer or an AI assistant cold, point them at those two files first.