FigmentFIGMENT FIELD NOTES / 01
20 small sites.
One publishing test.
A page can work in an AI chat and still break when you put it online. We tested what happens after the files leave the chat.
We made 20 small sites with Codex and ran them through Figment's local publishing code. Simple pages and browser tools worked. Some common ways to connect outside services did not.
This is a controlled test of selected hosting patterns. It is not a survey of customer sites or a comparison of AI models. External services were test stubs, not live bookings or payments.
The page was only half the job.
Our problems were at the edges: a script on another domain, an embedded calendar, a network request, a form, and a URL that existed only in the browser.
These were hosting limits, not proof that the AI wrote bad code. We kept the host's security rules in place and changed the files or their settings.
For the embedded calendar and form, we used links instead. Those checks confirm the link destinations, not a working embedded calendar or form delivery.
- Keep scripts and images with the uploaded files.
- Link to your booking and payment providers. Do not assume an embedded tool will work.
- Allow each API domain you need. Test its browser access.
- Give each page a real file. Refresh every URL before you share it.
LOOK AT THE RESULT
Before and after
A chart from a CDN
The host blocks JavaScript from another domain.
What changed: Include the script in the upload.
Every case, not just the good ones.
“Passed” means the page loaded, fit both screens, and passed its named check. Link checks confirm the destination only. They do not confirm a working booking or payment.
What we tested. What we did not.
We wrote these small examples to cover 20 publishing patterns. We did not draw them at random from users. The results describe these files on this host, not the odds that an AI website will work.
- Host
- Figment's real app upload, publish, and HTTP hosting code, running locally. Synthetic accounts. Operating-cost checks disabled for the test.
- Browser checks
- Chromium at 1280 × 800 and 390 × 844. HTTP response, page width, one task per case, browser errors, and blocked requests. Phone size is an emulation, not a real iPhone test.
- Outside services
- Local browser stubs for the calendar, form, script, and API. No third-party account or real transaction. Direct links were inspected without following them.
- Not covered
- Production sign-in, upload UI, DNS, TLS, live delivery, payment, Safari, Firefox, full accessibility, load testing, and custom backends.
- Search visibility
- The app host tells search engines not to index these pages. A shareable link is not the same as a search-indexed business website.