← All chapters3 / 17
Start here · Chapter 3
Writing a good description
The description is the most important thing you give Chirai. It decides which pages exist, what data is stored, and how the site looks. You don't need technical words — you need specific ones.
What makes a good description
Cover four things, in any order:
- What the site is and who it's for. "An online store for hand-painted kalamkari sarees, for customers across India."
- What people do on it. "Customers browse by category, save favourites, pay with UPI or cash on delivery, and track their order."
- What you need to manage. "I add products with several photos, sizes and stock; I see orders and mark them shipped."
- How it should feel. "Warm, earthy, light. Lots of photos."
Good and weak descriptions
| Weak | Better |
|---|---|
| "A recipe app." | "A community recipe site for home cooks. Members post recipes with photos, ingredients and steps, save favourites, comment and rate. Grouped by cuisine and diet (veg, vegan, Jain). A weekly newsletter." |
| "Job site." | "A job board only for engineering roles in Bengaluru. Verified companies post jobs; candidates upload a resume, save jobs and get alerts. Filter by experience and salary." |
| "Food delivery like Swiggy." | "Food delivery from local restaurants, shops and cloud kitchens. Customers have accounts with order history; restaurants have ratings and reviews; a separate cloud kitchen section." |
The "better" examples are close to real descriptions that produced the sites in the Showcase.
Be specific about
- Roles — who can do what ("only verified companies can post jobs", "anyone can submit a recipe").
- The things you store — products, bookings, listings, complaints — and what each one has (photos, sizes, price, status).
- Money — what's paid for, and how (online, cash on delivery, subscriptions).
- Region — your country and city. Prices, phone formats and legal pages follow it.
- Must-have pages — say them, or tick them in IILA's page list.
You don't need to say
- Technology (frameworks, databases, hosting) — Chirai chooses and sets it up.
- Sign-in, account pages, privacy and terms pages, the admin area — every site gets them.
- SEO basics — page titles, sitemap, share images and search-engine data are added automatically.
Things to keep realistic
- Data from other websites. If your idea needs live data from elsewhere (government portals, airline fares, stock prices), IILA asks how it will arrive. Sites read outside data only through a proper API you connect in Connections — they never copy other websites. Without an API, plan to enter that data yourself in Manage site.
- Very large ideas. A whole marketplace with chat, maps, payments and three kinds of users is possible, but a focused first version builds faster and works better. Add more pages later with IILA.
Website, landing page, or frontend only
On the build page, websites have three build types:
- Full-stack (default): pages, database, accounts, Manage site.
- Frontend only: real multi-page design without a database — good for trying a look.
- Landing page: a single page, no backend.
The Chirai ultra / Chirai brain switch picks which family of AI models writes the code (ultra uses Claude; brain uses open models).