A WEBSITE. A SMALL PLOT TWIST.
Almost there.
Enter ViveTile.
The page is built. The idea is good. There’s just that one little thing missing.
Meet four people getting their websites unstuck.
Meet Ada and the blue mugMade-up characters. Familiar website problems. Illustrations show examples of available features, not customer testimonials or live dashboards.
Makes mugs. Not backends.
One mug. Three sizes. Zero desire to resize it again.
“Do I really need to export this photo three more times?”
Ada’s pottery website is ready for its close-up. Her product photos? They need a square thumbnail here, a card there, and a bigger preview over there.
Enter ViveTile.She puts the photos in an Image library and creates three presets. Same source image, different sizes, each with its own stable URL.
New photo of the blue mug? Ada replaces the source. The links stay put. Back to the pottery wheel.
Image libraries · Presets · Bulk actionsThree formats. Their own stable URLs.
How Ada does it 3 small steps
- Upload the photos to a library. Start with Thumb, Card and Preview, or choose your own dimensions.
- Publish the images, preview each format and copy its URL into the site.
- Add more photos or replace a source. Presets also apply to new images in the library.
A published image collection counts as one active VTile. Image delivery and storage still contribute to estimated usage.
Open the practical guideBuilt the page. Met the missing piece.
The site looks great. The contact form goes… where?
“The AI made a lovely button. Who gets the message?”
Leo has turned an idea into a website with a little help from an AI coding assistant. There’s a contact form, a send button, and one very good question.
Enter ViveTile.He creates a Form in ViveTile, activates it, and gives its action URL to the coding assistant. The existing HTML form now has somewhere to send named fields.
The next request is saved in his dashboard. Leo can also ask for an email notification. His website has something useful to say back: thank you.
Form libraries · Saved responses · Optional emailA small message.
A real place to land.
How Leo does it 3 small steps
- Create a form in Form libraries. Add a notification email or an HTTPS thank-you page if you want one.
- Activate it. Open Install and connect the action URL to your HTML form using POST.
- Submit a test from an allowed website. Open Submissions to read the saved response.
Bring your own form design. File uploads, automatic email retries and advanced integrations are not included.
Open the practical guideBakes first. Updates second.
Tomorrow’s special shouldn’t need a website project.
“The cinnamon buns are back. Can the website know?”
Nina’s café has a website. It also has last month’s announcement. She wants to share tomorrow’s special and point visitors to the menu.
Enter ViveTile.She installs an Announcement and a CTA once. Then she can edit the message and button destination in ViveTile, preview them, and publish when they’re ready.
The site gets the new message. Nina gets back to the oven. Next week’s special starts with the same two VTiles.
Announcements · CTA buttons · Draft & publishGood coffee.
Excellent excuses
to stay a little.
See tomorrow’s menu Same website. Fresh news.
How Nina does it 3 small steps
- Create an Announcement and a CTA. Set their text, colours and the button destination.
- Save, publish and copy their installation snippets into the website.
- When the news changes, edit the drafts and publish again. No new snippet needed.
Publishing can take time to propagate. The CTA is a link; click analytics and scheduled publishing are not included.
Open the practical guideOne person. More than one website.
The portfolio. The shop. Oh, and the side project.
“Which project did I put that image in?”
Sam builds websites for a living and occasionally for fun. Each has its own images, forms and small updates. The collection of browser tabs is getting ambitious.
Enter ViveTile.With VGrowth, Sam adds the sites to one account and keeps their libraries separate. Bulk image actions help with the bigger collections; Usage & credits shows where the recorded activity comes from.
A place for every project, and a shared view of estimated consumption. Sam’s next site doesn’t need another numerical site allowance.
Multiple sites · Organised libraries · Usage estimatesHow Sam does it 3 small steps
- Use VGrowth for multiple sites. Add each website and its allowed addresses.
- Keep each project’s images and forms in that site’s libraries. Select images in bulk when useful.
- Review estimated account usage, then filter by website or inspect a resource.
VGrowth has no numerical site or active VTile limit. Traffic is still measured. Separate client logins and team roles are not available.
Open the practical guideYour website doesn’t
need a plot twist.
Just its next little thing.
Start with one image collection, a form or a message. Keep building from there.
VSmall: one site, three active VTiles. VGrowth: no numerical site or active VTile limit. Usage allowances and technical limits apply.