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

Sites is an experimental capability that is off by default. Enable it in Settings > Cowork, then use the Sites entry to choose a template or describe the website in a Cowork task. Generate and inspect a local result before publishing.

1. Describe the audience, purpose, required information, and interactions.
2. Start from a résumé, blog, product, portfolio, company, or blank template and generate a local workspace.
3. Open its local preview and refine content and mobile layout in the original conversation.
4. Review a specific version before choosing static H5 export, EvoX hosting, or Linux + SSH publication.

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

Choose resource types using the table above and declare them in evox-site-manifest.json. Manage database schema changes with ordered, immutable SQL migrations.

1. Declare variables in bindingSchema.environment, marking required and secret values.
2. Supply real values in hosting configuration, never client code or the manifest.
3. Rebuild and publish after changes, checking the configuration used by the new version.

Keep names only in .env.example; inspect secret handling before publication.

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