Tips and best practices

This page is about what your site can actually do and how to ask for it so you get what you had in mind. It applies whether you use the in-browser AI builder, the Claude or ChatGPT chat connector, or Claude Code on your own machine.

You do not need to know how to code. It does help to know what the building blocks are, 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 pieces the AI can drop into any page. You do not name them. Just describe what you want and it picks the right one.

Beyond these, it 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 whole thing worth it, and it is 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 in your TribeNest account. No placeholder text, no stock photos. It can:

• See and use your uploaded media, the actual images and videos in your library.
• Add new media from a link or a file on your computer, straight into your library.
• Find your real products, events, courses, and membership tiers, 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 somewhere else: give it the link and ask.
• Create membership tiers, forms, and custom content 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.

• Written into the design. Changing it means changing the site, which means asking the AI.
• Editable content fields. Text and images that are marked as editable. You change these any time, instantly, from the builder's Content mode or a chat with your own assistant. No rebuild, no publish step.

So ask for it. When the AI builds a section, add "and make the headline and images editable". Updating your hero text later becomes a ten-second job instead of a request.

This is also why the chat connector can update your site: it edits those fields. Anything written into the design is out of its reach until it is made editable.

Getting great results

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 it grab the right data instead of guessing.
• Give it your brand colours. Say "my brand colours are deep navy and gold" and it sets your theme, so every button, checkout, and section updates together.
• Iterate in small steps. Change one section, look at the live preview, then move on. Small requests are far easier to steer than one giant one.
• Watch the preview, not your imagination. It updates as the work lands, so you find out immediately if something is not what you pictured.
• Migrate, do not retype. Moving an event, a product list, or a page from another platform? Give it the link or the details and ask it to recreate it.

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, one monthly and one yearly, and add a join button to the header."
• "Take the event at this 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."

Good to know

A few things are handled for you, or deliberately out of reach. Knowing them upfront avoids surprises.

• Payments, accounts, and checkout are built in. You never wire these up yourself. Just make sure your payment settings are connected in your dashboard.
• The built-in pages work out of the box but look generic. Treat the store, product, checkout, and event pages as part of your site rather than something untouchable. Ask for them to be restyled to match your brand, starting with the ones your visitors see most.
• You cannot add just any add-on. Your site comes with a curated toolkit, including animation and 3D. If you ask for something that needs an unsupported add-on, the AI tells you it may not be possible rather than breaking your site.
• Some settings live in your dashboard, not in the site. Anything with a secret key, like advanced ad tracking or your payment connection, is configured in your dashboard, and the AI will point you there.
• The low-level project setup is managed for you, which is what keeps your site publishable.

Publishing safely

• A broken build never goes live. Publishing builds your site first. If anything is wrong it stops, nothing changes, and 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 to get a shareable link so someone else can look before it is public.
• Roll back if you need to. 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 text or image goes live immediately. Publishing is only for layout, design, and code.