14.1 Overview

Website Builder is one of the major specialized workspaces inside AIUNIFY PROS SUITE.

Unlike the Standard AI Generator covered in Chapter 12, Website Builder is a persistent, visual website-creation environment designed to let a subscriber:

  1. Describe a website or web interface in natural language
  2. Optionally provide a reference image
  3. Generate an initial AI-designed website
  4. Preview the generated design
  5. Continue modifying it through Design Chat
  6. Make targeted visual edits to individual page elements
  7. Upload or modify website images
  8. Preview desktop and mobile layouts
  9. View generated source code
  10. Download the generated site as HTML
  11. Save the website as a Website Project
  12. Reopen previously saved projects for additional editing
  13. Later publish the site to a subdomain

The Website Builder landing area tells the user:

“Bring your imagination to reality.”

and:

“Describe any web interface. Our AI will instantly design, build, and deploy it. No coding required.”

Publishing, subdomains, custom domains, and detailed project management are covered separately in Chapter 15.

14.2 Where Website Builder Is Located

Navigate to:

Sidebar → Core Tools → Website Builder

The Website Builder route is:

/website

The current page requires an authenticated PROS SUITE session. If you are not signed in, it redirects to Login.

14.3 Website Builder Is Different from the Standard Generator

Website Builder should be understood as a project workspace, not a one-request text generator.

A normal workflow looks like:

Describe Website

Generate Initial Design

Preview Website

Continue Conversation in Design Chat

Modify Entire Design or Selected Elements

Preview Desktop / Mobile

Save Project

Continue Editing Later

This is fundamentally different from:

Prompt → Text Output → Download

used by many Standard Generators.

14.4 Website Builder Uses Saved Projects

The main Website Builder page contains:

Your Projects

and a:

+ New Project

control.

Previously saved websites appear as project cards.

Each project can include:

  1. Generated website code
  2. Project Name
  3. Design Chat messages
  4. Last-updated information
  5. Published subdomain, when one exists

The current project-loading workflow restores the saved website design, Chat messages, and saved subdomain when reopening a project.

14.5 The Recommended New Website Workflow

For a complete new website, the most direct current workflow is the large creation area at the top of Website Builder.

You will see:

Bring your imagination to reality.

and the Prompt field:

“Ask AIUNIFY to build a website that can...”

Enter your website requirements there before entering the design workspace.

14.6 What to Include in Your Initial Website Brief

Your initial Prompt should describe the website in enough detail for the AI to establish a strong first design.

Consider including:

Website Purpose

What is the site supposed to accomplish?

Business or Brand

What company, organization, product, or service is being represented?

Audience

Who should the website appeal to?

Main Sections

For example:

  1. Hero
  2. About
  3. Services
  4. Features
  5. Pricing
  6. Testimonials
  7. FAQ
  8. Contact
  9. Call to Action

Visual Style

For example:

  1. Professional
  2. Enterprise
  3. Minimal
  4. Bold
  5. Luxury
  6. Futuristic
  7. Modern SaaS
  8. Corporate

Brand Direction

Include:

  1. Colors
  2. Desired visual mood
  3. Logo placement
  4. Typography direction

Interactions

Examples:

  1. Navigation
  2. Forms
  3. Dropdowns
  4. Tabs
  5. Modals
  6. Carousels
  7. Buttons

Responsive Requirements

Mention mobile expectations when they are especially important.

14.7 Example — Weak Website Prompt

A very broad request such as:

Build a business website.

gives the AI little specific direction.

It can still attempt a design, but more editing may be required afterward.

14.8 Example — Strong Website Prompt

A stronger initial request could be:

Build a premium B2B software website for a company serving enterprise sales organizations. Create a bold hero with headline, subtitle and two calls-to-action, followed by a systems overview, business outcomes, industry use cases, enterprise benefits, testimonials, pricing call-to-action and footer. Use a clean modern technology aesthetic, strong visual hierarchy, responsive mobile layout and professional blue branding.

The more complete the initial brief, the better the first generation can reflect your desired website.

14.9 Starting from a Suggested Website Type

Below the creation Prompt, Website Builder displays:

Try one →

with four current suggestion options:

  1. Auth Login Form
  2. Billing Settings
  3. Event Scheduler
  4. Workspace Dashboard


Selecting one fills the Prompt field with a more detailed example request.

14.10 Suggestions Do Not Immediately Generate

Selecting a suggestion only places its associated Prompt into the Website Builder Input.

For example, selecting:

Workspace Dashboard

loads instructions for a modern dashboard with elements such as a Sidebar, project cards, Quick Actions, and recent activity.

You can edit that Prompt before generating.

14.11 Customize Suggestions Before Generating

A suggestion is best treated as a template.

For example:

Workspace Dashboard

can be changed from a generic dashboard into:

Create an enterprise insurance agency sales dashboard with producer metrics, pipeline cards, recent leads, policy activity, commission summaries and quick actions.

This lets you use the example structure while making the design specific to your business.

14.12 Attaching a Reference Image

Website Builder's initial creation area provides:

Attach Image.

The current file selector accepts:

image files.

You can attach a reference image such as:

  1. A design inspiration image
  2. Screenshot
  3. Mockup
  4. Existing interface
  5. Layout example
  6. Brand visual

14.13 Image Preview

After attaching an image, Website Builder displays a small preview above the Prompt.

An X control is available on the preview to remove the image before starting the website.

14.14 Pasting an Image into the Initial Prompt

The initial Website Builder Prompt also detects an image pasted from the clipboard.

When an image is present in clipboard data, Website Builder loads it as the selected reference image.

This can be convenient when working from a screenshot.

14.15 Text Is Not Required When an Image Is Attached

The initial Generate control becomes available when either:

  1. Prompt text exists, or
  2. A reference image has been selected.


However, a reference image plus a clear written instruction will generally give the AI more explicit guidance than an unexplained image alone.

14.16 Generating from the Initial Builder

When your initial brief is ready, select the circular Generate/Send control.

Website Builder transfers your request into the Website Playground, where the AI creates the design.

If a reference image is attached, it is carried into the initial design request.

14.17 Initial Keyboard Shortcut

The current initial Website Builder Prompt uses:

Shift + Enter

to begin the project.

This is different from several other PROS SUITE workspaces.

For this initial Website Builder screen:

Shift + Enter → Start Project

You can always use the visible Generate control instead.

14.18 Initial Website Generation Cost

The current full initial Website Builder generation workflow requests a deduction of:

500 PROS SUITE Tokens

before generating the new design.

If the required Tokens cannot be deducted, Website Builder stops the generation.

14.19 Important Cost Distinction

Website Builder has different Token behavior for:

Full Initial Website Generation

500 Tokens in the current source workflow.

Subsequent AI Design Chat Modification

10 Tokens per current AI editing request.

This is one of the most important Website Builder operating concepts.

14.20 Plan the Initial Site Before Spending the Full-Generation Cost

Because initial generation is substantially more expensive than later AI editing, prepare the first Prompt carefully.

Before starting, consider defining:

  1. Website goal
  2. Sections
  3. Audience
  4. Brand style
  5. Required functionality
  6. Important content
  7. Calls-to-action
  8. Desired mobile behavior

A strong first brief can reduce the need to restart from scratch.

14.21 What Happens During Initial Generation

After the project begins, Website Builder:

  1. Adds your request to the Design Chat.
  2. Enters a loading state.
  3. Verifies/deducts the initial Token requirement.
  4. Sends the website request to the selected AI Model.
  5. Streams the generated design response.
  6. Begins updating the website preview when usable website code becomes available.
  7. Completes the generated design.
  8. Adds the AI result to the Design Chat.


14.22 Live Design Generation

Website Builder does not necessarily wait for the entire AI response before changing the Preview.

While code is streaming, the workspace checks for usable generated website code and can update the Preview progressively.

This means you may see the website begin taking shape while AI generation is still underway.

14.23 AI Is Crafting Your Design

Before useful streaming content arrives, Design Chat can display:

“AI is crafting your design…”

Allow the generation to complete before beginning another edit.

14.24 Thinking Panel

As generation progresses, Website Builder can display a:

Thinking…

panel containing streamed design information.

This can be expanded or collapsed.

Its purpose is to provide visual feedback while the design is being produced.

14.25 Completed Design Card

After a generated design response is recognized, Design Chat can display user-facing status elements including:

  1. Thinking
  2. Generated action indicators
  3. Completed milestone
  4. New Design Generated
  5. Updated Viewport
  6. What was built
  7. Up next


These help summarize the design activity.

14.26 Important Note About the Action Indicators

Some of the action rows shown in the completed design card are derived from words found in the AI response rather than being a literal backend activity audit.

The source itself describes those derived actions as visual enhancements based on generated text.

Therefore, labels such as generated structure or compiled activity should be treated as interface progress presentation, not as a formal technical deployment log.

14.27 Up Next

After a completed design, Website Builder can present an:

Up next

suggestion and a:

Build it

button.

The suggestion is derived from the design content or from a suggestion produced by the AI.

14.28 Using Build It

Selecting:

Build it

sends the displayed Up Next suggestion back through Website Builder's Design Chat as another AI modification request.

Because it invokes another Design Chat modification, it should be treated as another AI editing action rather than a free informational button.

14.29 The Website Builder Workspace

After the project opens, the main working area has two primary sections:

Design Chat

Used to instruct the AI and review design-generation activity.

Website Preview

Displays the generated website visually.


A third Visual edits settings panel can appear when a specific element is selected.

14.30 Design Chat

The left-side workspace is titled:

Design Chat

with:

AI-Powered Assistant.

Use Design Chat for natural-language modifications to the generated site.

14.31 Empty Design Chat

When no Design Chat messages exist, it displays:

“Ready to build something iconic?”

and:

“Describe your vision or upload a reference image to begin.”

This can occur when entering the Playground through + New Project without first using the main Website Builder brief.

14.32 + New Project

The Website Builder Projects area includes:

+ New Project

which opens the Website Playground directly.

In that direct empty workspace, the user can begin through Design Chat.

For the clearest full-site creation workflow, the initial Website Builder brief at the top of /website remains the recommended starting point because that path specifically invokes the verified full initial-generation process.

14.33 Editing Through Design Chat

Once a website exists, use the Design Chat Prompt:

“Ask for modifications or share a vibe...”

Examples:

Make the hero section more premium and enterprise-focused.

Change the primary color to deep navy blue.

Add a testimonials section below the features.

Make the navigation sticky.

Add a pricing section with three plans.

Improve the mobile spacing throughout the page.

14.34 Sending a Design Chat Modification

To send an edit:

  1. Enter the requested change.
  2. Press:
  3. Enter

or select the arrow Send control.

3. Website Builder adds the instruction to Design Chat.

4. The AI updates the design.

The Design Chat footer explicitly tells users:

Press Enter to send.

14.35 Shift + Enter in Design Chat

Because Design Chat submits only when Enter is pressed without Shift, Shift + Enter can be used to create a new line inside a longer edit request.

This differs from the initial Website Builder screen, where Shift + Enter starts the project.

Keep the two contexts separate:

Initial Builder

Shift + Enter → Start Project

Design Chat

Enter → Send

Shift + Enter → New line

14.36 AI Editing Cost

Every current SendMessage AI modification workflow deducts:

10 Tokens

before processing the requested edit.

If deduction fails, the pending user message is removed and the edit does not proceed.

14.37 Use Targeted Edits Instead of Rebuilding

Because current follow-up AI editing costs considerably less than the verified 500-Token initial generation, an efficient workflow is:

Generate strong initial site

Keep existing project

Request focused improvements

rather than repeatedly creating complete new sites for small changes.

14.38 Design Chat Retains Project Context

When a follow-up edit is sent, Website Builder includes the current design and the previous Design Chat messages in the AI editing workflow.

This allows follow-up requests such as:

Keep everything else the same and make the hero shorter.

without requiring you to reproduce all prior website requirements manually.

14.39 Reference Images During Editing

Design Chat also includes a Paperclip control for images.

Its file selector accepts:

image/*.

You can attach a reference image to a modification request.

For example:

Restyle the hero to feel closer to this reference image, but keep our existing copy.

14.40 Pasting Images During Editing

Like the initial Builder, Design Chat detects pasted clipboard images and displays them as the selected reference image.

14.41 Removing an Editing Reference Image

A selected Design Chat image displays an X button.

Use it to remove the image before sending the modification.

14.42 Previewing the Website

The generated website is displayed inside the Website Preview area.

The current workspace renders the generated design in an isolated preview frame.

As you edit the design, the Preview updates to reflect the current generated website code.

14.43 Desktop Preview

The Website toolbar contains a Monitor icon for the desktop/web view.

Select it to preview the design at full available width.

14.44 Mobile Preview

Beside the desktop control is a mobile-device icon.

Selecting it changes the Preview to approximately:

375 px wide.

Use this to inspect how the site looks on a narrower mobile viewport.

14.45 Always Check Both Views

Before saving a final design:

  1. Preview desktop.
  2. Preview mobile.
  3. Check:
  4. Navigation
  5. Headline wrapping
  6. Buttons
  7. Cards
  8. Forms
  9. Spacing
  10. Images
  11. Section order
  12. Correct any issues through Design Chat or Visual edits.

Responsive review is especially important for generated website designs.

14.46 View in a New Tab

The Website toolbar includes:

View

when the toolbar has enough space.

Selecting it creates a full HTML preview and opens it in a new browser tab.

This is useful for reviewing the site outside the editor layout.

14.47 View Is a Preview, Not Publishing

The View command creates a browser preview from the current generated HTML.

It does not mean the website is publicly published.

Publishing is a separate action covered in Chapter 15.

14.48 Viewing Generated Code

The Website toolbar contains:

Code.

Selecting it opens the generated source in a code viewer.

The current code viewer identifies the file as:

index.html.

14.49 Copying Website Source Code

Inside the Code viewer is:

Copy.

Selecting it copies the current generated source and displays:

Source code copied!

This can be useful if you need to transfer the generated HTML into another authorized development workflow.

14.50 Downloading the Website

The Website toolbar provides:

Download.

The current download creates:

index.html.

This differs from the Standard Generator's .txt downloads.

14.51 Download Confirmation

After the HTML download is created, Website Builder displays:

Download successful!

14.52 Compact Toolbar

When the Website Preview area becomes narrow—or when the Visual edits panel requires additional space—the commands:

  1. View
  2. Code
  3. Download

move into a three-dot menu rather than remaining as individual toolbar buttons.

The functions remain available.

14.53 Visual Edits

Design Chat contains a control labeled:

Visual edits.

Visual edits allows you to select a specific element inside the website Preview and work on that element instead of asking the AI to rewrite the entire design.

14.54 Turning On Visual Edits

Select:

Visual edits

The control changes its active appearance.

When Visual edits is active, moving across page elements in the Preview highlights them.

Click a specific element to select it.

14.55 Selected Element Indicator

When an element is selected, Design Chat displays a breadcrumb-like indicator showing:

Design / [element tag].

For example, the selected element could be identified as a heading, button, section, image, or another HTML element type.

14.56 Closing the Selected Element

Use the X beside the selected-element indicator or Close in the Visual edits panel to clear the current selection.

14.57 Visual Editing Panel

When a normal non-image element is selected, Website Builder opens:

Visual edits.

The current panel includes controls grouped around:

  1. Typography
  2. Colors
  3. Spacing
  4. Border
  5. AI modification of the selected element

14.58 Typography Controls

The current Visual edits panel provides:

Font size

Choices currently include sizes from 12px through 48px.

Font style

  1. Normal
  2. Italic
  3. Oblique

Font weight

  1. Light (300)
  2. Regular (400)
  3. Medium (500)
  4. Semi-Bold (600)
  5. Bold (700)

Alignment

  1. Left
  2. Center
  3. Right
  4. Justify


14.59 Color Controls

Visual edits includes:

  1. Text color
  2. Background color


Use these to make direct visual changes to the selected element.

14.60 Spacing Controls

The Visual edits panel includes separate controls for:

Margin

  1. Top
  2. Right
  3. Bottom
  4. Left

Padding

  1. Top
  2. Right
  3. Bottom
  4. Left


This allows precise local spacing adjustments.

14.61 Border Controls

The current panel also provides:

  1. Border width
  2. Border color
  3. Border style
  4. Border radius

Border styles include:

  1. None
  2. Solid
  3. Dashed
  4. Dotted


14.62 Direct Visual Changes Update the Working Design

Changes made through controls such as font size, text color, spacing, and borders are applied directly to the selected Preview element and copied back into the current working website design.

These direct style adjustments do not use the Design Chat AI request handler.

Therefore, the source does not establish the same 10-Token AI edit deduction for simply changing these local style controls.

14.63 Important: Direct Visual Changes Still Need Saving

Even when a local visual change immediately appears in the Preview, it is still part of the current working design state.

Use Save to persist the project before leaving.

Do not assume every Preview change is automatically committed to the saved project.

14.64 Asking AI to Modify a Selected Element

At the bottom of Visual edits is a targeted AI field:

“Ask AI to modify selected...”

This lets you apply a natural-language AI edit specifically to the selected element.

14.65 Example — Targeted AI Element Edit

Suppose you select a button.

Enter:

Make this button larger, use a stronger blue background, make the corners more rounded and change the text to Schedule a Demo.

Because a specific element is selected, Website Builder asks the AI to modify that element rather than blindly redesigning unrelated page sections.

14.66 Targeted AI Edits Use the AI Editing Workflow

A targeted AI request from Visual edits is passed through the same Website Builder Design Chat editing function.

Therefore, the current verified 10-Token AI editing deduction applies to that AI request path.

14.67 Targeted Element Editing Protects the Rest of the Site

When an element is selected, the current AI editing instructions specifically ask the Model to return the updated selected element rather than the entire unrelated page.

Website Builder then replaces the selected element in the current design.

This is useful for reducing unintended changes elsewhere.

14.68 Selecting an Image Opens Image Settings

If the selected page element is an image, Website Builder opens:

Image Settings

instead of the standard Visual edits controls.

14.69 Image Settings

The current Image Settings panel includes user-facing controls for:

  1. Image Preview
  2. Upload Image
  3. Prompt
  4. Generate AI Image
  5. AI Transform
  6. Border Radius


14.70 Replacing a Website Image

To replace an existing selected image:

  1. Turn on Visual edits.
  2. Select the image.
  3. Image Settings opens.
  4. Select the image preview or choose the file.
  5. Select:
  6. Upload Image
  7. Review the updated Preview.
  8. Save the project.

The image selector accepts image files.

14.71 Generate AI Image

Image Settings contains:

Generate AI Image

using the value entered in the Prompt field.

This image-generation behavior is tied to the image service used by the Website Builder environment.

Its availability can therefore depend on the current image-service configuration.

14.72 AI Transform Options

The current Image Settings source defines the following transform options:

  1. Smart Crop
  2. Resize
  3. Upscale
  4. BG Remove


Their actual availability depends on the current image-processing environment.

14.73 Saving the Website

Once you are satisfied with the working design, select:

Save.

While saving, the button changes to:

Saving

with a loading indicator.

14.74 Successful Save

When the project saves successfully, Website Builder displays:

Website Saved Successfully!

If it is the first save of a new project, Website Builder also attaches the newly created Project ID to the current workspace URL.

14.75 What Saving Persists

The current save workflow includes:

  1. Website HTML
  2. Design Chat messages
  3. Project identifier when updating
  4. Project Name


This is why a saved Website Project can later reopen with both the design and its prior Design Chat messages.

14.76 How New Website Projects Are Named

The current save workflow does not provide a separate user-facing Project Name field.

Instead, the Project Name is automatically derived from:

the initial userprompt

or, when no such initial Prompt exists:

“New Website”.

14.77 Important Naming Limitation

The current source does not establish a user-facing:

  1. Rename Project
  2. Edit Project Name
  3. Project Title field

for Website Builder.

Therefore, this manual will not instruct users to rename website projects through a control that is not currently present.

14.78 Why Your Initial Prompt Also Matters for Project Naming

When you start through the main Website Builder creation Prompt, that initial request can become the saved project's Name.

For example, an initial Prompt like:

Create an enterprise software landing page for insurance agencies

may be used as the project's displayed Name.

For that reason, consider keeping the opening request descriptive but reasonably concise.

14.79 Default New Website Name

If the project was created without an initial userprompt, the current save logic uses:

New Website.

Because no current Rename control is established, this is another reason the main Website Builder creation path is useful when you want a descriptive project listing.

14.80 Saving Is Separate from Generating

Website generation updates the working design.

It does not automatically mean the project has been persisted through the Website Builder Save operation.

Recommended:

Generate → Edit → Review → Save

Do not leave an important project unsaved.

14.81 Save After Meaningful Milestones

Good times to select Save include:

  1. After the initial design looks correct
  2. After a major new section
  3. After significant copy changes
  4. After extensive visual edits
  5. After replacing images
  6. Before experimenting with a major redesign
  7. Before leaving Website Builder

14.82 Reopening a Saved Website

Saved websites appear under:

Your Projects.

Each current project card displays:

  1. Website preview thumbnail
  2. Project Name
  3. Last updated
  4. Edit
  5. Delete control


14.83 Selecting Edit

On a saved Website Project card, select:

Edit.

Website Builder reopens the project in the Playground.

The current loading workflow restores:

  1. Saved design
  2. Saved Design Chat messages
  3. Saved subdomain if applicable


14.84 Project Preview Cards

Website Builder generates a miniature visual Preview inside each project card using the saved website design.

This helps identify projects visually before opening them.

14.85 Last Updated

Each project card displays:

Last updated: [date].

Use this as a quick reference when choosing among saved projects.

14.86 No Projects Yet

If no saved Website Projects exist, the Projects area displays:

“No projects yet. Create your first AI website!”

Use the Website Builder creation area to begin.

14.87 Deleting Projects

Website Builder includes a Delete control on each saved project.

Selecting it opens:

Delete Project

with:

“Are you sure you want to delete this project? This action cannot be undone.”

Project deletion will be covered again as part of project management in Chapter 15.

14.88 Website Builder and the Selected Model

Website Builder uses the currently selected PROS SUITE AI Model when sending website-generation and editing requests.

Therefore, Model selection from Chapters 10 and 11 can affect Website Builder.

14.89 Current Model Recommendation Banner

Under certain environments, the Website Playground can display a note recommending:

Gemini 3.6 Flash

or:

GPT 5.4 mini

for best results.

The banner is conditional and should not be assumed to appear for every subscriber.

Use the Models actually available in your current Model Selector.

14.90 Do Not Treat a Conditional Banner as a Permanent Model Requirement

Website Builder sends the current selected Model into its AI workflow.

Therefore:

  1. A recommendation is not necessarily the only supported Model.
  2. Available Models can change.
  3. Provider API-Key requirements can still apply.
  4. Use the current Model Selector as the operational reference.

14.91 Website Builder Generates HTML-Based Sites

The Website Builder's generated design is converted into complete HTML for:

  1. Saving
  2. Previewing
  3. Viewing code
  4. Downloading

The user-facing Code view identifies the website as index.html, and Download produces that HTML file.

14.92 No Coding Is Required for Normal Use

Although users can view and download the generated HTML, ordinary Website Builder operation can be performed through:

  1. Natural-language prompts
  2. Visual edits
  3. Image controls
  4. Preview controls
  5. Save

You do not need to manually write HTML to create a site.

14.93 Source Code Is Available When Needed

More technical users can open:

Code

and review the generated HTML with line numbers.

The Code viewer is a viewing/copying interface; the current source does not establish direct manual code editing within that viewer.

14.94 Do Not Confuse Code View with a Code Editor

The current Code window provides:

  1. Syntax-highlighted source
  2. Line numbers
  3. Copy

It does not establish an editable source-code editor in that dialog.

For normal changes, use:

  1. Design Chat
  2. Visual edits

14.95 Website Builder Does Not Automatically Publish Every Saved Site

A saved website remains a saved Website Project.

Publishing is a separate action.

Therefore:

Save ≠ Publish

View ≠ Publish

Download ≠ Publish

The public hosting process begins only when you use the separate Publish workflow.

Chapter 15 covers this in detail.

14.96 Troubleshooting — Generate Button Is Disabled

On the initial Website Builder screen, the Generate control remains disabled when:

  1. No Prompt text exists
  2. No reference image is attached


Enter a website description or attach an image.

14.97 Troubleshooting — Initial Website Does Not Generate

Possible causes include:

  1. Insufficient Tokens
  2. Selected Model issue
  3. Provider/API-Key issue
  4. Network failure
  5. AI generation error

The initial workflow requires the verified 500-Token deduction before generation continues.

14.98 Troubleshooting — Insufficient Tokens

If the initial deduction fails:

  1. Check Monthly Tokens.
  2. Remember that current initial generation uses 500 Tokens.
  3. Review your Plan if additional usage is required.
  4. Retry only after sufficient balance exists.

For later AI Design Chat edits, the current workflow uses 10 Tokens.

14.99 Troubleshooting — AI Did Not Generate Code

If the full initial response does not contain usable website code, Website Builder displays:

“AI did not generate any code.”

Possible actions:

  1. Review your Prompt.
  2. Confirm the selected Model.
  3. Make the website request explicit.
  4. Retry if appropriate.

14.100 Troubleshooting — Modification Did Not Produce Valid Code

For an AI edit, Website Builder can display:

“AI did not generate any valid code for this modification.”

Try a clearer instruction.

For example, instead of:

Fix this.

use:

Change the hero headline to two lines, reduce its font size on mobile and keep all other sections unchanged.

14.101 Troubleshooting — AI Edit Failed

If the editing request itself fails, Website Builder can display the returned error or:

“Failed to send message”.

Check:

  1. Model availability
  2. Token Balance
  3. Provider access
  4. Connection

before retrying.

14.102 Troubleshooting — Save Fails

If Save cannot complete, Website Builder can report:

Failed to save website

or:

Error saving website: [message].

Do not leave the workspace assuming the design has been persisted.

Retry Save after resolving the issue.

14.103 Troubleshooting — Direct Visual Edit Appears but Is Gone Later

A direct Visual edit changes the current working design.

If you leave without successfully selecting Save, that change should not be assumed to exist in the saved Website Project.

After important visual adjustments:

Review → Save → Confirm Website Saved Successfully!

14.104 Troubleshooting — Project Is Named New Website

The current save workflow uses:

New Website

when no initial user Prompt is available for naming.

The source does not establish a Rename control.

For future projects, starting with a descriptive initial brief can create a more identifiable project Name.

14.105 Troubleshooting — Cannot Find Rename Project

There is no source-verified current Website Builder:

Rename Project

function.

Do not look for a hidden Rename workflow.

14.106 Troubleshooting — View Opens but Site Is Not Public

This is expected.

View creates a local browser preview.

Use Publish when you intend to make the project available through its public Website Builder URL.

Publishing is covered in Chapter 15.

14.107 Troubleshooting — Toolbar Buttons Disappear

If:

  1. View
  2. Code
  3. Download

are not individually visible, look for the three-dot menu.

The Website toolbar enters compact mode when the available width becomes small.

14.108 Troubleshooting — Visual Edits Panel Makes the Workspace Narrower

When a selected element opens the Visual edits panel, the main PROS SUITE Sidebar can automatically collapse to preserve working space.

This is expected workspace behavior.

14.109 Troubleshooting — Opening Main Sidebar Closes Visual Editing Context

The current Website Builder listens for the main Sidebar being manually expanded.

When that happens, it can clear the current selected-element Visual edits panel to prevent the layout from becoming too constrained.

If your selected element disappears, reactivate Visual edits and select it again.

14.110 Best Practice — Start with the Entire Site Architecture

Before the initial 500-Token generation, outline the website.

Example:

Page Goal

Generate enterprise demos.

Sections

  1. Navigation
  2. Hero
  3. Platform overview
  4. Business outcomes
  5. Systems/features
  6. Industries
  7. Testimonials
  8. CTA
  9. Footer

Then turn that architecture into the initial Website Builder Prompt.

14.111 Best Practice — Include Brand Information Up Front

Include important brand requirements before first generation:

  1. Brand Name
  2. Colors
  3. Audience
  4. Tone
  5. Visual character
  6. Primary CTA

This reduces later redesign work.

14.112 Best Practice — Use Reference Images as Direction, Not as the Only Instruction

A screenshot is useful for:

  1. Layout inspiration
  2. Mood
  3. Spacing
  4. Visual hierarchy
  5. Component style

But also tell AIUNIFY:

  1. What should remain unique
  2. What content belongs to your company
  3. What sections you actually need

14.113 Best Practice — Refine Instead of Restarting

Once the overall site is strong:

Do not rebuild everything to change one button.

Use:

  1. Design Chat
  2. Visual edits
  3. Targeted element AI editing

This protects existing work and can use Tokens more efficiently.

14.114 Best Practice — Use Visual Edits for Precise Styling

Use direct Visual edits for changes such as:

  1. Font size
  2. Font weight
  3. Alignment
  4. Color
  5. Margin
  6. Padding
  7. Border
  8. Border radius

Use AI editing for broader design/content changes.

14.115 Best Practice — Use Targeted AI Editing for Complex Element Changes

A selected-element AI Prompt is appropriate for:

  1. Rewriting a complete hero block
  2. Reworking a card
  3. Adding components inside a selected section
  4. Changing button composition
  5. Restructuring an individual element

This is more controlled than asking for a general page-wide redesign.

14.116 Best Practice — Check Mobile After Every Major Design Change

A desktop design can look good while creating issues on mobile.

After major changes:

Desktop Preview

Mobile Preview

Correct layout if necessary.

14.117 Best Practice — Save Before Major Experiments

Before a large change such as:

Completely redesign the homepage in a different style

select:

Save

first.

This preserves the currently saved version before you make more extensive changes to the working design.

14.118 Best Practice — Download Important Website Versions

In addition to saving inside PROS SUITE, use:

Download → index.html

when you need an external copy of an important generated site version.

This can be useful for controlled backup or development handoff.

14.119 Best Practice — Keep Project Naming in Mind

Because current Website Builder naming is automatic:

Initial Prompt → Project Name

or:

No initial Prompt → New Website

keep the opening brief descriptive enough to identify the project later.

14.120 Recommended Website Builder Workflow

A strong complete creation workflow is:

WEBSITE BUILDER

Define Site Goal

Write Detailed Initial Brief

Optional:

Attach Reference Image

Generate

500-Token Initial Creation

Review Generated Preview

Desktop / Mobile Check

Design Chat

10-Token AI Refinements When Needed

and/or:

Visual Edits

Review

Save

Website Saved Successfully!

Continue Editing or Move to Publishing

14.121 Website Builder User Checklist

Before initial generation:

  1. I know the site's primary goal.
  2. I know the audience.
  3. I identified the main sections.
  4. I provided brand/style direction.
  5. I included the important call-to-action.
  6. I attached a reference image if helpful.
  7. I reviewed my Monthly Token Balance.
  8. I understand the current full initial workflow uses 500 Tokens.
  9. I selected an appropriate AI Model.

After initial generation:

  1. I reviewed the full design.
  2. I checked desktop Preview.
  3. I checked mobile Preview.
  4. I identified specific changes rather than restarting unnecessarily.
  5. I understand current AI Design Chat edits use 10 Tokens.
  6. I know how to attach an image to an edit.
  7. I know how to use Visual edits.
  8. I know how to select an individual page element.
  9. I know how to change typography.
  10. I know how to change colors.
  11. I know how to adjust margin and padding.
  12. I know how to modify borders.
  13. I know how to ask AI to modify the selected element.
  14. I know image elements open Image Settings.
  15. I know how to View the website in another tab.
  16. I know how to open Code.
  17. I know how to Download index.html.
  18. I know how to Save the project.
  19. I wait for Website Saved Successfully!
  20. I understand Project Name is currently derived automatically.
  21. I understand Save does not equal Publish.

14.122 What Website Builder Currently Supports

The source verifies the following subscriber-facing capabilities:

Creation

  1. Natural-language website brief
  2. Image reference attachment
  3. Clipboard image paste
  4. Suggested starting prompts
  5. AI-generated website design

Editing

  1. Design Chat
  2. Image references during modifications
  3. Conversation context
  4. Targeted AI modifications
  5. Visual element selection
  6. Typography controls
  7. Color controls
  8. Spacing controls
  9. Border controls
  10. Image Settings

Preview

  1. Desktop view
  2. Mobile view
  3. New-tab View

Code

  1. View generated HTML
  2. Copy generated source
  3. Download index.html

Persistence

  1. Save Website Project
  2. Restore saved code
  3. Restore saved Design Chat messages
  4. Reopen Project using Edit

Deployment

  1. Publish capability exists and will be covered in Chapter 15.

14.123 What the Current Website Builder Does Not Establish

The source does not establish a subscriber-facing universal function for:

  1. Manually renaming Website Projects
  2. Duplicating a Website Project
  3. Project folders
  4. Project tagging
  5. Multi-user collaborative editing
  6. Comments between collaborators
  7. Automatic version history
  8. Undoing to arbitrary previously saved revisions
  9. Editing HTML directly inside the Code viewer
  10. WordPress export
  11. Direct ZIP export
  12. Automatic source-control repository creation

Do not expect these functions unless they are added to a future user-facing version.

14.124 Website Builder at a Glance

The current Builder can be summarized as:

DESCRIBE

Ask AIUNIFY to build a website that can...

Optional:

ATTACH IMAGE

GENERATE WEBSITE

Current verified full-generation workflow:

500 Tokens

DESIGN CHAT + PREVIEW

Choose:

AI EDIT

Current verified editing workflow:

10 Tokens

or:

VISUAL EDITS

Direct local styling

DESKTOP / MOBILE PREVIEW

VIEW / CODE / DOWNLOAD

SAVE

WEBSITE PROJECT

Next:

PUBLISH / DOMAIN MANAGEMENT

14.125 Chapter Summary

Website Builder is AIUNIFY PROS SUITE's AI-assisted website design and project workspace.

The main creation interface invites users to:

“Ask AIUNIFY to build a website that can...”

and supports both natural-language instructions and image references.

The current full initial generation workflow requests 500 Tokens before creating a new website.

Once a site exists, the Design Chat lets users request additional modifications through:

“Ask for modifications or share a vibe...”

and current follow-up AI editing requests use 10 Tokens.

Website Builder also provides Visual edits, allowing users to select individual page elements and adjust Typography, Colors, Spacing, and Borders directly. A selected element can also receive a targeted AI instruction through:

“Ask AI to modify selected...”

The generated website can be previewed in desktop or mobile form, opened through View, inspected through Code, copied, or downloaded as index.html.

Selecting Save persists the current website design and Design Chat messages. A successful operation displays:

Website Saved Successfully!

The current project Name is generated from the initial Website Builder Prompt or defaults to:

New Website

when no initial Prompt exists. No user-facing Rename function is established in the current source.

The most effective operating method is:

Plan the Site → Generate Once → Review → Refine Through Design Chat → Use Visual Edits for Precision → Check Desktop and Mobile → Save → Preserve Important Versions → Publish Only When Ready

Write Your Comment