like 6…7  /  how this was made (in 6–7 hours) ← back to the site
Jump to a section
  1. The idea
  2. Saving the work
  3. On the internet
  4. Looking right on phones
  5. Save it as an app
  6. Knowing if anyone's there
  7. A real share image

How this was made (in 6–7 hours)

A walkthrough of like67.com — built in an afternoon by talking to an AI.

This site is a joke. A page for the moment when somebody says like 6… 7. The whole thing — the HTML, the animations, the icons, the share image, the install prompt for your phone — was built in one afternoon by typing into a chat with an AI. I didn't write any code by hand. Even this tutorial and recap was generated without typing any code.

Below is the story of how it actually happened, in the order it happened, broken into seven pieces.

Each piece has two columns. The left column is for someone who is just curious in seeing the pieces of what I did, in plain English. The right column is for someone who wants to learn a little more technical language (jargon) with the goal of being detailed enough to copy the whole thing — the specific tools, the prompts I used word-for-word, the commands I ran. You don't need to read both.

Anything underlined with little dots, like HTML, is an acronym — hover (or tap) to see what it stands for.

§1The idea

From session 000 — the ChatGPT prototype
View the raw conversation that produced this →
The unedited prompts and replies. This page is the curated version.

How it went

In plain English
To replicate it
Where I was

Nothing existed yet. Just an idea for a stupid webpage about a meme. I wanted a single page that felt like the moment somebody says like 6… 7.

No code, no website, nothing yet. Just an idea and a closed laptop.

What I wanted

One web page that, when you opened it, felt like the meme. Big glowing “6 7” numbers in the middle. Confetti. Color. Noise. Nothing useful. Just chaos pointed at a single moment.

A self-contained index.html — markup, styles, and scripts all in one file. No assembly step before it could run (a “build step”), and no extra library like React to install first (a “framework”). Something I could double-click on my own machine and have the whole site running locally before anything else got involved.

What I already knew (that might be new to you)

There's a pile of background knowledge baked into even the first sentence I typed. I knew that webpages are made of code called HyperText Markup Language (HTML). I knew that the code lives in a file you can save and open. I knew an AI chat could write that code, not just talk about it.

None of those are obvious if no one has ever told you. The whole tutorial below is paced to a reader who is finding out about each of them as they appear.

HTML / CSS / JS basics. That JSFiddle exists as a place to paste-and-run. That LLMs iterate well in conversation — they get better when you say what's wrong. That plain-English prompts work; you don't have to “write code” to ask for code.

What I asked

I told the AI: make me a crazy 6–7 animation webpage. Big numbers, vibrant, more chaos than makes sense. Then I tried what it built, said what was off, and asked for fixes. Over and over. Each round was just a few words.

> Can you do custom html animations?
> I want a 6 7 animation. Something big, vibrant and crazy. Reflecting the meme.
> That's pretty good, can we add anything else to the chaos?
> Make all the hypeText, rare. Let's get rid of the More Chaos button.
What got built

A working webpage. Big numbers in the middle, glowing colors behind them, raining emojis, hype text that flashes once in a while. I could see it run on the screen, try it, and ask for changes. By the end of the conversation, the page was the page.

One HTML file (~200 lines) with embedded <style> and <script>. About ten prompts of iteration. Previewed live in JSFiddle, then the final result was saved as a local file. The first git commit doesn't happen until §2.

Concepts introduced in this section

Click any concept for a definition and an example.
HTML

HyperText Markup Language. The code that tells a browser what's on a webpage — headings, paragraphs, images, buttons. It's just text in a file, with little tags wrapped around the parts.

Example: <h1>Hello</h1> makes the word Hello show up as a big heading.

CSS

Cascading Style Sheets. The code that tells the browser how the page should look — colors, sizes, fonts, animations.

Example: h1 { color: hotpink; } turns every <h1> heading hot pink.

JavaScript

The code that lets a webpage do things — react to clicks, change over time, run animations, respond to the user.

Example: a button that, when clicked, makes confetti fall down the screen.

prompt

What you type to an AI. The clearer and more specific you are, the better the answer. You can iterate — say what's wrong, ask for a change, get a new version.

Example: “Make the numbers bigger and add more emojis.”

iteration loop

The cycle of: ask for something → see what came back → say what's wrong or what you want next → repeat. Most of building with AI is iteration, not one giant prompt.

JSFiddle

A free website where you can paste HTML, CSS, and JS into three boxes and see your webpage run live in a fourth. Useful for testing before you save anything to a file.

It lives at jsfiddle.net.

Tools I used

ChatGPT for generation · JSFiddle for live preview · any plain text editor (TextEdit, Notepad, VS Code) for saving the file.

Commands I ran

None this section — entirely chat & copy-paste. The terminal first appears in §2.

Questions to try

Ask your AI
  • “What's the dumbest possible webpage I could make about [a thing I love]?”
  • “Make me a single HTML file that animates the words [my idea] in a fun way.”
  • “I'm a total beginner — what is HTML, in plain English?”
Search
what is HTML · what is JSFiddle · getting started with HTML on MDN
Ask yourself
What's a meme or a moment I'd actually want a page for? Can I describe it to an AI in one sentence?

Going deeper

JSFiddle.net — open it in a tab and play

§2Saving the work

From session 002 — importing the prototype into a repo
View the raw conversation that produced this →
The unedited prompts and replies. This page is the curated version.

Full entry coming in a later session. Topic preview: taking the HTML from the chat, saving it as a real file on the laptop, putting it in a folder version-controlled by Git, and pushing it to GitHub so it lives somewhere besides one machine.

§3On the internet

From session 003 — license, hosting, and DNS
View the raw conversation that produced this →
The unedited prompts and replies. This page is the curated version.

Full entry coming in a later session. Topic preview: picking a license for the code, picking a free host that auto-publishes the site every time you change something (Cloudflare Pages), and pointing the domain like67.com at the host through DNS.

§4Looking right on phones

From session 004 — title, mobile layout, share previews
View the raw conversation that produced this →
The unedited prompts and replies. This page is the curated version.

Full entry coming in a later session. Topic preview: fixing the way the page rendered on iPhones (where iOS Safari was clipping the top of the animation), adding a proper page title for link previews, and laying out the “SIX SEVEN” chant differently on narrow screens.

§5Save it as an app

From session 007 — fullscreen hints and PWA install
View the raw conversation that produced this →
The unedited prompts and replies. This page is the curated version.

Full entry coming in a later session. Topic preview: making the page installable on a phone's home screen so it opens like a real app (Progressive Web App / PWA), drawing the icons that show up there, and showing a hint to the user telling them how to install it.

§6Knowing if anyone's there

From session 010 — analytics and the corner-link rewrite
View the raw conversation that produced this →
The unedited prompts and replies. This page is the curated version.

Full entry coming in a later session. Topic preview: turning on a privacy-friendly visitor counter (Cloudflare Web Analytics) so I can see how many people land on the site, without using cookies or tracking anyone personally.

§7A real share image

From session 011 — the OG image and hint polish
View the raw conversation that produced this →
The unedited prompts and replies. This page is the curated version.

Full entry coming in a later session. Topic preview: making the picture that shows up when somebody pastes the link into iMessage, Twitter, or Discord. Built with a tiny Python script the AI wrote, so iterating on the image was as fast as iterating on the page.