Start with a clinic booking site or an internal admin tool from one of 200 ready-made…
· Info Inlet
Start with a clinic booking site or an internal admin tool from one of 200 ready-made templates across 11 industries. That is the shortcut Xenition offers—you describe what you want in a conversation, and it opens a fully working app, not a text box. Most web projects start with the same few patterns: a booking system, a customer portal, a dashboard, an e‑commerce store. Building each one from scratch means wiring up authentication, database schemas, form validation, and responsive layouts every time. Even with a framework, the first hour goes to boilerplate. The second hour goes to styling. By the third hour you might have a skeleton that still doesn't connect to anything real. **The problem with starting from zero** Blank pages are expensive. Every developer knows the feeling of staring at an empty editor, reaching for a starter kit, then spending time adapting it. Starter kits help, but they are static—you download a zip, open it in an editor, and then make changes by hand. If you need a new feature mid‑project, you either write it yourself or paste in another snippet. There is no conversation, no way to say “make the checkout form collect a phone number” and watch the code update. **A different starting point** Xenition begins with a template. Not a static HTML file, but a live, working application that you can run immediately. There are 200 such templates, spread across 11 industries. They cover the kinds of sites people build most often: a clinic booking site with appointment slots, an internal admin panel with user management, a shop with product listings and a cart, a real‑estate listing site, a restaurant menu with reservations, a portfolio with contact forms, a knowledge base with search, and more. Each template is a full app—front end, back end, database, and deployment configuration. It runs in the browser or can be exported. You do not need to set up a server or install dependencies. The template is ready to use as soon as you open it. **How the conversation works** Once you pick a template, the real work begins by typing. You tell Xenition what you want to change. For example, with a clinic booking template, you might say: “Replace the default clinic name with Oakwood Medical. Add a second doctor with Tuesday availability. Change the booking confirmation email to include the doctor’s name.” Xenition interprets that request and updates the running app—the schedule view, the database records, the email template—all at once. You see the result instantly, not a block of suggested code. The same applies to any template. With a shop template you can change currency, add a discount code field, or connect a payment gateway by describing the workflow. With an admin panel you can rename sidebar sections, alter permission roles, or add a new data table for reporting. **11 industries, 200 starting points** The templates are grouped by industry: healthcare, education, retail, real estate, hospitality, finance, media, logistics, professional services, nonprofit, and internal tools. Each group contains between 15 and 25 templates. A healthcare group includes patient portals, appointment schedulers, and telehealth dashboards. The education group has course managers, grade trackers, and enrollment forms. The internal tools group has asset tracking, helpdesk boards, and expense report managers. Having 200 options means you rarely need to start from a blank page. You find a template that matches the core functionality and then customise it to fit your exact needs. The conversation handles the customisation, so you do not need to know every line of code in advance. **What you get at the end** When you finish describing your changes, Xenition produces the final version of the app. It is not a mock‑up or a preview. It is the actual thing—a working application with your data, your branding, and your logic. You can run it locally, deploy it to a server, or share it with a client. The database schema, API routes, and front‑end components are all real. If you later need to add a feature, you can open the same conversation again or start a new one. The app remains editable in the same way: describe what you want, and Xenition changes the app directly. **What to do next** Open Xenition and browse the template library. Pick the one that most closely matches the project you are building. Describe the first change you want—a company name, a new field on a form, a different colour scheme. The app will update immediately. Keep describing until the app does what you need. That is the whole workflow: start from a template, talk to Xenition, get a working application. There is no separate code generation step. The app is the output.