After creating a website in Website Builder, AIUNIFY PROS SUITE provides a project-management and publishing workflow for working with the website beyond its initial generation.
This chapter covers the subscriber-facing functions for:
index.htmlThis chapter remains system-user/subscriber only. Administrator Domain Management functions are intentionally excluded.
A Website Builder project can move through several user-controlled stages:
Create
↓
Generate
↓
Edit
↓
Preview
↓
Save
↓
Optional:
Download
↓
Optional:
Publish
↓
Public Website
↓
Optional:
Continue Editing
or:
Delete from public
↓
Optional:
Delete Project
These operations are separate and should not be confused with one another.
Navigate to:
Sidebar → Core Tools → Website Builder
The main Website Builder page includes:
Your Projects
and:
+ New Project.
The Your Projects area is the primary subscriber-facing location for previously saved Website Builder projects.
The page retrieves the Website Projects available through the current Website Builder project service and renders them as project cards.
Each Website Project card currently contains:
This gives you both a visual and text-based way to identify saved projects.
At the top of each card, Website Builder renders a miniature version of the saved website.
This preview is intended for identification rather than interactive use.
Links and forms inside the thumbnail are not intended to function as the live site.
Below the preview, the saved Project Name appears in bold.
As established in Chapter 14, the current Website Builder automatically uses:
the initial Website Builder Prompt
or:
New Website
as the Project Name when saving.
The supplied user-facing source does not establish a:
control.
Therefore, project naming remains automatic in the current version.
Each project card displays:
Last updated: [date].
This helps you distinguish older and more recently modified projects.
If no saved Website Projects are available, Website Builder displays:
“No projects yet. Create your first AI website!”
Use the creation workflow from Chapter 14 to begin.
Select:
+ New Project
to open a new Website Builder Playground.
Remember that the main Website Builder creation Prompt described in Chapter 14 is generally the clearest path for creating a completely new AI-generated site with a descriptive project Name.
To continue working on an existing site:
The project reopens inside the Website Playground.
When an existing Project ID is opened, Website Builder retrieves the saved project.
The current loader restores:
This means a saved Website Project is more than a screenshot—it can restore the working design and prior design conversation.
After selecting Edit, you can continue using the same tools described in Chapter 14:
The Website Playground toolbar contains:
Save.
Use Save to persist the current website project.
The Save control is disabled when:
While the project is being saved, the button displays:
Saving.
Avoid leaving the page until the save operation completes.
A successful operation displays:
Website Saved Successfully!
Use that confirmation before assuming new work has been persisted.
The current Save workflow submits:
If the current website has not yet received a Project ID, a successful first Save can create one and update the working URL with that Project ID.
This allows subsequent saves to update the same Website Project rather than creating a separate project each time.
This distinction is essential:
Save stores your Website Project. Publish makes the website publicly accessible through its publishing URL.
A website can be:
Saved but not Published.
Likewise:
Delete from public
and:
Delete Project
perform fundamentally different operations.
This chapter explains both separately.
Recommended Save points include:
The Website Playground displays the generated website inside its visual Preview workspace.
The toolbar below the Preview provides controls for:
Select the Monitor icon to use the:
Web/Desktop
Preview.
The design uses the available Preview width in this mode.
Select the mobile-device icon to switch to:
Mobile
Preview.
The mobile Preview is rendered at approximately 375 pixels wide in the current Website Design component.
A website that looks correct on desktop may still have:
on a mobile screen.
Always review both views before publishing.
Before publishing, inspect:
Navigation
Can users understand and access it?
Hero
Does the headline wrap properly?
Buttons
Are calls-to-action visible and usable?
Images
Do they scale appropriately?
Cards
Do they stack cleanly?
Forms
Are fields readable?
Footer
Does it remain organized?
The Website toolbar includes:
View.
This opens the current generated website in a separate browser tab for a larger Preview.
Website Builder constructs the current website into a complete HTML document and opens it through a temporary browser object URL.
For users, the important distinction is:
View is a temporary Preview—not a public deployment.
You can use View before the site is public.
This allows you to inspect the website in a cleaner browser environment before deciding whether to publish it.
The browser tab opened by View should not be treated as the address you send to customers.
Use:
Publish
to create the Website Builder's public publishing address.
The Website toolbar includes:
Code.
Selecting it opens a source-code viewer for the current generated website.
The source viewer identifies the website file as:
index.html
and provides syntax-highlighted HTML with line numbers.
The Code viewer includes:
Copy
and confirms successful copying with:
Source code copied!
The current source viewer provides:
It does not establish direct manual source-code editing inside that dialog.
Use Design Chat or Visual edits for normal Website Builder modifications.
The Website toolbar includes:
Download.
This creates an HTML copy of the current generated website.
The current downloaded file is:
index.html.
After the file is generated, Website Builder displays:
Download successful!
Downloading the HTML gives you a local copy of the website.
It does not:
When the available Preview space is narrow—or Visual edits is consuming additional workspace—the following controls can move into the three-dot menu:
If those controls seem to disappear, check the menu.
Even when the toolbar becomes compact, the current design keeps the major project/public controls separate from View/Code/Download:
Once the website is ready for public access:
The Publish button appears when the current project does not have a published subdomain.
Publish is disabled when:
Selecting Publish opens:
Publish Website
with:
“Enter a subdomain to host your website.”
The current field uses the placeholder:
my-awesome-site.
Enter the public identifier you want Website Builder to use.
A subdomain is the website-specific portion of the public address provided by the Website Builder hosting configuration.
Conceptually:
your-site + platform-domain
can produce:
your-site.platform-domain
Depending on the deployment environment, the system can alternatively publish through a /sites/your-site style path.
The current source supports two URL patterns:
https://[subdomain].[base-domain]
[current-host]/sites/[subdomain]
Therefore, this manual does not hard-code one universal public domain.
Use the public URL displayed by your live PROS SUITE environment.
Inside the current Publish Website dialog, Website Builder automatically:
a–z0–9-Examples that fit the current input rules include:
company-site
enterprise-demo
summer-campaign
sales-platform
my-business
A good public subdomain should generally be:
Avoid extremely long descriptions when a concise identifier will work.
If you attempt to publish without entering a value, Website Builder displays:
Please enter a subdomain.
The Publish button is also disabled while the field is empty.
After entering the subdomain, select:
Publish.
During the operation, the button can display:
Publishing....
The current publishing operation submits:
This means Publish is not merely attaching a URL to an unsaved visual snapshot—it also persists the website information involved in the publication operation.
If the website does not yet have a Project ID, a successful Publish operation can create the project and add its new Project ID to the Website Builder URL.
Therefore:
A separate Save is recommended before publishing, but the current Publish workflow itself can also create/persist a new project as part of publishing.
A successful operation displays:
Website Published to Subdomain!
Website Builder then records the project's current subdomain in the working interface.
After a successful Publish and valid Project ID, Website Builder constructs the public URL and opens it in a new browser tab.
This lets you immediately inspect the public version.
After publication, review the public site carefully.
Check:
Do not assume that a successful publication message means every part of the content itself is correct.
When Website Builder knows that the Project has a subdomain, the toolbar displays a green public-site indicator with a Globe icon and the public URL.
The displayed public URL is clickable and opens the published website in another tab.
Use this whenever you need to inspect the live/public version while editing.
When no subdomain exists, the toolbar shows:
Publish
When a subdomain exists, the Publish button is replaced by:
Delete from public.
This is how the current Website Builder indicates whether the project is considered published through its subdomain workflow.
A published site can still be edited in Website Builder.
You may:
However, because the sanitized source bundle does not include the backend public-site delivery implementation, this manual does not make an unsupported guarantee about exactly when every saved change becomes visible publicly.
After editing a published project:
Save the project and verify the public URL yourself.
When a saved project is reopened, the loader restores the saved subdomain into Website Builder.
If the subdomain is restored successfully, the toolbar can again display the public URL and Delete from public.
To remove the current Website Builder publication, select:
Delete from public.
This is the current user-facing unpublish control.
This distinction is extremely important.
Delete from public
clears the project's public subdomain association.
It does not invoke the Website Project deletion function.
The current unpublish operation sends the existing Project ID with:
clearSubdomain: true.
While removing the project from public access, the toolbar temporarily displays:
Deleting.
This wording refers to deleting the public publication association—not deleting the Website Project itself.
When the public removal succeeds, Website Builder displays:
Website unpublished!
The working projectSubdomain is then cleared.
Once the public subdomain is cleared:
This allows you to publish again later if needed.
After Website unpublished!, the project itself can remain available under:
Your Projects
because the unpublish workflow clears only the subdomain rather than invoking project deletion.
Use Delete from public when:
Do not use it merely because you want to:
Those actions do not require removing the public publication.
Think of publication status as:
Saved Project + No Subdomain
→ Publish
→
Saved Project + Public Subdomain
→ Delete from public
→
Saved Project + No Subdomain
The Website Project remains separate from that cycle.
Project deletion is performed from:
Website Builder → Your Projects
not through Delete from public.
Each saved project card contains a Trash/Delete control.
Selecting the Delete control opens:
Delete Project
with:
“Are you sure you want to delete this project? This action cannot be undone.”
and:
Delete.
The confirmation explicitly states:
“This action cannot be undone.”
Do not confirm deletion unless you intend to permanently remove the saved Website Project.
Before deleting a project, consider:
index.html if needed.After successful deletion, Website Builder displays:
Project deleted
and refreshes the Project list.
If deletion fails, Website Builder can display:
Failed to delete project
or:
Error deleting project.
If that happens, do not assume the project was removed.
The distinction can be summarized as:
Removes publication/subdomain
Project remains saved.
Removes the saved Website Project
Confirmation warns that the action cannot be undone.
This distinction should be understood before using either control.
Another important distinction:
Used by the owner while editing.
Includes:
Creates a public Website Builder address.
Use Preview for review.
Use Publish only when the website is ready for public access.
Creates:
index.html
on your device.
Places the Website Project at its configured public Website Builder URL.
Downloading does not automatically deploy that downloaded file anywhere.
Lets you inspect and Copy the generated source.
Creates the current website as:
index.html
Both use the generated website source but serve different purposes.
Persists the project inside Website Builder.
Creates an external HTML copy.
For important projects, you may choose to do both.
Persists the editable Project.
Persists the publishing state and assigns the public subdomain.
A good production workflow usually uses:
Save → Review → Publish
A published Website Project remains editable.
Recommended workflow:
Open Project
↓
Edit
↓
Desktop Preview
↓
Mobile Preview
↓
Save
↓
Open Public URL
↓
Verify Changes
Because public delivery is handled outside the included user-interface source, verification is important.
Before substantially redesigning a published site:
index.html if an external backup is useful.After publishing, use the public URL shown in the toolbar.
Do not rely solely on the embedded Website Preview.
This helps verify the website in the environment visitors will actually access.
Before sharing the public URL, review:
AI-generated designs should be tested before business use.
Website Builder provides desktop and mobile Preview controls, but it can also be useful to inspect the public website using actual devices or browser responsive tools.
The built-in controls provide the initial verification step.
Choose a public subdomain that communicates the project clearly.
For example:
Company Website
company
Product Demo
product-demo
Campaign
summer-campaign
Customer Portal Mockup
client-portal
Avoid meaningless identifiers if customers will see the URL.
The current client source validates the format of the entered subdomain, but the sanitized bundle does not establish client-side availability checking before Publish.
If a requested value cannot be accepted, the publishing service can return an error.
Do not assume a syntactically valid subdomain is necessarily available.
If publication fails, Website Builder can display the returned error or:
Failed to publish website
with the applicable status.
The catch path can also display:
Error publishing website: [message].
Check whether:
The current Publish control is disabled under those conditions.
Confirm that a subdomain value has been entered.
If empty, Website Builder displays:
Please enter a subdomain.
This is expected.
The Publish dialog automatically converts the value to lowercase.
The current publishing field strips characters outside:
Use a hyphen instead of spaces.
A public URL indicator is only rendered when Website Builder has a projectSubdomain for the current Project.
Confirm that:
Compare:
Then:
The wording can be confusing.
The source verifies that Delete from public invokes the unpublish workflow, which clears the subdomain association.
The permanent project deletion function is separate and appears under Your Projects with a confirmation dialog.
That is expected.
Delete from public is not Project deletion.
The site should remain a saved Website Project unless you separately select Delete Project.
The current confirmation explicitly states that deletion:
cannot be undone.
The supplied subscriber source does not establish:
This is why downloading important versions before destructive deletion can be valuable.
Check the toolbar's:
three-dot menu
The controls are moved there when the toolbar enters compact mode.
If a website is already published, the toolbar replaces:
Publish
with:
Delete from public.
Look for the displayed public URL.
A saved project's loader restores its subdomain when that value exists.
If it does not appear:
The current Save process can display:
Failed to save website
or:
Error saving website: [message].
Do not close the page until you know whether your latest changes were successfully persisted.
The Project list formats the project's returned updatedAt date using the browser's local date formatting.
Use it as a project-recency indicator rather than as a detailed activity log.
The current subscriber-facing source does not establish a project version-history interface.
There is no verified:
function.
Save carefully and Download important milestones when needed.
The current project-card source establishes:
but not:
Duplicate.
If you need to preserve a version before experimentation, use Save and Download as appropriate.
There is no source-verified user control for organizing Website Projects into:
The current Your Projects view presents project cards directly.
The source bundle does contain a separate component titled:
Domain Management
with tabs for:
and code for adding and verifying custom domains.
However, this component must not be treated as an active subscriber capability merely because its source file exists.
A complete source search found the DomainManager component definition but no separate import/render invocation connecting it to the ordinary Website Builder user interface.
Therefore, the current User Operations Manual does not instruct subscribers to look for or open a Custom Domain panel that is not source-verified as reachable.
The unused component contains interface code for:
But source presence alone does not prove that an ordinary subscriber can access these controls.
Accordingly:
These are not documented as current subscriber operations.
This follows the same source-verification standard used throughout this User Operations Manual.
The bundle also contains a separate:
src/views/admin/AdminDomains.tsx
whose interface says:
“Manage all domains and websites created in the playground.”
That is explicitly an Admin view and is not part of this subscriber manual.
The Website Builder subscriber workflow that is directly rendered and source-verified is:
Publish
↓
Publish Website
↓
Enter a subdomain to host your website
↓
Publish
↓
Website Published to Subdomain!
↓
Public URL
This is the publishing workflow users should rely on in the current version.
If a future subscriber release visibly adds a Custom Domain interface, the User Operations Manual should be updated from the actual released UI.
At that point, documented user steps can cover whatever the released interface verifies, such as:
Until then, those controls remain outside the verified user workflow.
A simple way to think about the Website Builder is:
PROJECT
Your editable saved website.
PREVIEW
What you inspect before release.
PUBLICATION
Whether Website Builder exposes the project through its public URL.
They are related but not identical.
After Website Builder changes:
Edit
↓
Preview
↓
Save
↓
Wait for:
Website Saved Successfully!
↓
Then leave the workspace.
Recommended sequence:
Save
↓
Desktop Preview
↓
Mobile Preview
↓
View
↓
Correct Any Problems
↓
Save Again
↓
Publish
↓
Verify Public URL
Before major changes to a production/published site:
index.html.This gives you an external copy of an important milestone even though Website Builder does not currently provide a version-history interface.
If your goal is only to remove the website from public access:
Use:
Delete from public
Do not use:
Delete Project
unless you also intend to permanently remove the saved project.
A customer-facing URL should be intentional.
Before publishing, ask:
The subdomain becomes part of the public address.
The user-interface source verifies saving and publication controls, but the backend public-rendering implementation is outside the sanitized source bundle.
Therefore, after modifying a published site:
Save → Open Public URL → Verify
is the safest operating practice.
Before leaving a Website Project:
index.html if I need an external copy.Before publishing:
Before selecting Delete from public:
Afterward:
Before selecting Delete in the Delete Project confirmation:
index.html if I need a copy.The current subscriber controls can be understood as:
EDIT
Reopen the saved Website Project.
SAVE
Persist the current editable project.
DESKTOP / MOBILE
Change Preview size.
VIEW
Open a temporary full-page Preview.
CODE
Inspect/copy generated HTML.
DOWNLOAD
Create index.html.
PUBLISH
Assign a public Website Builder subdomain.
PUBLIC URL
Open the published site.
DELETE FROM PUBLIC
Remove the project's public subdomain/publication.
DELETE PROJECT
Permanently remove the saved Website Project.
A website can conceptually exist in these states:
Generated/edited in the current session.
Stored under Your Projects but without a public URL.
Stored as a Project and associated with a public subdomain.
Saved Project remains, but the public subdomain has been cleared.
Saved Project has been removed through Delete Project.
Understanding these states makes Website Builder much easier to operate.
The source verifies the following user-facing project-management capabilities:
index.html
The source does not establish an ordinary-user function for:
The presence of unused components or administrator views is not treated as proof of subscriber functionality.
The verified current workflow is:
YOUR PROJECTS
↓
EDIT
↓
DESKTOP / MOBILE PREVIEW
↓
SAVE
↓
Optional:
VIEW
CODE
DOWNLOAD
↓
PUBLISH
↓
PUBLISH WEBSITE
↓
Enter:
my-awesome-site
↓
PUBLISH
↓
Website Published to Subdomain!
↓
PUBLIC URL
↓
If you later want it offline:
DELETE FROM PUBLIC
↓
Website unpublished!
↓
Project remains under:
YOUR PROJECTS
If you instead want to permanently remove the project:
YOUR PROJECTS → DELETE PROJECT → DELETE
AIUNIFY PROS SUITE Website Builder provides a persistent Your Projects workspace for managing websites that have been saved.
Each Project card displays a visual Preview, Project Name, Last updated, Edit, and a Delete control.
Selecting Edit opens the Project in the Website Playground, where its saved design, Design Chat messages, and existing subdomain can be restored.
The Website toolbar provides:
and the current Download action creates:
index.html.
A successful Save displays:
Website Saved Successfully!
When a website is ready for public access, select:
Publish
The dialog displays:
Publish Website
and:
“Enter a subdomain to host your website.”
The current subdomain field automatically converts the entry to lowercase and permits letters, numbers, and hyphens.
A successful publication displays:
Website Published to Subdomain!
and can automatically open the published website in another tab.
Once published, Website Builder displays the public URL and replaces Publish with:
Delete from public.
Selecting Delete from public clears the subdomain and displays:
Website unpublished!
It does not delete the Website Project.
Permanent deletion is handled separately under Your Projects through:
Delete Project
with the warning:
“Are you sure you want to delete this project? This action cannot be undone.”
Finally, although the codebase contains a component with Custom Domain/DNS controls, no subscriber-facing source invocation of that component was found. The separate active Domain Management view identified elsewhere in the source belongs under, so it is excluded from this system-user manual.
The verified subscriber workflow is therefore:
Create → Edit → Preview → Save → Publish to Subdomain → Verify Public Site → Continue Editing or Unpublish → Delete Project Only When Permanently Finished