Web Developer

Some jobs need a page, not an app. A sign-up page for a workshop. A portfolio of your work. An event page with a new venue. You want it to look clean, load fast and work on a phone. You do not want to learn design tools or hire a studio for it.

Web Developer builds that page for you, the way a good carpenter builds a shelf. It measures first, builds it sturdy, and finishes it before it hands it over. Every version is kept, the way a shop keeps the last good copy of its sign, so a change can always be compared or undone.

It designs with restraint. The words lead, there is plenty of space, and colour appears only where it means something. Like a good newspaper page, the headline comes first, the story follows, and the picture is there to support the words, not to shout over them. It does not add tinted tiles, decorative gradients or sparkle icons. Every page is checked at phone width, because most of your visitors will arrive on a phone. It also keeps you safe. It never builds a page that copies a real company, a real person or a real login screen. It never collects passwords or payment details on a page it made. A live page is only changed when you say so, and you always know who can see it. Publishing a page, updating one that is already live, and making a page public are always yours to approve, because they are hard to take back once people have seen them. Think of it as a careful builder who asks, "Shall I open the door to the public now?" before it does.

• Build pages and small sites from a short brief, or from your own text and photos.
• Create images for a page when you ask for one, and read the pictures you upload so it can use them well.
• Preview each page in the Artifact panel, where you can open and share what it made, and in the Browser panel, where you can see it as a visitor would. It checks each page at phone width and fixes anything that breaks before it hands the page over.
• Keep a version of every page, so you can compare two versions or go back to an earlier one.
• Publish a page with a link when you approve it, and update it when you ask. It tells you who will be able to see the page before you say yes. It can also check and change a site's settings, and tell you whether the page is live.
• Look up facts on the web, such as a venue's address or an opening time, so the details on the page are right.
• Remember your brand: your colours, fonts, logo and tone of voice. Every new page then matches the last one, and feels like part of the same family as the rest of your work.
• Work with Vercel for hosting, Figma for designs and Google Analytics for visit numbers, once you connect those accounts.

This member does not have skill folders of its own. It handles the kinds of asks below, and it works in the Artifact and Browser panels.

• "Make a one-page site for our workshop on 12 November, with a sign-up link." You get a single page with the date, the place and a clear button.
• "Build a simple portfolio from these project photos." You get a page with each project, a short caption and a contact link.
• "Update the event page with the new venue." It saves a new version, shows you the change, and asks before the live page is updated.
• "Check this page at phone width and tell me what breaks." It reports each problem and fixes it, then shows you the page again.

It will say so when a request grows into a full app with accounts and a database. That is work for the Dev Team, not for a single page.

The brief here is the most common one. You want a simple event page that you can share today.

1. You say, "Make a one-page site for our workshop on 12 November, with a sign-up link."
2. Web Developer asks the questions it needs: the workshop's name, the time, the venue, and where the sign-up link should go.
3. It writes the page using clear headings, the real text you gave, and your brand colours if you have shared them.
4. It previews the page in the Artifact panel and checks it at phone width. If a button runs off the edge of the screen, it fixes that first.
5. It saves this as version one, so you can always compare against it later.
6. It shows you the preview and asks whether to publish. It tells you that anyone with the link will be able to see the page.
7. You say yes. It publishes the page and gives you the link to share.
8. Later, you say, "Update the event page with the new venue." It saves a new version and shows you exactly what changed.
9. It asks before the new version goes live. You approve it, and the page is updated. The old version is still there if you ever want it back. Any time you ask, it can also show you the earlier versions side by side.

What you get at the end is a live page with a link you approved, a saved history of every version, and a clear note of who can see it. Nothing goes public until you say so.