Build a website with App Builder

App and Website Builder is a $79 monthly workspace add on. It activates App Builder and Orders for the workspace.

The interface is named App Builder, but its supported publishing scope is customer facing websites. Use it for landing pages, multi page business sites, portfolios, and storefronts connected to agaro. It does not build a separate ERP, CRM, login system, custom database, admin platform, or standalone application.

#Start a project

Open App Builder from the sidebar. On the start screen you can enter a prompt or choose a starter template.

Good prompts describe:

• The business and intended visitor
• The site's main goal
• Required pages or sections
• Desired tone and visual direction
• Products or services to feature
• The primary call to action
• Whether the site needs a contact form, booking link, or storefront

For example:

Build a five page website for a commercial HVAC company in Northern Virginia.
Include Home, Services, Maintenance Plans, About, and Contact. Use a calm,
professional style. The main action should request a service estimate.

Avoid asking the builder to create a separate user account system or custom business database. Those functions belong inside agaro modules.

#Build mode and Plan mode

The prompt control offers two modes:

Use Plan for larger multi page sites or when the navigation and conversion path need agreement first. Use Build for a focused landing page or a small revision with clear requirements.

#Starter templates

The start screen includes curated prompt templates. A template is not a static theme file. Selecting one launches a real generation using its prepared structure and visual direction.

After generation starts, the editor opens with chat and live preview. Each project keeps its own session, files, versions, and deployment state.

#Refine through chat

Ask for one coherent change at a time. Effective requests identify both the target and the result:

On the home page, replace the generic features row with three service cards for
installation, emergency repair, and preventive maintenance. Keep the current
typography and spacing.

The builder streams progress and updates the preview. If the build fails its health check, automatic repair can run when enabled. An error card remains visible when repair cannot produce a healthy preview.

#Preview and Code

Use the center control to switch between Preview and Code. Preview shows the live sandbox. Code lets an authorized user inspect and edit project files.

Manual code changes are saved as a version so they can be restored through History. A live preview can restart when its temporary sandbox expires; restarting the preview does not delete the project files.

Use the page selector when a project exposes more than one route. If a page is removed, the preview returns to an available route rather than leaving the editor on a dead path.

#Visual editing

The preview supports visual editing controls for selecting an element, editing supported text, and leaving a comment. Use chat for structural changes that affect component logic, navigation, data connection, or several pages.

#History and recovery

Open History to review saved versions. Generation turns and manual code saves append version history. Restore a known healthy version when a later edit breaks the design or behavior.

Restoring a version changes the editable project state. It does not silently replace an already published deployment until you publish again.

#Project management

Use Projects to switch between project sessions. The project list indicates published state where a live deployment exists.

Deleting a project moves it to Builder trash. You can restore it from the start screen. A deleted project that was already published can continue serving until it is explicitly unpublished, so delete and unpublish are separate decisions.

#Storefront and CRM connections

Generated websites can use agaro's public storefront connection instead of inventing a second product database:

• Product content comes from the workspace catalog.
• Store orders return to the Orders module.
• Online payment requires a ready tenant Stripe connection.
• Supported lead capture connects visitors to the workspace CRM.

Before publishing a storefront, confirm that at least one sellable product exists and Stripe is connected under Settings → Payments. The publish dialog reports commerce readiness.

#Credentials and secrets

If a generated site needs an external credential, the builder displays a credential request. Every request requires approval, including in Autonomous mode. Enter the value only in the secure request surface.

Secret values are encrypted before storage and are not returned to the model or displayed later. The project sees only approved runtime access, not the stored plaintext.

#Troubleshooting

#The builder refuses my prompt

Rewrite it as a website request. A landing page for a software product is supported. Building the software product, its accounts, database, or admin system is not.

#Preview is offline

Use the preview restart control. If it remains unavailable, open the build error, review the install or runtime message, and restore the last healthy version if needed.

#A generated product price is wrong

Do not hardcode a replacement in the site. Verify the workspace product catalog and storefront connection, then ask the builder to use the live catalog source.

#My project disappeared

Open the start screen and review Builder trash. Restore the project instead of creating a duplicate when it was deleted accidentally.

#Code changes are not on the public site

The preview and published deployment are separate. Save the edit, verify Preview, then publish a new deployment.