A prompt that builds your site for One9x

Most trouble with an AI-built site shows up at the end: a React project instead of a finished site, a form that posts nowhere, a server the site cannot have. All of it is avoidable if the tool knows where the site is going before it starts. Paste this at the start of your chat — or into a chat where the site is already built — and you get something you can drop straight onto One9x.

It works whether or not the tool can open web pages: the rules it needs are in the prompt, and a tool that can browse also reads our docs.

The prompt

I'm going to host this website on One9x Pages (https://one9x.com), a static site host. If you can open web pages, read https://one9x.com/llms.txt and the pages it links to before you start. Then follow these rules:

1. Static files only. The finished site is plain HTML, CSS, JavaScript and assets. No server code: no PHP, no Node or Express server, no API routes, no serverless functions, no database, no server-side rendering.

2. No build step if possible: plain HTML, CSS and vanilla JavaScript that works by opening index.html in a browser. If you do use a framework (React, Vite, Next.js static export), tell me the exact build command and the folder it creates (for example dist/). That folder is what I upload, not the project's source code.

3. index.html sits at the top level of the folder I upload. Other pages are their own HTML files (about.html, or about/index.html). If pages are drawn in the browser (React Router or similar), remind me to choose "Single-page app" in Deploy options when I upload.

4. Relative paths for links and assets (images/logo.webp), never file:/// or C:\ paths. Match upper and lower case exactly in file names.

5. Keep it small: every file under 10 MB and fewer than 500 files in total. Compress images (WebP or JPEG at a sensible width).

6. No secrets: no API keys, passwords or tokens in any file. Everything I upload is public.

7. Forms: do not connect them to a database, CRM, email service or a third-party form service. One9x has a built-in form service. For every form:
   - post to /_one9x/forms/<form-name> with method="POST", where <form-name> is lowercase letters, digits, - or _ (for example: enquiry);
   - use simple field names: name, email, phone, message;
   - put this hidden spam trap inside the form, exactly as written:
     <input name="_gotcha" style="display:none" tabindex="-1" autocomplete="off">
   - put this spam check inside the form, just before the submit button:
     <altcha-widget auto="onsubmit" challenge="/_one9x/captcha/challenge"></altcha-widget>
   - and load its script once on the page:
     <script type="module" src="/_one9x/altcha.js"></script>
   - to show my own thank-you page, add
     <input type="hidden" name="_next" value="/thanks.html">
     and create thanks.html.
   Do not add JavaScript that submits the form; it posts on its own.

8. When you are done, give me:
   - every file, each with its full path inside the site folder;
   - for each form: its name and its field names, each with a type (text, long text, email, number, checkbox) and whether it is required, so I can create the same form in the One9x dashboard;
   - a checklist of placeholders I must replace before publishing: phone numbers, addresses, prices, reviews, photos.

If you have already built a site for me in this chat, don't start over: check that site against every rule above, fix everything that breaks them, and give me the complete, corrected files as in rule 8.

The limits in rule 5 are the Free plan’s. On a paid plan they are higher — see Limits and loosen the numbers to match.

Already have a site? Paste the same prompt into the chat where the tool built it. The last line has the tool check what it made against every rule and hand back corrected files instead of starting over — worth doing before publishing anything built without the prompt, while a source-code folder, a form that goes nowhere or a hard-coded key is still cheap to fix.

Then put it online

1. Save the files into one folder, using the paths the tool gave you.
2. If the site has a form, open your site’s Widgets → Forms in the dashboard, turn on Accept form submissions, and create each form with the name and fields the tool listed — the names must match exactly. Every plan includes 250 submissions a month or more. Widgets has the details.
3. Drop the folder on your site’s Overview tab, then Upload and stage and Make live, as in Deploy from the dashboard.
4. Test the form once yourself and check the submission shows up under Widgets → Forms.

If the tool used a framework after all, build it first and drop the folder the build creates — the page for your tool has the steps.