Custom code — tips & best practices

This page explains what your custom code site can actually do and how to get the best results when you ask the AI to build it — whether you're using the in-browser AI builder or Claude Code. The advice applies to both.

You don't need to know how to code — but it helps to understand the building blocks the AI has, so you can ask for the right things.

What you can build

Your site already ships with every page a creator business needs — a store, product pages, events, courses, coaching, a blog, memberships, a checkout, and an account area. You can restyle any of them, and add your own pages and sections on top.

Here are the ready-made building blocks the AI can drop into any page. You don't reference these by name — just describe what you want and it picks the right one:

Beyond these, the AI can build anything you can describe — custom layouts, landing pages, animations, 3D, sections that mix your real data with your own design.

How the AI uses your real data

This is what makes the custom code workflow powerful, and it's worth understanding so you can trust what you get.

When the AI needs a product, event, image, or video, it looks up the real thing from your TribeNest account — it does not use placeholder text or stock photos. It can:

• See and use your uploaded media — the actual image and video URLs from your library.
• Add new media from a link or a file on your computer, straight into your library.
• Look up real product, event, course, and membership IDs so buttons and lists point at the right thing.
• Create an event with ticket tiers in one step (great for moving an event over from Eventbrite — just give it the link).
• Create membership tiers, forms, and custom content (like a directory or resource library) directly in your account.
• Read and change your editable text and images — and those changes go live instantly, with no rebuild.

Editable content — set it up once, edit it forever

There are two ways text and images live on your site, and knowing the difference saves you a lot of time.

• Hardcoded — written directly into the site's code. Changing it means editing code (or asking the AI).
• Editable content fields — text and images that are marked as editable. You can change these anytime, instantly, from the builder's Content mode or a chat with Claude or ChatGPT — no rebuild, no publish step.

Best practice: ask the AI to make your copy and images editable. When it builds a section, say "make the headline and images editable". Then updating your hero text later is a ten-second edit instead of a code change.

This is also why the chat connector can update your site: it edits these fields. Anything hardcoded is out of its reach until it's made editable.

Getting great results from the AI

A few habits make a big difference:

• Point at real things. "Feature my 'Summer Tour' event" or "use the studio photo from my media library" lets the AI grab the right data instead of guessing.
• Give it your brand colors. Say "my brand colors are #1a1a2e and gold" and the AI sets your theme — every button, checkout, and section updates together to match.
• Iterate in small steps. Change one section, look at the live preview, then move to the next. It's easier to steer than one giant request.
• Check for errors before you publish. The AI verifies the site still builds as it works, so problems get caught before they ever reach your live site.
• Migrate, don't retype. Moving an event, product list, or page from another platform? Give the AI the link or the details and ask it to recreate it — it'll build the real event and tickets for you.

Good things to ask for:

• "Change the homepage headline to 'Live in Lagos this August' and make it editable."
• "Add a tour section that lists my upcoming events, styled to match the site."
• "Set up two membership tiers: $5/month and $50/year, and add a join button to the header."
• "Take the event from this Eventbrite link and create it on my site with the same tickets."
• "Make the store page match my brand — dark background, gold accents, bigger product images."
• "Add a contact form with name, email, and a message, and email me the submissions."

Good to know (the guardrails)

A few things are handled for you or intentionally off-limits — knowing them upfront avoids surprises:

• Payments, accounts, and checkout are built in. You never wire up Stripe or logins yourself — the building blocks handle it. Just make sure your payment settings are connected in your dashboard.
• The functional pages (store, checkout, account, etc.) work out of the box but look generic. Treat them as part of your site, not untouchable — ask the AI to restyle the ones your visitors see most (store, product, checkout, event pages) to match your brand.
• You can't add arbitrary software libraries. The site comes with a curated toolkit (including animation and 3D). If you ask for something that needs an unsupported add-on, the AI will tell you it may not be possible rather than break your build.
• Some settings live in your dashboard, not the code. Things that need secret keys — like advanced ad tracking (Meta CAPI) or your Stripe connection — are configured in your TribeNest admin, and the AI will point you there.
• Build and config files are managed by TribeNest. The AI won't (and can't) change the low-level project setup — that keeps your site publishable.

Publishing safely

Custom code publishing is built to protect your live site:

• A broken build never goes live. Publishing builds your site first. If anything is wrong, it stops and nothing changes on your live site — your current site stays up. Read the error (or ask the AI to fix it) and publish again.
• Preview before you commit. Watch the live preview as you work, and use Deploy preview (in the builder) or tribenest preview (with Claude Code) to get a shareable link to test the new version before it's public.
• Roll back if needed. Every publish saves a restore point, so you can return to an earlier version from the builder's History menu.
• Content edits are instant and separate. Changing an editable field (text/image) goes live immediately and doesn't need a publish. Publishing is only for code, layout, and design changes.