Stop building every site from a blank page

Stop building every site from a blank page

Most developers I know start a new project the same way: empty editor, empty directory, and a long list of things that need to exist before the actual work starts. Login, layout, database, routing, admin screens — the stuff every site needs and nobody wants to rebuild. Even when an AI assistant writes the code, you still spend time moving it into place, wiring it together, and checking whether it matches what you asked for. The problem is the starting point. A blank page gives you nothing to react to.

Starting points are the product

The difference between an easy project and a hard one is rarely the idea. It's how much groundwork already exists when you begin. If you have a working thing to change, you can improve it. If you have nothing, you build from zero.

That's why a catalog of ready-made sites matters. Xenition includes 200 ready-made site templates across 11 industries. A clinic booking site, an internal admin, a shop — you start from one that already fits, then make it yours.

What the templates are

A template here is not a static page you look at and rebuild by hand. It's a starting point you can work from directly. You open it, see how it's put together, and change what you need.

200 templates is a real number. Across 11 industries, it takes in a lot of common projects. You don't need the perfect match — you need the closest one. The distance between what you want and what's already there is work you don't have to do.

The examples in the catalog

• A clinic booking site. That's the kind of site a medical practice needs: patients can see what's available and book an appointment. You take that structure and add the practice's real hours, staff, and services.
• An internal admin. That's the tool the people inside a company use to keep records straight. You take the existing screens and connect them to your own data.
• A shop. That's the kind of site that shows products and takes orders. You swap in your products, prices, and payment details.

These are three different industries with three different needs. The common thread is that someone already did the boring part.

How the workspace fits in

Xenition works by conversation. You describe what you want, and it opens the real thing rather than handing you text to paste somewhere else. With the templates, the flow is shorter: describe the project you need, start from the template that fits, and adjust.

The template is the baseline. Your conversation with the workspace is how you steer it in your direction. 'Change the booking form to ask for a reason' or 'replace the product grid with a list' — changes like that move the starting point toward your goal.

What you stop rebuilding

A clinic booking site needs more than a form. It needs storage for appointments, a way to avoid double-booking, a view for the staff, and a view for the patient. An admin needs records that persist and a way to edit them. A shop needs products, prices, stock, and a checkout that leads somewhere. These are real systems. Building them from nothing is days of work. Starting from a template that already has the shape of the system is a different task: you're modifying, not inventing.

The same applies to the internal admin. The screens for adding, editing, and viewing records are part of what a ready-made admin gives you. What's missing is your specific data and your specific rules.

The part that's still yours

Nobody is saying the template does the whole job. Your project still has its own logic: how appointments relate to staff, how stock interacts with orders, how roles control who sees what. That's where your time goes now, and it's the part worth spending time on.

The template is the floor. Your work is what sits on top of it.

What to do next

Look at the 11 industries in the template catalog. Find the one that matches your current project, or the one closest to it. Open that template in Xenition. Describe the changes you need, and work from the version that already fits instead of the empty page.