your name on the door.
Everything so far has been about making your copy run. This step is about making it say who it belongs to. Your site's name, its description, the name in the footer, the founder on the founder page: all of it comes from one file, FoundersConfig.json. Right now it holds unparty's details. By the end of this step it holds yours.
| You fill in | Where it shows up |
|---|---|
| Site name, title, headline | Browser tabs, the homepage title, search results |
| Description and tagline | Search results and link previews |
| Legal name | The copyright line in every page's footer |
| Founder name, photo, bio, links | Your founder page at /founders |
| Address (from Your domain) | Sitemap, link previews, search engines |
✓ Success: your site says it is yours.
this is a work in progress
1️⃣ Fill In Your Details
Open src/data/FoundersConfig.json in your editor. It has three parts: site (your business), founder (you), and brandColors. Replace each value between the quote marks with your own. Here is what a small bakery might write:
{
"site": {
"name": "bakery",
"title": "bakery.com",
"tagline": "fresh every morning.",
"headline": "Neighborhood Bread and Pastry",
"description": "A neighborhood bakery sharing what we bake and how.",
"url": "https://www.bakery.com",
"legalName": "Sam's Bakery LLC",
"github": "",
"logo": { "path": "/bakery-logo.png", "width": 1200, "height": 1200 }
},
"founder": {
"name": "Sam Rivera",
"role": "owner",
"title": "baker.",
"image": "sam-rivera.jpg",
"initials": "SR",
"cover": "cover-052",
"bio": "Bread before sunrise, for twelve years.",
"summary": "Sam Rivera, owner of bakery.com, a neighborhood bakery.",
"links": [
{ "label": "Instagram", "url": "https://instagram.com/bakery" }
]
},
"brandColors": ["#C8553D", "#F2D0A4", "", "", ""]
}🏷️ The site Part
| Field | What to write |
|---|---|
| name | Your site's short name, the one that comes first in the homepage title |
| title | The name shown in browser tabs on pages without their own title. Often your domain |
| tagline | A few words under that title in search results |
| headline | What your site is, after its name on the homepage: "bakery — Neighborhood Bread and Pastry" |
| description | Two sentences for search results and link previews |
| url | Your address from Your domain. Starts with https://, no slash at the end |
| legalName | Your business's legal name, for the copyright line |
| github | The GitHub user or organization that owns your projects' code. Leave "" if you do not have one |
| logo | A PNG or JPG in your public folder, and its real width and height in pixels |
To find a picture's size in pixels: on a Mac, open it in Preview and press ⌘ + I. On Windows, right-click it, choose Properties, then Details. Google asks for a logo's real size, so copy both numbers exactly.
🙋 The founder Part
| Field | What to write |
|---|---|
| name, role | Your name and what you are: "owner", "founder", "chef" |
| title | One or two words in large letters on your founder page: "baker." |
| image | A square photo of you in your public folder, by file name. Or "" to show your initials |
| initials | Two letters, shown when there is no photo |
| cover | The picture across your founder page. Use your cover from Your first cover |
| bio | One or two sentences under your title. Two stars around a word make it bold |
| summary | One sentence about you for search results and link previews |
| links | Anywhere people can find you. Add as many as you like, each with a label and an address |
Put your photo and logo in the public folder at the top of your copy, the same way you added your cover, then write their file names in. brandColors holds up to five colors, like "#C8553D". They are saved for a future update that colors your theme; leave the ones you do not need as "".
- Keep the quote marks — every value sits between straight double quotes
- A comma between lines, never after the last one — the last line in a block or a list has no comma
- Numbers have no quotes — the logo's width and height are plain numbers
- Apostrophes are fine here — unlike articles, this file needs no backslash: "Sam's Bakery LLC"
2️⃣ Check It
A missing comma in this file can take your whole site down, so your copy comes with a checker that reads it before you do anything else:
# Check FoundersConfig.json
npm run check:identity- ❌ lines are problems — each names the field and what is wrong, like a photo file that does not exist. A broken comma is reported with its line number
- ⚠️ lines are values still set to unparty's — they never stop your site, but each one is a place where unparty is still speaking for you
- ✅ with nothing above it — everything is yours
Now start your site with npm run dev and open localhost:3000/founders. You will see your photo, your name, your title, your bio, and your links, and nothing else. That is on purpose:
| Part of /founders | Shows when |
|---|---|
| Your profile and links | Always, from this file |
| Your answers to the founder questions | Once there are answers saved under your name. A later update adds a form for them |
| Your repositories, effort and tech | Once your site holds data about repositories owned by your github name |
Your copy came with unparty's answers and repository data. Your founder page never shows them under your name: it only shows data that belongs to the founder and the GitHub name in this file.
3️⃣ See Your Name, Then Ship It
- The homepage tab reads your name and headline
- The footer, at the bottom of any page, says © and your legal name
- /founders shows your profile, and only your profile
- npm run check:identity still ends with ✅
In GitHub Desktop, the Changes list should hold FoundersConfig.json, plus your photo and logo if you added them. Write a summary like "Make it mine", click Commit to main, then Push origin.
“Same code, same pages. Your name on all of it.”
— unparty-app
⚠️ What Still Says unparty
- The example pages — the /theunparty pages, stories, articles and covers that came with your copy are unparty's projects, kept as working examples next to yours
- These setup articles — they stay signed by their author, as a manual would
- The words in the code — file and folder names still say unparty in many places. None of it is shown to your visitors
- A list of every one is coming — a later update adds a page that finds each remaining unparty reference, so you can replace or remove them one by one
🧯 If Something Is Off
- "is not valid JSON (line 31, column 37)" — open the file at that line. It is almost always a comma after the last item in a list, or a missing comma between two lines
- "points to a file that does not exist" — the photo or logo is not in the public folder, or its name is spelled differently. Check capitals and the ending: .jpg is not .jpeg
- "has no matching file in public/covers/" — use the name of a cover that exists, without its ending: cover-052, not cover-052.jpg
- Your photo shows as initials — the image name is wrong or empty. Run the checker
- The site shows an error after you saved — run npm run check:identity. A broken file stops the whole site until it is fixed
🤖 Ask Your LLM
Here is what my business does: [describe it]. Write a two-sentence
description for search results, a four-word tagline, and a short
headline that says what my site is. Keep it plain and specific.
(In Claude Code, inside your copy)
Run npm run check:identity and fix every problem it reports in
src/data/FoundersConfig.json. Ask me before you change any wording.✅ You Are Done When
- npm run check:identity prints ✅ with no ⚠️ lines above it
- Your homepage tab, footer and /founders show your name, on your computer and on your live site
- Your photo, logo and cover are in your copy and pushed
- The commit with FoundersConfig.json is live on Vercel
That is every required step. Your copy runs, it lives at your address, it knows you own it, it holds your first cover, story, article and project page, and now it says your name. The optional steps are there when you need them: payments, email, uploads and more, one at a time.
“Your name on the door. What you build behind it is up to you.”
— unparty-app