Microsites

Microsites let you build and share standalone web pages directly from Vū AI — a quick way to package content into a shareable link without leaving Vū Studio. You describe what you want in plain language, Vū AI generates the page, and it is saved to your library as a web asset you can preview, refine, and share.

A microsite comes in one of four formats:

Format	Best for
Page (default)	A complete, standalone single-page site — landing pages, one-pagers, and interactive presentations.
Whitepaper	Long-form content — white papers, reports, and briefs. A page styled as a document: cover block, table of contents, sections, and images.
Dashboard	A data-style layout rendered with the dashboard renderer.
Slides	A presentation you page through — a deck with built-in navigation, a slide counter, and a full-screen Present control. See Slide decks.

Microsites are private by default. The link only works for you until you publish it (see Sharing a Microsite).

Creating a Microsite

Open Vū AI and ask it to create a microsite, describing what you want it to contain. The assistant assembles the page for you and saves it so you can revisit and update it later.

To create one:

1. Open Vū AI.
2. Describe the microsite you want — for example, "Create a landing page for our spring product launch with a hero section, three feature cards, and a contact form," or "Make a one-page whitepaper summarizing this report."
3. Vū AI generates the microsite and adds it to your library as a web asset. It opens in the microsite sidebar so you can review it.

Ground it in your own material

If you give Vū AI substantial source content to work from — an attached document, a pasted brief, or an existing asset — it will base the microsite on that material rather than inventing content. Paste or attach what you have before asking it to build the page.

White papers

Ask for a white paper, report, or long-form brief and Vū AI builds it as a regular microsite styled as a white paper, rather than as a plain text document. Because it is an ordinary page underneath, it gets everything a page gets:

• Full page editing — the element picker, direct text editing, image and video swapping, and the Code view, all in the microsite sidebar.
• Real images — library assets and stock photography, placed in the layout (see Embedding your own images and video).
• An editable table of contents — a sticky contents bar written as part of the page, so you can rename, reorder, or remove entries like any other content.
• Animation — calm by default (subtle reveals as you scroll). Ask for a livelier treatment if you want one, and ask for a static page if you want none.

The layout follows a consistent shape — a cover, an executive summary, numbered sections, and a conclusion — and pulls its facts from the material you provide. Paste or attach your source content before asking, exactly as for any other microsite.

note

White papers created before this change keep rendering and editing the way they always have. Existing pages are not converted, and their links stay the same.

Slide decks

Ask Vū AI for a slide deck and it builds the microsite in Slides format. Each slide is a full-screen panel, and Vū Studio wraps the deck in a consistent navigation frame — so every deck moves the same way no matter how the slides themselves are styled.

To create one:

1. Open Vū AI at one.vu.studio/ai — click the Vū Studio icon to go Home, then click Vū AI.
2. Ask for a deck, describing what should be on it — for example, "Build a slide deck introducing our Q4 roadmap, one slide per initiative," or "Turn this brief into a ten-slide pitch deck."
3. Vū AI generates the deck, saves it to your library as a web asset, and opens it in the microsite sidebar.

The look of each slide is Vū AI's — decks are meant to vary. What is fixed is the frame: the navigation, the slide counter, and the full-screen control.

Moving through a deck

Control	What it does
‹ and ›	Previous slide and next slide.
Slide counter	Shows where you are — for example 3 / 12.
Dots	One dot per slide; click any dot to jump straight to that slide.
Present	Takes the deck full screen for presenting. Press it again — or press Esc — to come back out.

The keyboard works the way it does in any deck: ← and → move one slide, and so do Space (Shift+Space to go back), Page Down / Page Up, and n / p. Home and End jump to the first and last slide. Scrolling, swiping on a touchscreen, and a trackpad gesture each advance exactly one slide rather than skidding past several.

The navigation bar stays visible everywhere the deck is shown, including on a wall you cast it to.

Presenting a deck

Select Present to go full screen, then move through the deck with the arrows or the keyboard. Esc leaves full screen. Because a deck is an ordinary microsite underneath, you can also publish it and send the link — the recipient gets the same navigation in their own browser, with no Vū Studio account (see Sharing a Microsite).

Editing a deck

Open Edit in the microsite sidebar and edit a deck exactly as you would any page — text, image and video swaps, section controls, and Save to write everything at once (see Editing it yourself (Edit mode)).

Two things work differently in Edit mode:

• The arrows, the counter, and Present are not shown. They need scripts, which the editor's preview deliberately does not run so that your edits stay accurate.
• The dots and scrolling still work, so every slide is reachable and editable. Click a dot, or scroll, to get to the slide you want.

Everything returns in Preview and on the published page.

Editing one slide. When you use Pick element to point Vū AI at something on a deck, the edit is scoped to the slide that element sits on — so "make the image on this slide smaller" changes that slide and leaves the rest of the deck alone.

Turning an existing page into a deck

Already have a page-format microsite that reads like a deck? Ask Vū AI to turn it into a slide deck. It rewrites the page into proper slides and the navigation frame is applied to the result — your link and version history are preserved, and the change is recorded as a new version like any other edit.

Decks that already have the frame pick up improvements to it automatically the next time they are saved — through a Vū AI edit, a manual Save in the sidebar, or a save from the Code view. You never need to regenerate a deck to get the current navigation.

A deck as a microsite, or as a Canvas design?

Both can build a deck, so the question is where it is going rather than what it can do.

If the deck is…	Build it as
Shared as a link, presented from a laptop, emailed, or published	A microsite in Slides format
Going up on a Vū wall, a display, a lobby screen, or signage	A Canvas design
Something you want to nudge by hand afterwards	A Canvas design — it has a full visual editor
Required to be pixel-exact at a known screen size	A Canvas design

Ask for a deck and Vū AI builds a microsite, then mentions the Canvas alternative. Mention a wall, display, screen, lobby, or signage in your request and it asks which you want first, because a Canvas design is built for a specific screen size and is not something you can resize afterwards.

Embedding your own images and video

Microsites can embed images and video from your Vū Studio library instead of using generic placeholders. Reference the media you want in your request (for example, attach or pin the assets, or ask Vū AI to find them), and it will place them in the page. Only image and video assets can be embedded; if a suitable asset is not available, Vū AI uses a neutral placeholder so the layout stays intact.

Built-in stock imagery

When you have nothing in your library that fits the topic, Vū AI can pull built-in stock photography into the page as a starting point, so a new microsite arrives with real imagery instead of grey boxes. It is used for generic or atmospheric subject matter — cityscapes, textures, abstract backdrops, anonymous people in an office. It is never used to stand in for something of yours: your logo, your product, your team, your venue. For those, point Vū AI at your own assets.

You stay in control of which source is used:

• "Use my own photos" — Vū AI uses library assets only.
• "Use stock images" or "you pick the photos" — Vū AI chooses stock imagery.
• "No stock photos" — Vū AI leaves neutral placeholders you can fill later.

A single page can mix both — your logo in the header, a stock photo behind it.

Swapping a stock image. In Edit mode, select the image and use the Swap control. The picker offers two sources: My Library for your own assets and Unsplash for other stock photos. You can also ask Vū AI to swap it ("replace the hero image with the one I attached"). Swaps are buffered like any other manual edit and are written when you select Save.

Photographer credit for stock images is added to the published page automatically as a single credits line. It updates itself: swap a stock photo for one of your own assets and its credit disappears; remove the last stock photo and the line goes away entirely. You never need to write an attribution yourself.

Uploading HTML files

Already have a finished web page? Upload the .html file and Vū Studio hosts it as a microsite instead of storing it as a file. The page keeps its own markup, styling, and scripts — nothing is regenerated — and it gains everything a generated microsite has: a shareable link, version history, AI and manual editing, publishing, and casting to a display.

There are two ways to bring one in:

• From the Microsites gallery — at one.vu.studio/ai/microsites. Click the Vū Studio icon to go Home → click Vū AI → click Microsites, then click Import an HTML file below the prompt box and pick your file. The imported page opens straight in the editor so you can review it.
• From the Asset Library — at one.vu.studio/library. Click the Vū Studio icon to go Home → click Asset Library, click the Add Media button (➕ icon) → Upload files, and drop the .html file in. It is imported as a microsite and lands in your library rather than going through media processing.

Either way, the first version is recorded as Imported from <filename> in the microsite's version history, so you can always get back to the file exactly as you uploaded it.

What is accepted

Condition	Result
A single .html or .htm file, up to 5 MB	Imported
References to images hosted over https://	Imported — external images load normally
References to files next to the original page (./style.css, ./app.js)	Imported, with a warning naming what is missing
References over http://	Imported, with a mixed-content warning — those files are blocked once the page is served securely
An empty file, a file over 5 MB, or a file that is not HTML	Not imported — the message tells you which

Single file only. The importer takes one self-contained page: only the file you pick is uploaded, so anything it links to alongside it — a separate stylesheet, script, font, or image file — does not come with it. The page still imports and renders, minus those pieces, and Vū Studio names the first few missing references so you know what to inline. Put your CSS and JavaScript inside the file, and either host images at an https:// URL or add them afterwards in the editor.

Sharing an imported page. Uploaded HTML is treated as untrusted content, so when someone other than you opens it — through a share link, a published link, or a shared folder — the page runs in a restricted sandbox. Two consequences worth knowing: a page that saves state in the browser (cookies or local storage) will not be able to do so for those viewers, and a collaborator cannot use the visual Edit mode on your imported page, though editing it through Vū AI still works. Your own view of the page is unrestricted.

Starting from a Template

The Microsites gallery at one.vu.studio/ai/microsites (click the Vū Studio icon to go Home → click Vū AI → click Microsites) has a Templates section below the prompt box. It lists the built-in starter templates together with any templates you or your team have saved (see Saving a Microsite as a Template). Saved templates carry a Yours or Team badge.

1. Click a template tile to open a large, scrollable preview of it.
2. Click Use this template. Vū AI starts a new conversation with a new microsite copied from the template, which you can then change like any other microsite.

Click the Templates heading to collapse or expand the section. Vū Studio remembers your choice.

Rebuilding a Website from Its URL

To remake an existing website as a microsite, give Vū AI the site's web address and say what you want, for example "Remake this site as a microsite, same layout and text: https://example.com". Vū AI reads the page's text, its colors and typefaces, and its layout, then builds a microsite from them. It doesn't save anything from the site other than the new microsite.

• Images. Vū AI doesn't copy images from the original site. Attach the images you want to use, and Vū AI matches them to the page's images by filename. If any are missing, it tells you which ones and asks you to attach them or build without them.
• Typefaces. Fonts are replaced with close Google Fonts matches.
• What it can't read. Vū AI reads the page's code, not a screenshot of it. It places images next to the correct text, but it has to work out from the code which side of the text each image sits on. A site that builds its content with JavaScript gives Vū AI very little text to work with, and Vū AI tells you when this happens.

Showing a Session's Mind Map or Flow

If you use Vū Intelligence sessions, you can put a session's live view on a microsite. Ask Vū AI to add a session to a microsite and say which view you want:

• Mind map: the session's concept graph. This is the default.
• Flow: the session's insights as a moving stream of cards. The number of cards and their size adjust to fit the space on the page.

For example: "Make a microsite recapping the Q3 planning session, with the session as a flow view." In the mind map, visitors can click a node to read the insight behind it.

Things to know:

• Your sessions only. Vū AI can only embed sessions you are able to open. If it can't find or open the session you named, it says so and lists your recent sessions so you can pick the right one.
• Publishing shares the session. Anyone with a published microsite's link can see the embedded view, and the view keeps updating while the session is live. Before you publish, check that the session's content is suitable for everyone who has the link. See Sharing a Microsite.
• Team-only sessions stay team-only. If the session is set so only your team can open shared links, visitors who aren't signed in to your team see a sign-in prompt in place of the view.
• Transcripts aren't included. The embedded view shows the mind map or flow only, never the transcript.

Reviewing in the sidebar

The microsite sidebar has four views, selected with the toggle at the top of the panel:

• Preview — a live view of the current version of the page.
• Edit — a WYSIWYG mode for making manual adjustments yourself (see Updating a Microsite). Shown for page-format microsites; dashboards and older white papers do not have it.
• Code — the raw source. The tab is labelled Data on a dashboard and Markdown on a white paper, because that is what those formats store. Dashboard data is read-only here and is changed through Vū AI instead.
• Feedback — notes left by visitors on the published page. See Collecting feedback from visitors.

Along the top of the panel you also get Share / publish, Open a live preview in a new tab (the tab stays linked and refreshes itself each time a new version is saved), and Close editor. At the foot of the panel, Version history opens the list of every saved version — see Version history.

Sharing a Microsite

Once a microsite is ready, share its link with anyone who needs it. Recipients can open the microsite in any browser — no Vū Studio account required.

Because microsites are private by default, you must publish one before its link will work for other people. Until you publish, the link opens only for you and returns a "not found" page for anyone else.

You can publish in either of two ways:

• Ask Vū AI — tell it to publish or share the microsite (for example, "Publish this and give me the link"). Vū AI makes it public and returns the shareable URL.
• Use the sidebar — select the Share / publish action in the microsite sidebar to open the publish dialog, then publish and copy the public link.

Published microsites are served from a stable public link, and the link stays the same across publish and unpublish cycles.

The Share dialog

Selecting Share / publish in the microsite sidebar opens a dialog headed Share "[your microsite's title]", with a Published or Draft chip showing its current state. Once the page is published the public link appears at the top with Copy next to it and an Open in a new tab control.

Four settings live in this dialog. All of them are optional, and each one takes effect when you select Publish (or Update, on a page that is already published).

Setting	What it does
Collect feedback from visitors	Adds a Give feedback button to the published page so anyone with the link can leave a note without signing in. See Collecting feedback from visitors.
Allowed embed domains	One domain per line, *.acme.com for subdomains. Only the sites you list can put the page inside an iframe. Leave it empty and any site can embed it. The link itself keeps working everywhere either way.
Link expires	A date after which the public link stops working. Use Clear to remove it.
Password	Requires anyone with the link to enter a password before the page will open. On a protected page the dialog shows Password protected with a Remove control, and typing in the field sets a new password.

A page can have a password or an embed allow-list, but not both — whichever one you set disables the other field, and the dialog tells you why. The reason is that restricting embeds relies on the browser reporting which site the page is framed in, and that can be faked, so it is not a safe substitute for a password.

The dialog's buttons are Publish on an unpublished page, and Update plus Unpublish once it is live. Done closes the dialog without changing anything.

Changes after publishing

A published microsite keeps up with your edits. When you add a library image or video — or an embedded Vū Intelligence session — to a page that is already published, visitors see it as soon as the new version is saved, whether the edit came from Vū AI, Edit mode, or the Code view. You do not need to publish again.

If the Share dialog finds media on the page that visitors still cannot see, it says so under the public link — for example 2 items on this page aren't visible to visitors — they were added after this link was last published. Hit Update to publish them. Select Update to fix it.

Anything a visitor cannot be shown appears as a dark panel reading This media isn't available., in place of the image or video, so the layout stays intact. The panel does not say why. Media that is hidden only from visitors still shows when you open the page yourself, so check the page in a private browser window when you need to see exactly what visitors see.

Collecting feedback from visitors

You can invite the people you send a microsite to comment on it, and then act on what they say without leaving the chat.

Turn it on in the Share dialog with Collect feedback from visitors, then select Publish or Update. Feedback is a separate switch from publishing on purpose: making a page public never opens a way for people to write to it unless you ask for it. You can switch it on for a draft as well, so it is ready the moment you publish.

What a visitor sees. A Give feedback button appears in the corner of the published page and stays put as they scroll. Selecting it opens a small panel headed Give feedback that asks What would you change about this page?, with Cancel and Send. Sending shows Thanks — your feedback was sent. No sign-in is needed, and there is a limit on how much feedback one page will accept in a short window, so the button cannot be used to flood you.

What you see. Open the Feedback view in the microsite sidebar. Each note shows its text, how long ago it arrived, and — where the visitor was looking at a recognisable part of the page when they sent it — the name of that section. Notes are also tagged with the version they were left against (V2, for example), and a note left on an older version is highlighted so you do not read a complaint about a page you have since rewritten as though it were about the current one.

Two filters sit above the list:

• Show resolved — include notes you have already dealt with. By default you only see open ones.
• Latest version only — hide anything left against an earlier version of the page.

Each note has three controls:

Control	What it does
Revise	Attaches the note to the chat so you can ask Vū AI to act on it. Where the note names a section, the edit is scoped to that section rather than the whole page.
Tick / undo	Marks the note resolved, or reopens it.
Trash	Deletes the note permanently.

You can also just ask Vū AI about it — "What have people said about this page?" — and it will read the feedback and answer.

note

Visitor feedback is anonymous: it records what was written and which version it was written about, not who wrote it. Anyone with the link can post, which is why deleting a note removes it outright rather than only hiding it.

Making a microsite private again

To stop sharing, unpublish the microsite — ask Vū AI to make it private again, or use the sidebar. Unpublishing takes down the public link for everyone.

caution

Unpublishing breaks any link you have already shared. Anyone you sent the link to will no longer be able to open the microsite.

Microsites on a Display Wall

When a microsite is cast to a wall or a large display, it is scaled up automatically so it stays readable from across the room. Microsite layouts are composed for a desktop browser, and on a very large portrait screen an unscaled page lands as a narrow ribbon of small text down the middle with empty gutters either side.

You do not have to turn this on or configure it, and it does not change the page itself — the scaling is applied to the copy being shown on the wall, so the version in your library and the link you shared are untouched. It applies to existing microsites as well as new ones, including white papers and dashboards.

The page is measured as it is scaled, so it grows only as far as it can without content running off the edge. It is not applied to ordinary browsers, laptops, or tablets — only to screens large enough to be a display.

Updating a Microsite

Ask Vū AI to make changes to an existing microsite at any time — updating text, swapping content, or adjusting layout. When you request a change, Vū AI can review the microsite's current content first, so edits build on what's already there and update only the parts you asked about. Your changes are saved to the same microsite, so the shared link always reflects the latest version.

You have two ways to update a microsite: through Vū AI, or by editing it yourself in the sidebar.

Updating with Vū AI

Ask Vū AI to edit the microsite you are working with — for example, "Make the headline shorter," "Swap the hero image for the one I just attached," or "Add a pricing section below the features." Vū AI applies the change in place and saves a new version. Because it edits the existing microsite rather than creating a new one, your link and version history are preserved.

Pointing Vū AI at part of the page

Rather than describing which bit of the page you mean, you can point at it. In the Preview view select Pick element, then click the part of the page you want to talk about. While you are picking, the up and down arrow keys widen and narrow the selection — up to take in the block around what you clicked, down to get back to the smaller thing inside it — Enter confirms and Esc cancels.

The element you confirm is attached to your next message, so an instruction like "make this shorter" or "swap this for the photo I just uploaded" needs no further explanation. Scoping an edit this way also keeps it contained: Vū AI rewrites the section you pointed at rather than regenerating the whole page.

Duplicating a Microsite

Duplicating a microsite in your library creates a genuinely separate page, not a second tile pointing at the same one. The copy gets its own public link, its own content, and its own version history.

That means you can edit the copy freely without touching the original, and deleting one never takes the other's content with it — so duplicating is a safe way to start a variation of a page that works, or to hand a team-mate a starting point.

Two things to expect:

• The copy is unpublished. It has its own link, and that link does not work for anyone else until you publish the copy in its own right — see Sharing a Microsite.
• Links you already sent still point at the original. The copy never inherits the original's public link, so nothing you have already shared changes.

Saving a Microsite as a Template

When a microsite works well, save it as a template so you or your team can start the next one from it.

1. Open the Microsites gallery at one.vu.studio/ai/microsites (Home → Vū AI → Microsites).
2. Under Your microsites, find the microsite and click its Save as template button.
3. In the Save as template dialog, enter a Name and, if you like, a Description saying what the template is good for.
4. If you are working in a team, choose Who can use it: Only me or Everyone on this team.
5. Click Save template. A Saved as a template. message confirms it.

The template appears in the gallery's Templates section. See Starting from a Template.

What a template keeps:

• A snapshot. The template saves a copy of the microsite as it is when you save it. Later changes to the microsite, or deleting it, don't affect the template.
• Structure and styling. Images and video from your library, stock photos, and embedded sessions are replaced with neutral placeholders. A template shared with your team never contains media that only you can open. Replace the placeholders when you use the template.

Deleting a saved template. Open the template's preview from the Templates section and click Delete, then Confirm Delete. Only the person who saved a template can delete it. Deleting a team template removes it for everyone on the team. Built-in templates can't be deleted.

Editing it yourself (Edit mode)

Open Edit in the microsite sidebar to make manual adjustments without going through the chat. Edit mode is available for page-format microsites, including white papers, slide decks, and imported HTML pages (dashboards use the dashboard renderer instead, and white papers created before the change edit as markdown in the Code view). It offers three kinds of change:

1. Text — text elements on the page become directly editable. Click into any text and type.
2. Image / video swap — click a media element (or its Swap control) to pick a replacement from your library. You can swap an image for a video or vice versa; the surrounding layout is preserved.
3. Section delete / reorder — each section has corner controls to move up (▲), move down (▼), and delete (✕).
4. Image / video placement — hover an image or video and, alongside the Swap control, a small pad appears for nudging it into place: arrows to move up, move left, move right and move down, then make smaller (−), make bigger (+) and reset position and size (⟲). Use this when the picture is right but sitting in the wrong spot or at the wrong size; use Swap when it is the wrong picture.

All manual edits are buffered as you work — nothing saves per action, and the editor shows Unsaved changes until you save. Select Save to write every change at once. Each save appends a new version.

note

In Edit mode the preview renders statically without page animations so that your edits stay accurate. Any motion effects return in the normal Preview and on the published page.

Version history

A microsite records a new version every time valid page changes are saved, so the history is a complete record of how the page got to where it is. That covers every way a page changes:

• an edit you asked Vū AI to make;
• a manual Save in Edit mode (all buffered text, swap, and section changes are written as one version);
• a save from the Code view;
• restoring an earlier version — the restored content is added as a new version at the top of the history rather than rewinding it, so nothing is ever lost and you can roll a rollback forward again.

Versions are numbered in order (V1, V2, …) and labelled with what produced them — for example Initial version, the instruction behind an AI edit, Edited page for a manual save, or Restored: ….

Browsing the history. Select Version history at the foot of the microsite sidebar. The drawer lists every version newest-first with its number, its label and the time it was saved; the one the page currently serves is marked Current. Each row offers Open, which shows that exact version in a new tab, and — on any version that is not the current one — Restore, which asks you to confirm before it writes that content back as a new version at the top of the history.

The same numbers appear on visitor feedback, so a note tagged V2 can be lined up against the version it was about without counting rows.

Asking Vū AI instead. Vū AI can now see a microsite's history, so you do not have to work through the drawer yourself. It can list the versions, describe what changed between any two of them, and restore one on your say-so — "What did you change in the last edit?", "Compare the current page with V3", or "Put back the version before the pricing section went in." It always tells you which version it is about to restore and waits for you to confirm, and it will not restore the version that is already current.

The comparison it gives you is section by section — which sections were added, removed, reworded or moved — rather than a line-by-line list of code changes. On a white paper it compares headings and their text, and on a dashboard it compares cards by title.

The shared link always serves the current version.