Skip to content

FAQ

No. AISiteEngine is its own CMS. WordPress is only ever used once, as a source to import existing content from.

In your own Cloudflare account — a per-site D1 database, an R2 bucket for media, and a Pages project for the site. Nothing is shared with other clients.

Yes. The data is standard SQL in D1 and the files are plain objects in R2. Both belong to your Cloudflare account, so you keep them whether or not you keep using AISiteEngine.

The public site is static HTML served from Cloudflare’s edge cache. There is no server rendering per request, so traffic spikes do not slow page loads.

As long as the next build and deployment — usually a couple of minutes.

Yes, but there is no live co-editing. The last save wins; if two people edit the same record, the second save overwrites the first. Split long articles into separate records, or coordinate.

Content has a soft Trash — recoverable. Taxonomies and terms are deleted permanently, with a confirmation that states what will be removed.

Yes. A custom domain is a proxied DNS record pointed at the Pages project, so Cloudflare’s cache and TLS are in front of it.

No. Only publish records are generated into the static build.

Set the record back to Draft and save. That removes it from the next build.

Pages are static HTML with real URLs, and each record has its own slug and title. Metadata and sitemap generation are part of the site build.

Anyone with media.read on that site. Media URLs themselves are public — do not store confidential documents there.