Sites

Create and host websites and web applications with EvoX

EvoX Sites turns a natural-language brief into a reviewable web experience. In the desktop app, you can create a local site workspace, preview and continuously refine it, then export a static H5 package, use EvoX-managed hosting, or publish to your own Linux server.

Site creation and publishing are separate stages. You can complete and review the local version first, then explicitly choose how to publish it.

Get started with Sites

Start with a short brief or choose a resume, blog, product, portfolio, company, or blank-site template.

1. Describe your site: Explain the audience, purpose, expected behavior, and required information.
2. Generate and preview: EvoX creates a local workspace and a reviewable site preview.
3. Keep refining: Continue editing copy, images, interactions, and mobile layouts in the original site conversation, and add existing project files when needed.
4. Export or publish: After review, export static H5, use EvoX-managed hosting, or publish to your own server over SSH.

The local preview normally runs on a loopback address and lets you check content and interactions before publishing.

Use prompts to create Sites

These are suitable tasks for the EvoX Sites workflow.

Create an operations request board. Team members should submit requests, update status,
and filter by owner. The records must persist, so declare a D1 binding.

Prepare this existing product site for release. Preserve its facts and information architecture,
repair the mobile layout, and deliver a local preview first.

Create a resource-library site. Each record has a title, tags, and description, and can include
an uploaded attachment. Store metadata in D1 and files in R2. Mark missing facts as [replace].

A useful brief can include the audience, primary job, facts to preserve, persistence requirements, and publishing method. Mark names, prices, customers, qualifications, or statistics that have not yet been supplied as [confirm] so they can be completed before release.

Understand projects, versions, and deployments

EvoX creates a site project in a local workspace and uses evox-site-manifest.json to describe runtime and hosting resources. A site can remain local or be published from the desktop after review.

The v2 site manifest supports these core settings:

runtime        static | worker
bindingSchema  d1 / r2 / environment
migrations     ordered, immutable SQL migrations

• static is for sites centered on content and client-side interactions.
• worker is for sites with server logic, build steps, or a runtime entry point.
• D1 stores structured data; R2 stores files and uploads.
• Environment entries can declare a name, required status, and secret status.
• Export and publishing start from a specific reviewed version, supporting later updates and rollbacks.

When online hosting is unnecessary, export a static H5 package with index.html as its entry point. EvoX-managed hosting publishes a reviewed version from the desktop. For your own server, the Linux + SSH publishing path checks the host fingerprint, destination, uploaded files, and real production URL.

Choose a Site type

Match the site to the data it needs to retain.

Configure data, files, and environment

EvoX Sites can declare runtime resources together in evox-site-manifest.json:

• Use D1 for form records, task state, content indexes, and other structured data.
• Use R2 for images, attachments, and other uploaded files.
• Use environment entries for API origins, third-party configuration, and server credentials.
• Use ordered, immutable SQL migrations to manage database schema changes.

To configure environment entries:

1. Declare the variable name under bindingSchema.environment.
2. Mark whether the variable is required and whether it is secret.
3. Provide the actual runtime value in hosted configuration.
4. Rebuild and publish after changing configuration so the new version uses the latest values.

Secrets are managed by the runtime instead of being written into client code or the site manifest. A local .env.example can list variable names so project members know which configuration is required.

Review before sharing

Before publishing or sharing, review the site as the final visitor will experience it.

• Confirm that the intended version is selected.
• Review names, pricing, contact details, customer claims, qualifications, and legal copy.
• Test desktop and mobile layouts for wrapping, touch targets, overlap, and horizontal overflow.
• Exercise forms, uploads, and persistent data.
• Confirm that client assets contain no keys, tokens, private origins, or other secrets.
• Test the real URL after publishing and record the version and validation result.

Take down and roll back

EvoX-managed Sites can stop a current publication and roll back to a reviewed version. For sites published to your own server, use the publication receipt to reconcile the destination, live version, and real URL before rolling back or taking the site down.

Before acting, verify the site project, target environment, and version. Afterwards, visit the real URL again to confirm the result.

Currently supported Site capabilities

Related docs

• Projects and chats
• File handling
• Troubleshooting

EvoX Docs · Features · Workflows