Publish the page, not the project
A finished campaign page does not have to wait for the homepage redesign.
Publish what’s ready.
Keep working on the rest.
Review changes by page, choose what goes to the review link or live site, and leave unfinished work in the editor. Tandmade handles the build and everything the site needs underneath.
Review first. Switch the domain only when you’re ready.
Home can go.
Fleet can wait.
Tandmade groups changes by page. Select what is ready, leave the rest in progress and see whole-site changes separately before anything goes out.
Selective publishingUnfinished work stays put
Pages you leave unchecked remain in the working copy for the next publish.
Whole-site changes stay visible
Shared components, Brand and site-wide styles appear separately, so their reach is never hidden inside one page.
The first publish sends the full site. Page-by-page publishing starts once the live site exists.
See the website change.
Not just the code change.
Changes are written in the language of the page: what moved, what was added and what visitors will see. Open the exact place, undo one change or inspect the CSS when you need it.
ReviewPlain language first
A marketer can review the website without translating a file diff.
The exact place is one click away
Open the affected page and section directly from the publish panel.
Code when it matters
Designers and developers can inspect the precise CSS change without making everyone perform a code review.
Useful checks.
No surprise gates.
Tandmade points out problems before the site goes live without turning publishing into another approval bureaucracy.
Before publishingCatch the obvious mistakes
Links, image descriptions, button labels and page metadata are checked before publish.
Fix them where they happen
Each suggestion names the section or page where the problem is.
Publishing remains a decision
Checks inform the team. They do not silently block a time-sensitive release.
Review first.
Go live when it’s right.
Send the selected changes to a shareable review link or to the verified public domain. Same project, two deliberate destinations.
DestinationsFor approval
Review link
Share the latest version with the team or client without changing the live website.
For visitors
Live site
Publish the selected, approved work to the verified custom domain.
Agents can make the change. A person still decides which destination receives it.
If the publish fails,
the live site doesn’t.
Tandmade prepares the new version separately. A failed build leaves the current live website exactly where it was.
Release safetyThe current site stays live
A build error never replaces the last working public version.
Hand the failure to the agent
Fix with agent includes the build output, so the agent starts with the relevant context.
Close the tab
Publishing runs on the server and continues while you work elsewhere.
Restore a previous publish
Return to one of the last six published versions without rolling CMS records backwards with it.
Publish the website.
Tandmade handles what it needs to run.
The platform builds the site, prepares its data and media, uploads the files, configures the address and keeps the result fast and secure.
UnderneathInfrastructure follows the site
Sites that need structured content get their own database and media storage. Static sites remain static.
Media is prepared for the visitor
Images are resized and delivered in modern formats at the width the browser needs.
Performance is part of publishing
Static files are cached, dynamic content is invalidated when it changes and HTTPS is handled automatically.
Cloudflare Workers · D1 · R2 · CDN · HTTPS
Move the address.
Not the risk.
Verify the domain while the old website is still running. Publish the new site, switch traffic last and let Tandmade keep checking the records in the background.
Domainsvesper.aeroThe current site stays online until you switch.1Verify ownershipTXT recordsIn DNS2Publish the siteReady3Switch trafficCNAMEsites.tandmade.comDNS at Wedos · Checked in the backgroundOpen WedosAddressesvesper.aeroMainwww.vesper.aero301HTTPS · Certificate issued
Keep the old site online
Ownership and the HTTPS certificate are prepared before visitors are redirected.
DNS without the archaeology
Copy each value, copy everything at once or send the full set of records to IT.
Connect a domainTandmade keeps checking
Pending records are checked automatically, even after the settings page is closed.
One main address
Choose example.com or www.example.com as the main domain. The other redirects to it.
The site is live.
Everyday work isn’t a deployment.
Articles, case studies and form submissions keep moving without reopening the release process.
Everyday operationsJournalPrivate jet charter to NiceSaved · not live yetPublish changesPublished · just now
Publish the item, not the website
A CMS record goes live independently. The page does not need another build or deployment.
New submissionContact · just nowEmma Wrightemma@example.comFour of us, Prague to Nice on 18 October. Can you quote?StoredEmail sentWebhook delivered
Save the enquiry before sending the email
Tandmade stores every submission in the site’s database before sending notifications or webhooks.
The website and its day-to-day operation remain the same system.
A coding agent can deploy a repository.
Tandmade publishes the website.
The pages you chose. The changes your team reviewed. The content, data and infrastructure the site needs to keep working.
Questions
Can I publish only selected pages?
Yes. Once the site has been published for the first time, select the pages that are ready and leave the rest in the working copy. Whole-site changes are shown separately because they can affect more than one page.
What happens on the first publish?
The first publish sends the complete site so the public version has a consistent starting point. Page-by-page publishing is available for later changes.
What happens to pages I leave unchecked?
Their changes stay in the editor and wait for a later publish. They are not discarded or added to the public site.
Can I publish to a review link first?
Yes. The review link is a separate destination kept out of search. Use it for internal or client review before publishing to the public domain.
What happens if the build fails?
The current live website stays untouched. Retry, inspect the details or ask the agent to fix the build error.
Can I close Tandmade during publishing?
Yes. Publishing runs on the server and continues after the tab is closed.
Do CMS updates require a site publish?
No. Published CMS records update independently of the site build. Layout, styles and static-page changes use the normal Publish flow.
Can I restore an earlier published version?
Yes. Restore one of the last six published site versions. CMS content has its own publishing and version history and is not rolled backwards with the site.
Can I connect a domain without taking the current site offline?
Yes. Verify ownership and prepare HTTPS while the current site remains online. Switch traffic only after the Tandmade version is ready.
Who can publish?
Owners, admins and members with full site access can publish the website. Content editors can publish CMS records without access to the full design and release controls.
Publish the work that’s ready.
Keep the rest moving.
Start with a free draft. Make one real change, share it on a review link and move the domain only when the site is ready.