#Building websites

Describe a site in plain language and Arachne builds something you can open, use, and refine until it is right.

#Overview

Arachne can build a website for you from a description. You say what the site should do and how it should look, and Arachne produces something real — a working site you can open and use — rather than a sketch or a set of instructions. You do not write any markup, wire anything together, or specify the path Arachne takes. You describe the outcome; Arachne builds toward it.

This matters because a website is usually a project, not a question. Getting one made normally means tools, setup, and steps. Here it is a conversation: you explain what you want, watch it come together, and keep shaping it in plain language. Everything Arachne builds is verified before it is reported done, and it is saved as an artifact you can return to, reuse, and export.

#What you can do

• Build a small website from a plain-language description of what it should do and look like.
• Describe both the purpose and the appearance — the content, the structure, the feel, the tone.
• Open and use what Arachne produces, not just preview a picture of it.
• Refine the result in plain language: ask for changes, additions, and corrections until it is right.
• Iterate as many times as you need; each round of changes builds on the last.
• Keep the finished site as an artifact you can find again, reopen, reuse, and export or download.
• Watch the build happen live and steer it as it goes, at the permission level you set.

#How to use it

1. Describe the site. Say what it is for and what it should look like — its purpose, the main content or sections, and the feel you want. The clearer your picture, the closer the first result lands.
2. Add anything you already have. If you have reference links, text, a name, colors, or constraints, give them up front so Arachne builds with them from the start.
3. Choose how much freedom to give. Set a permission level that fits. For a first build, watching as it goes is a good way to steer; for a task you trust, let it run further on its own.
4. Watch the first run. See the site take shape live. This is the easiest moment to catch "not quite that" and redirect before it goes further.
5. Open and try it. Arachne hands you something you can actually open and use. Click through it, read it, see how it behaves.
6. Refine in plain language. Tell Arachne what to change — "make the header simpler," "add a section for pricing," "warmer colors," "move the contact form to the top." Each request reshapes the site.
7. Repeat until it is right. Keep refining as long as you like. When you are happy, the finished site is saved as an artifact you can reopen, reuse, and download.

#Examples

What you ask:

Build a one-page site for my photography studio. Clean and minimal,
dark background, a gallery of my work up top, a short about section,
and a contact form at the bottom.

What you see: Arachne builds the site live as you watch, then hands you a working one-page site you can open — a dark, minimal layout with a gallery area, an about section, and a contact form — saved as an artifact you can reopen and download.

What you ask:

Make the gallery bigger and put my studio name in large text at the top.

What you see: Arachne updates the same site in place, enlarging the gallery and adding your studio name as a prominent heading, and shows you the revised version to open and check.

What you ask:

Build a simple landing page for a weekend workshop — a headline, three
bullet points on what people will learn, the date and location, and a
sign-up button. Friendly and bright.

What you see: A bright, friendly landing page you can open and use, with the headline, the three points, the date and location, and a sign-up button — ready to refine further or download as it is.

#Tips

• Describe the feel, not just the parts. Words like calm, bold, minimal, warm, or playful steer the look as much as a list of sections does.
• Bring your own material. Give Arachne the real text, name, links, or colors you already have, so the first build is yours rather than placeholder content.
• Refine in small, clear asks. One change at a time — "simpler header," "add pricing," "warmer colors" — is easier to land than a long mixed list, and you can always chain them.
• Watch the first build. Staying with the first run lets you redirect early, which is faster than fixing a finished result you did not want.

#Related

• Building apps — when you need a working app rather than a site.
• What Arachne does — the full picture of Arachne's hands on the web.
• Using Arachne well — how to describe outcomes for the best results.
• Permissions & control — choosing how much freedom to give a build.
• Artifacts & where they go — finding, reopening, and exporting what you build.