Buying and using it #
These questions usually come up before the purchase or in the first few days after it. One thing up front: you pay 89 euros once and get an open project folder that belongs to you.
Do I really own the code?
Yes. You get an open project folder with no copy protection and no strings attached. You can change it, copy it, back it up and put it on any server. Buy once, yours forever, even if you never speak to us again.
Can I use the Template for client projects?
Yes, that is exactly what it is built for. You buy it, rebuild it for your client via chat and charge your own fee. At the end you can hand your client the complete folder including the guideline and the skills, and they keep maintaining it themselves.
Can I use one Template more than once?
Yes. The purchase belongs to you, not to a single project. If you work with it regularly and build several client projects a year from it, write to us about reseller terms.
Do I get updates?
Your Template keeps running exactly as you received it and needs no update to work. When we develop a template further, you hear about it by email and decide for yourself whether you want the new version. Your own changes stay untouched, because switching is always your decision.
What about the second language version?
Every Template comes finished in German and in English, and both versions are yours. For the rebuild you pick one of them as your basis. If you want to go live in both languages later, the text of the other language is already there and nobody has to translate it.
Can I resell my Template?
The finished website you build from it is yours to sell or hand over, including every file. What does not work is passing the unchanged template on as a template or putting it on a marketplace. Put simply, sell your work, not ours.
Every Template ships with an empty legal notice page and an empty privacy page. We deliberately supply no text for them and let no AI write it either, because that would be legal advice. How to fill both pages properly is covered in the chapter Legal notice and privacy.
AI and tools #
Your Template is built so that an AI understands it. The knowledge sits in the project as plain text, in the file CLAUDE.md and in the seven skills.
Do I absolutely need Claude Code?
No, but it is the path the Template is built for. Claude Code reads the rules and the seven skills on its own and works directly in your files. With another tool you get there too, you just explain more yourself.
Does it work with other AI tools?
Yes. The guideline and the skills are plain text files. Any tool that is allowed to read your project folder and write files can work with them. The difference is that you open the right skill yourself and paste it into the chat, instead of it kicking in by itself.
Start, template rebuild, system knowledge, copywriting, SEO, design system and quality check. They live in the hidden folder .claude/skills and are written to be read by people. What each one does is covered in the chapter The seven skills.
What does using the AI cost me?
The Template costs 89 euros once, the AI is billed separately. For Claude Code you need a subscription with Anthropic, starting at around €20 a month. For rebuilding a website the smallest tier is usually enough, and after that you only need the AI when you actually want to change something.
Do I need to know how to code?
No. You need two commands in the terminal, everything else happens in conversation in plain English. The commands are spelled out step by step in the chapter First steps. If you have ever installed a program, you will manage this.
How much of it will I understand myself?
More than you expect and less than a developer. After the rebuild you know which folder does what, where your text lives and how to start a change. That is enough to maintain your website yourself for years. The shortest way there is the chapter How your Template is built.
When setup gets stuck #
Almost every start-up problem has one of five causes. Which kind of Template you have decides the first command. One look in the folder tells you.
| What you see in the folder | How you start the preview | What you open |
|---|---|---|
There is a folder called src | Once npm install, then npm run dev every time | http://localhost:4321 |
An index.html sits at the very top | npx serve ., there is no build step here | the address that appears in the terminal |
The terminal says the command was not found
Then Node.js is missing or the terminal does not know it yet. Install the LTS version from nodejs.org, close the terminal completely afterwards and open it again. Only then does it know the new commands. These two lines tell you whether everything is there. Each one answers with a version number.
- node -v · shows whether Node.js is installed
- npm -v · shows whether the package manager came along
The port is already in use
Usually the preview is still running in an earlier window. Find the old terminal and stop it there with Ctrl and C. If you cannot find it, the preview moves to the next number by itself and the terminal shows a different address such as http://localhost:4322. Just use that one.
The build stops with an error
The most common reason is where the folder lives, see the second to last question in this block. Otherwise the rule is simple: paste the error message into the chat in full, not only the last sentence. The line that matters is almost always in the middle.
The page stays blank
Look at the terminal first, it usually already names the cause, most often a typo in the file you changed last. If everything is quiet there, reload the page while holding the shift key. If that does not help either, stop the preview with Ctrl and C and start it again.
My folder is in OneDrive, Dropbox or on a network drive
This is the most common cause of errors nobody else can explain. Cloud folders sync in the middle of the process and the paths get too long. Put the project directly on your hard drive, for example under C:\websites\myproject, and work there. For your backup you copy the folder into the cloud afterwards.
None of this applies
Then pass the error on instead of interpreting it. Your AI reads error messages for you and knows how your project is built on top of that.
The start is stuck. Here is the complete output from the terminal. Tell me in plain words what is causing it, what I should do next and whether I need to install anything for it. If you can fix the cause in the project yourself, do it and explain briefly what you changed.
Rebuilding and content #
The rebuild happens in conversation. How good the result gets depends almost entirely on how clear your instruction is. You can copy the lines below and fill in your own details.
How do I change something I cannot find?
Do not search, describe. Your AI knows the whole project and finds the spot in seconds. Say where the text sits, which page and which area, and quote a few words from it. That is enough.
On the home page, in the upper area, there is the sentence “paste the old sentence here”. Show me which file it lives in and change it to “paste the new sentence here”. Then tell me whether the same text appears anywhere else.
The AI broke something, what now?
This can almost always be undone. Work through it in this order.
- Change nothing else. Every additional change makes undoing harder.
- Say it in the same conversation. Your AI knows what it touched last and can take it back.
- If the conversation is closed, restore the affected file from your last copy.
- If that still leaves you stuck, unzip the original archive into a second folder and have the file taken from there.
Your last change broke something. Undo it completely and restore the state from before. Then tell me which files you touched and what went wrong, before we try it a second time.
Copy the unzipped folder aside once before you start, and again whenever you like an intermediate state. Two copies on your hard drive cost nothing and take the risk out of every experiment. The rhythm for this is in the chapter Maintaining and extending.
How do I phrase it so the AI understands me?
Three details make the difference: the place, the goal and the limit. So where something sits, what should be different afterwards and what stays untouched. An instruction without a limit leads to more being rebuilt than you wanted.
On the services page, change the heading of the third block to “paste the new heading here”. The text below it stays exactly as it is. Do not touch any other page. Show me in one sentence what you intend to change before you do it.
Can I add or remove pages?
Yes, both. When adding, what matters is that the new page makes it into the navigation, into the footer and into the sitemap file for search engines, otherwise nobody finds it. When removing, the same path applies in reverse, plus a redirect if the page was already live.
Create a new page called “Pricing”. Use the structure of the existing services page as a model so the layout and spacing match. Add it to the navigation, to the footer and to the sitemap, with its own page title and its own description. Show me every changed file at the end.
The AI writes down details that are not true
That happens when a gap needs filling and the detail is missing. Always supply numbers, names and evidence yourself and say explicitly that nothing may be added that you did not provide. One section less beats one invented testimonial. The full version is in the chapter Text and content.
Technology and hosting #
In the end your website is a set of finished files that a server only has to hand out. Most answers in this block follow from that.
What hosting do I need?
Almost any. Simple web space from around €3 a month is enough, a static host works too. The options and how they differ are in the chapter Going live. There is one exception: if your Template comes with a PHP contact form, the web space has to support PHP.
Do I need a database?
No. There is no database, no login and no admin interface that somebody would have to keep up to date. That is exactly what makes the website fast, cheap to run and hard to attack.
Does the contact form work?
It looks finished, but as delivered it sends nothing, because we do not know your mailbox. Before going live you either connect a sender or you replace the form with your email address and your phone number. A form that leads nowhere does more harm than good.
How fast is the website?
Fast, because nothing is calculated when someone opens it. The biggest lever after that is yours, and it is images. Have every photo of your own scaled down and converted to WebP before it goes in, and the speed stays the way it shipped.
What about email mailboxes?
Mailboxes belong to the domain, not to the website. You create them at your host or your domain provider, and a few are usually included in the plan. Use an address on your own domain for the website, it reads as more reliable than a free mail address.
After the launch #
A website is not finished after going live, it is reachable. The effort after that stays small if you give it a rhythm.
How do I change something later?
Exactly as before. You open the project folder, tell your AI what should be different, look at it in the preview and upload afterwards. From the second time on, a text change takes minutes.
How often do I have to do something?
For the website to keep running, nothing at all. As a rhythm it is enough to check opening hours, prices and contact details once a quarter, and once a year to ask whether the home page still describes what you do today. Everything else is in the chapter Maintaining and extending.
What do I do with the old website?
Back it up first, then replace it. Download the old files and your existing text before you overwrite anything. After that the new website goes into the same directory. The addresses are what matters: if an old subpage had visitors from Google, set up a redirect to the matching new page.
Do I need a backup?
Yes, and it is simple. Your project folder is the backup, so copy it regularly to a second drive or into the cloud. If you like, put the project into version control as well, though that is not required.
What happens if I touch nothing for months?
Your website keeps running as long as web space and domain are paid for. If you want to change something again after half a year, the building blocks may be fetched again with the first command. That is normal and takes a few minutes once.
Getting help #
For almost every problem there is a fast order and a slow one. This is the fast one.
Ask your AI in the same conversation
It knows your project folder, your latest changes and the rules of your template. Describe what you did last and what you see, and paste error messages in full. That solves the large majority of cases.
Look it up in the right chapter
The eleven chapters cover the way from the ZIP file to long after the launch. Everything that can go wrong while publishing is collected in the section When something looks wrong.
Write to us
If that leaves you stuck, send an email. What belongs in it is in the last section of this chapter.
What do I do when I am stuck?
Change the level instead of repeating the same attempt. Describe to your AI not the route you took, but the goal you want to reach. Very often there is a simpler way there that you could not have known about.
What details make a question easy to answer?
Four things turn a question into an answerable question: which template, what you did last, what you expected instead, and the error message 1:1. For design questions a screenshot helps, for errors the copied text helps more than any picture.
Summarise our problem so an outsider understands it: which template, what I did last, what happens, which error message comes up exactly and what we have already tried. Write it as a short paragraph I can paste into an email.
Where do I find what in this documentation?
Chapters 01 to 03 get your Template running, 04 to 07 turn the template into your website, 08 takes it live and 09 keeps it in shape. If you do not know where to look, the overview is the fastest way.
Something is stuck during the launch, where do I look?
Everything that can go wrong while publishing is in the chapter Going live, in the section When something looks wrong. From a file list instead of the home page, through missing styling, to the security warning, every known picture is listed there with its cause.
If none of this fits #
Some questions are on nobody's list. In that case write to us at hello@ai-website.com, in English or in German.
So the answer fits on the first try, tell us these four things.
- Which template. The name is in the folder and in your purchase confirmation.
- What you did last. The last command or the last sentence you sent your AI.
- What you see. The error message copied 1:1 or a screenshot of the spot.
- Which operating system. Windows or Mac, ideally with the version.
Every question in this chapter reached us in exactly this form once. If yours joins them, it will be here next time. Until then: your website is a folder on your hard drive, and one copy of it makes every experiment safe. If you want to know what comes next, look at Maintaining and extending.