unparty.app
unparty.app fish out of water Logo

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
Site name, title, headline
Where it shows up
Browser tabs, the homepage title, search results

this is a work in progress

  1. Fill it.

    One file: your site and you.

  • Success.your site says it is yours.

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:

json
{
  "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
name
What to write
Your site's short name, the one that comes first in the homepage title

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
name, role
What to write
Your name and what you are: "owner", "founder", "chef"

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.

🎨 Your Colors

Five colors, and the first one is your site's: buttons, borders and the bar at the top of a phone take it. All five lead the colors your visitors can pick from. You do not have to type them into the file. Tap a ring, then a color, and this page tries it on. A cover gives you all five at once.

Loading BrandColors...
  • Without sign-in — only an admin can save, so copy your colors into brandColors in src/data/FoundersConfig.json yourself
  • On your computer — signed in as admin, with npm run dev running, save my colors writes them into src/data/FoundersConfig.json, and your site reloads in them
  • On your live site — with your GitHub App connected, saving opens a change in your repository that merges itself. Your site wears the colors after its next deploy
  • Without the GitHub App — saving shows the one line to paste over brandColors in the file
  • Anytime later — the same rings are in /admin, under your site. Change one color or all five

Your colors travel. Every link to your site shares a card made from them, your words and your covers. Try a color above and watch the card change.

Loading LinkPreview...
  • 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:

bash
# 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. It is your resume, read like any article on your site, and written for someone deciding whether to back you, hire you or buy from you. Every chapter is worked out from your own site, and a chapter with nothing to show yet stays hidden:

Chapter of /founders
Your name, title, photo, bio and links: the header, byline and opening
Shows when
Always, from this file
json
"resume": {
  "thesis": "the one sentence your work makes the case for",
  "articles": ["your-best-article", "your-first-story"],
  "components": ["GoalBudget"],
  "areas": [
    { "name": "writing", "match": ["story"] },
    { "name": "guides", "match": ["setup."] }
  ],
  "labels": false,
  "views": false
}
  • thesis — your case, in your words. The page never writes it for you
  • articles — the slugs of the articles and stories to show first, in order
  • components — components to show working, each from its home article (see /build)
  • areas — the kinds of work you do, each matching a category, a tag, or article, story or component
  • labels — each chapter opens with a hand-drawn icon; true adds its word beside it
  • views — your traffic is yours to share, so it stays off until you turn it on

Your copy came with unparty's articles and stories. Your resume never counts them as yours: it only counts what is credited to your name or your site's name.

3️⃣ See Your Name, Then Ship It

  1. The homepage tab reads your name and headline
  2. The footer, at the bottom of any page, says © and your legal name
  3. /founders shows your profile, and only your profile
  4. 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

prompt
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

YOURS. make it your own.

  1. Make it yours: identity→

    One file says who your site is and who built it. Fill it in, and your name replaces unparty's everywhere it counts.