Build your studio
Create a name, domain, project structure, support surface and basic legal/privacy pages.
What this step is for.
A studio needs a stable identity and a way for users to understand who built a product, what its status is and how to get help. Keep unfinished work clearly labelled. Use a domain you control and create consistent project, support and privacy surfaces.
Keep the scope small enough that you can inspect the result yourself. AI can accelerate the work, but it should not erase the distinction between a suggestion, a changed file, a successful build and a verified product.
Take one concrete action.
Choose a studio name, create a simple project directory and draft About, Contact, Support and Privacy pages. Mark every prototype with its actual status.
Create a five-page studio site that works locally
Know the layers: a local preview runs only on your computer. Hosting puts site files on an internet-connected server. A domain is the readable address people type. DNS connects that domain to the host. This exercise needs only the local preview.
Create my-studio-site with index.html, projects.html, about.html, contact.html and privacy.html. First paste this complete pattern into index.html:
<!doctype html>
<html lang="en">
<meta charset="utf-8">
<title>My Studio</title>
<nav>
<a href="index.html">Home</a>
<a href="projects.html">Projects</a>
<a href="about.html">About</a>
<a href="contact.html">Contact</a>
<a href="privacy.html">Privacy</a>
</nav>
<h1>My Studio</h1>
<p>A practice studio site built locally.</p>
</html>Copy that entire file four times and rename the copies. In each copy change only the <title>, <h1> and paragraph to match Projects, About, Contact or Privacy. The navigation stays identical.
Open PowerShell in my-studio-site, run python -m http.server 8000, visit http://localhost:8000 and click all five links. Visit http://localhost:8000/missing.html once to see a local 404. Stop with Ctrl+C.
Prepare for Step 13: run git init, git add . and git commit -m "studio site baseline". If Git asks for identity, use the exact name/email commands taught in Step 07. Run git status; it must be clean.
Success: five pages navigate locally without errors and the source folder has a clean baseline Git commit. Nothing has been published to the internet yet.
Turn the idea into evidence.
Open every page from the navigation rather than typing each filename. Record any broken destination before creating the baseline Git commit.
Do not move on until this is true.
A visitor can identify the studio, the product status, a support route and the privacy information without searching social media.
Why we use this principle.
Nyfir Studios treats generated output and verified output as different states. Development work on local AI, Android software and bookkeeping workflows has repeatedly shown that recoverable state, explicit tests and clear product status are more useful than simply producing more output.