Start with a template or a prompt to create, preview, and share interactive websites in Qoder.
Availability: Individual plans (Free, Lite, Pro, Pro+, and Ultra) and business plans (Teams and Enterprise). The individual Free plan supports static website deployment only; database and storage services are not supported.
Sites is free for a limited time at launch, with usage limits. Reaching a limit may temporarily restrict creating sites or public access to sites with high usage. You can still edit and manage existing sites. Usage is counted across all sites in your account, and limits may be adjusted during the free period.
Create your first site
Select Sites in the sidebar and click Add site. Qoder opens a new task with @sites referenced in the composer. Choose a starter template or describe your requirements directly.
Start from a template
Choose a template above the composer as a starting point for the page layout and features.
You can also choose a template from the Sites start page. Qoder opens a new task, prepares the template attachment, and keeps the text already in the draft. Once the attachment is ready, check the template, add any instructions, and send. If preparation fails, retry the attachment in the draft.
- Select a suitable template and wait for its attachment to finish preparing.
- Check the attachment in the composer. Selecting a template keeps your existing instructions; when switching templates, confirm that the attachment is the version you intend to use.
- Optionally choose a design style, add content, layout, and interaction requirements, and send the task.
@sites chip alone, with no text or ready attachment, cannot submit an empty task. Check attachment readiness before sending. Add goals, content, and design requirements when you need a more specific result.
Describe what you need
If you already have a clear idea, reference @sites in a new task and describe the website. Explain who will use it, what it should help them do, which information to display, and the actions it should support.
For example, create a dashboard for a project meeting:
Build a site with Agent capabilities
A site can call an Agent service in Qoder Cloud Agents to run a task when a visitor interacts with it. Tasks can include processing data, retrieving information online, generating text or images, and generating page content dynamically. Outputs can be saved in the site's database and storage, without connecting a model or maintaining a backend yourself.
Describe what visitors will submit, what the Agent should produce, and how the results should be displayed and saved. For example, you can request a sales analysis site:
Preview and refine
When generation finishes, click the website artifact in the response to open its preview in the Sites panel on the right. You can also open the site artifact from the task outputs. Interact with buttons, filters, and links directly, or use Show workspace fullscreen to expand the preview.
For the project dashboard, switch owners and task statuses to check that summary counts, filtered results, and task details agree. If you supplied your own materials, check that the page represents them accurately.
Refine a page on the design canvas
Switch to Design in the Sites work surface and select the content to adjust. Double-click editable text and press Enter to confirm, or use available property controls to adjust styles or layout. Direct edits are saved to the current Site draft; refresh to check the result.
For changes that need the Agent, prepare a request with annotations, natural-language instructions, or the canvas drawing tools. Check the task input before sending; an unsent request does not trigger Agent changes. Draft edits do not automatically update a published website. Publish the updated version when it is ready.
Request changes in chat
Continue in the current task and describe what you want to change:
Annotate a specific element
To adjust a particular button, heading, or card, identify it directly in the preview:
- Click Annotate at the top of the Sites panel, then click the element you want to change.
- Enter a request in Site annotation comment, such as "Change this card to show the overdue task count," and click Add annotation.
- The annotation is attached to the composer as a webpage comment. Send the message to ask Qoder to make the change.
- Review the new preview. Click Stop annotating to interact with the page again.
Publish and share
When the site is ready, publish a version and choose who can access it. New sites are accessible only to you by default, so you can check the published result first.
Sites provides website generation and a service for distributing content through website links that others can access. To comply with China's Measures for Labeling AI-Generated and Synthetic Content, AI-generated content labels on sites cannot be removed. Actual access remains subject to the selected permissions and the access scopes supported by your plan.Article 10 of the Measures for Labeling AI-Generated and Synthetic Content sets out the following requirements (translated from the Chinese original): Users who publish generated or synthetic content through online information content distribution services must proactively declare it and use the labeling features provided by the service provider. No organization or individual may maliciously delete, tamper with, forge, or conceal the generated or synthetic content labels required by these Measures; provide tools or services for others to carry out such malicious acts; or harm others' lawful rights and interests through improper labeling practices.
Publish the current version
- Review the latest preview's content, links, and interactions for your intended audience.
- Click Publish in the upper-right corner of the Sites panel and wait for Published.
- Open the publishing details to find the site address, then click Visit to check the published page.
Choose your audience
Click Share in the site list or site details. Select Change access scope and choose an audience.
For Only invited users can access, enter the person's email address or Qoder UID, follow the interface to add them, and confirm that they appear in the Invited users list. A Qoder UID is available under Settings → Profile → Edit.
Use Copy link to share the address after configuring access. Visitors to restricted sites must sign in with a Qoder account that has permission. Forwarding a link does not grant access. Permission to open and use a site is separate from permission to edit it.
Individual plans
Individual plans support three access scopes:
| Visibility | Use case |
|---|---|
| Only you can access | A personal work dashboard or a version you are not ready to share. |
| Only invited users can access | Project updates or a feature prototype for selected users. |
| Anyone can access | A public product introduction or feature demo. |
Teams and Enterprise
Site access on Teams and Enterprise plans is controlled by enterprise policy. To make a site available on the internet, ask an enterprise administrator to enable permission for internet-visible Sites in the enterprise console. After that permission is enabled, choose public access for the specific site.
| Visibility | Use case |
|---|---|
| Only you can access | A personal dashboard or a version you are not ready to share. |
| Only invited users can access | Project updates or a prototype for selected organization members. |
| Organization members can access | A project portal or internal tool for your organization. |
| Anyone can access | A public product introduction or demo, after an enterprise administrator enables internet visibility. |
Update a published site
When project progress changes, open Sites from the sidebar and find the dashboard. Choose More → Locate conversation to return to the original task and describe your changes in the conversation.
For example, attach this week's task list and ask Qoder to update progress and due dates while keeping the layout. Review the new preview, then click Publish to update the live version.
The preview and published version are separate. A chat edit or new preview does not automatically replace live content. Visitors see the update at the site address after you publish again.