Idea → structure
Outline the page
Decide what the page is for, who it is for, and the few sections it needs. For this demo: a strong opening, one explanation, and a visible workflow.
This tiny webpage exists to make the publishing process visible. We outline an idea, turn it into code, save it on GitHub, and deploy it through Cloudflare.
The code is just text. The browser turns it into a page.
THE WORKFLOW
You do not need to understand everything at once. Follow the hand-off from one stage to the next.
Idea → structure
Decide what the page is for, who it is for, and the few sections it needs. For this demo: a strong opening, one explanation, and a visible workflow.
Structure → webpage
HTML gives the page its structure. CSS controls the colours, type, spacing, and layout. Open the file in a browser and keep adjusting until it feels right.
Webpage → history
Git records a snapshot of the files. Each commit is a named checkpoint, so you can see what changed, collaborate safely, or return to an earlier version.
History → shared source
GitHub stores the repository online. Push the commit and your friend can inspect the same code, suggest an edit, or continue building from another computer.
Source → live internet
Connect the GitHub repository to Cloudflare Pages. Cloudflare builds the site, gives it a public address, and automatically redeploys after every future push.
THE IMPORTANT BIT
Once GitHub and Cloudflare are connected, every improvement follows the same repeatable path.
WHAT YOUR FRIEND JUST LEARNED
It is a set of ordinary files, a history of deliberate changes, and a service that puts those files on the internet. The best way to understand the workflow is to ship something small.