Earlier tutorial: this recording shows a previous interface. Use the written guide below for current instructions.
Earlier tutorials and recordings (1)
These recordings may show an earlier interface or an older cut. Follow the current written instructions below.
Written guide
Overview
Appmint distinguishes a website record from a development environment. Sites are the websites you manage; a development environment provides a separate place to build and preview code through Vibe Studio. We will create and locate each kind of record, inspect its URLs and understand where a custom domain belongs.
First distinguish three records
A site owns the website settings and pages. A page is one editable document within that site. A development environment is the separate code-building/preview route. Switching one does not rename the organization or automatically select a page in another site.
Historical Appmint dashboard: a site exists in plan usage, but Active Site says nothing is loaded. Choose a site before editing its pages or attaching its domain. A site count alone does not select a destination.
1. Find a site and inspect its actions
Why this matters
A site card represents one website, not the entire organization. Check its name before opening settings or attaching a domain.
Follow these steps
- Open Sites (or use the dashboard's Choose a site entry when none is active). Use Search sites with the saved site name.
- In grid or table view, identify the exact record before choosing View Site. Inspect the actual opened address and content; do not infer its URL from the title.
- Return to that record and choose Site Settings. Verify the site name before changing Home Page, branding or features.
- After a change, save, reopen this same site's settings and test its View Site destination. Keep page-saving and choosing the site's home page as separate operations.
Check the result:
The opened website corresponds to the selected record; settings show that same identity.
What an existing page tells you
Historical Build Studio Saved Pages reference: the page cedar-and-form belongs to site leasite. This is a page list, not the Sites manager and not a newly created development environment. Use the SITE column to avoid editing the right page name under the wrong website.
2. Create another website record
Why this matters
Site Name identifies the new site. Title and Description explain it to people. A custom domain is optional and requires its own configuration rather than merely typing a name.
Follow these steps
Open Create New Site. Enter an available Site Name, then Title and Description. Leave Domain (Optional) blank for the initial example. Choose Create Site once. Wait for the request and list refresh. Search for the new site and open View Site. Record the actual destination rather than guessing a URL from the name.
Check the result:
The site is listed after refresh and its destination opens. Default content is not described as a fully designed website.
3. Create and open a development environment
Why this matters
Use a development environment when working with the code-based route. Opening Vibe Studio and previewing the output are separate actions.
Follow these steps
Open Create Dev Environment. Enter Environment Name using lowercase letters, numbers, hyphens or underscores. Observe normalization as you type. Add Title and Description and choose Create Environment. Wait for the record. Open Dev Environment Settings and read Production URL and Preview URL under Access URLs. Use Open Vibe Studio for the editor and Preview Environment for its preview.
Check the result:
The environment record survives refresh. The editor and preview addresses are identifiable; an unavailable service is shown as a dependency failure, not hidden.
4. Attach a domain to the intended destination
Why this matters
The application’s domain association and the domain’s external DNS are different pieces. Production and preview domains are also separate lists; attaching to the wrong one can send visitors to a different build.
Follow these steps
For the intended site or environment choose Attach Domain. Check the read-only target name. Enter Domain Name without https://, paths or a trailing slash. Submit with the dialog’s attachment action and inspect the returned state. Reopen settings and locate the domain in the appropriate list. Complete DNS using the actual domain instructions for that deployment, then test the full HTTPS address in another browser session. Do not invent a universal DNS target for this course.
Check the result:
The correct record contains the domain and a browser request reaches the intended website or build after DNS and TLS are ready.
5. Handle limits, removal and cleanup
Why this matters
A failed create request and a failed request response are not always the same thing. Checking the list before retrying prevents duplicate environments. Removal also differs between sites and development environments.
Follow these steps
If creation reports a quota or service error, refresh and search the exact requested name before retrying. Record the actual error. For a disposable site inspect the Delete confirmation, cancel first, and demonstrate removal only on that disposable record. Inspect domain removal availability: development-environment domain removal is not implemented server-side in the inspected source, so do not promise a working Remove action there.
Check the result:
Retries are based on the real list state and destructive actions are not performed on a live site.
6. Choose the active site and configure its website identity
Why this matters
The active site is the destination for site-scoped work. A site’s home page and default status are separate settings: one selects its first page, while the other marks the organization’s default site.
Follow these steps
Use the site’s active-selection action, then confirm the site name in Studio before opening a page/template workflow. Open Site Settings. In Info choose Home Page from that site’s pages, set Title, Description and Keywords, and inspect Domain, read-only Host Name and Aliases. Configure Favicon and the logo/image fields with intended assets. Change Is Default only when the selected website should become the organization’s default. Save and reopen settings, then visit the site root to check the chosen home page. Do not treat the table’s Edit action as a functioning editor: its inspected handler only displays an Edit site notice. Site Settings opens the real data form. Clone likewise only displays a notice in this component.
Check the result: Site context and saved identity agree; opening the root displays the intended page. Default-site behavior is verified separately from homepage content.
7. Website settings, features and account experience
Why this matters
Site Settings brings together the choices that affect the visitor experience. Feature rows combine a capability, whether it is enabled and, when needed, the page where it belongs.
Follow these steps
In Settings choose Login Redirect and Logout Redirect from this site’s pages. Configure supported Currencies and Languages before their defaults. Choose Language Switch, Search Bar, Show Login and Dark Mode. Decide whether Published Pages Only should restrict the reader to published pages. Save and test the corresponding visitor controls and sign-in/sign-out destinations.
In Features add the intended feature, enable it and choose its page when the feature takes over a page. Leave page empty for non-page features such as live chat. For chat select the intended Chat Config rather than assuming a feature toggle creates the chat configuration. Save and test the actual visitor page/widget. Turning enabled off keeps the feature row but should stop that feature; verify the result.
In My Account choose the layout page, enabled account features and a preset (default, minimal, modern, elegant, dark or midnight). Save and inspect it as an authenticated customer. These are presentation/availability choices, not proof that the customer’s underlying orders or integrations exist.
Check the result: The selected visitor behavior appears on the correct site, with redirects and account layout verified in the proper session.
8. Store presentation, tracking and spam settings
Why this matters
Site-level storefront options determine how the shop is presented. They do not replace product, payment or shipping configuration. Keep those module setups separate while testing their result in this site.
Follow these steps
Open Storefront settings. Choose Template, Quick View and Extra Info Display; set Show Search, Show Comments and Show Share. Choose Filters Position. Add a filter with Source and Name, then its permitted Display control. Price filters can expose range controls and Min Increment; an attribute filter requires an Attribute selection. Save and test with products that actually contain those values. The inspected Quick View default is left although its enum lists none/dialog/drawer-left/drawer-right: select an explicit supported value and verify persistence rather than teaching the inconsistent default.
Open the social/tracking group. Enter the intended Pixel, Google Analytic, Google Site Verification or Bing Site Verification values only for configured services. Add social rows with Name, Handle and URL, save and inspect rendered links. Under Spam Protection inspect the contact/comment and account-flow protection switches. Enabling a switch is not evidence that provider credentials or verification are configured: test the corresponding form and the actual rejection/success behavior.
Check the result: Shop controls and social links work; tracking and spam services are only marked verified after observing their actual behavior.
9. Read the domain instructions and verify their target
Why this matters
After Attach Domain, Appmint opens DNS Configuration. The hostname target belongs to the selected record. Read it from the actual dialog rather than copying another organization’s example.
Follow these steps
After a controlled attachment, read DNS Configuration. The inspected UI shows an A record at @ and a www CNAME; the CNAME is calculated from the site Host Name or development Production URL. Copy the exact hostname for the intended record into the DNS provider’s matching record only after confirming deployment requirements. Check the apex and www addresses separately and verify TLS and the correct content. For a disposable site alias, use Remove and confirm that the site’s alias state changes after refresh. Domain removal does not automatically remove DNS at an external registrar.
Check the result: Domain association, external DNS and HTTPS content all agree.
Production finding: The A record value is hardcoded to 104.21.94.214 in the inspected UI. This pass did not verify that it is correct for the deployment. Do not publish it as a universal instruction or change real DNS without validating the target. Dev-environment removal remains unimplemented; site removal is a different endpoint. Deleting a site passes deleteResources:true, so it is not merely hiding the record.
Additional source references: installed SDK src/models/site.ts; site-management/modern-site-app.tsx.
Troubleshooting, recovery and alternatives
If the operation fails, keep the error text and inspect the saved state before retrying. A confirmation message is not enough: reopen the item or reader/output destination. Do not repeat a create action while the original request is pending. Use the smallest disposable example to distinguish a missing permission, unavailable backend or incomplete implementation from a content mistake. Keep explanations of prerequisites separate from the continuous task demonstration.
Next steps
You now have the module’s main path and the checks that tell you whether the result is ready to use. Keep the editable source, verify the output where your audience will see it, and return to the relevant chapter when you need an alternative.
Limitations and checks
Source-only manuscript: no site/environment/domain was created here. Vibe Studio, provisioning, DNS, certificates and quota behavior need a live rehearsal. The source explicitly notes development-environment domain removal is unimplemented; preview domains expose Open without a Remove button. Site settings and deployment-specific DNS instructions need a deeper verified companion before final video production. Do not imply a domain field alone configures DNS or TLS.