/ and pick 3D Website to enter.
Screenshot coming. Brief → preview → deploy flow.
How it works
| Step | What Foundry does |
|---|---|
| Brief | You describe the experience. Foundry asks 1–2 clarifying questions if the brief is vague. |
| Design | A scene plan is generated — lighting, camera path, primary 3D elements, palette. |
| Render | The plan is turned into a working preview you can scrub. |
| Iterate | Reply with edits — “slower camera glide”, “warmer palette”, “add a hero CTA at the second scene break”. |
| Ship | Push the build to a hosted URL. |
Tips
- Anchor on one mood. “Quiet, contemplative” or “high-energy, neon” — not both.
- Name the scroll pattern. “Single-scroll story”, “snap-to-section”, “horizontal sweep” all work.
- Iterate small. One edit at a time; review; iterate again. Big rewrites confuse the planner.
Limits
- Today’s generations are single-scroll story sites. Multi-page apps with auth are out of scope.
- Performance budget matters — extremely heavy 3D scenes can drop frames on lower-end mobile.
- Hosted-URL deploys are a beta feature and may rotate as we harden the pipeline.
Related
Tutorial: Build a 3D site
Concrete walkthrough.
Workflows: Blueprints
Coming soon — multi-step 3D pipelines.