Structure the site around the brief
Create the pages and sections the audience needs. Use reusable collections for content that appears in more than one place, such as FAQs or service listings.
Topolo for Web designers & studios
Give the client a website they can actually review.
Build the page structure, edit the content and inspect a real preview in Topolo Web. Keep reusable content in the CMS and publish a reviewed version when the site is ready.
The work behind the workflow
A website handover should not turn every edit into a development task.
The layout is ready, but the client still needs to change a service description, add an FAQ or refine a call to action. When that content is buried in source files, small revisions keep coming back to the studio. Topolo Web gives the site’s pages, sections and collections an editable home, while keeping draft review separate from the version visitors see.
How it works
From a clear brief to a reviewed publication.
Work on the site itself, with the content and the launch decision kept visible.
Review a real preview
Check the draft’s layout, copy, links and images at desktop and mobile sizes. Apply the client’s correction in the CMS and review the result.
Publish a version you can identify
Run the launch checks, then publish an immutable version. Connect an active custom domain for the public site and retain publication history for recovery.
Evaluate the wider workflow.
Keep the first exercise bounded, then check the handoffs needed for a broader process.
Website delivery for digital agencies
A website handover should include the content, domain and measurement decisions, not just the design. Keep reusable pages in Web and review the enquiry journey before publication.
Structure the site
Agree the pages, reusable content and client editing responsibilities in Web.
Check the enquiry
Use Forms for the intended request fields and inspect where the submission is delivered.
Prepare the handover
Verify the customer domain and the Insights collector before the client takes over.
Before expanding
Verify domain ownership, publication rights, submission delivery and the agreed event definitions.
Bring a real example to the conversation.
Use these questions to explain your current process and agree what a useful evaluation would need to show.
Walk through your most recent brief-to-preview delivery. Where did time accumulate?
Consider this against a recent example from your own process.
What did the client change after seeing the first preview?
Consider this against a recent example from your own process.
Which page elements and accessibility requirements are mandatory for a typical small site?
Consider this against a recent example from your own process.
Which review format works today, and must reviewers sign in?
Consider this against a recent example from your own process.
Who approves content and publication, and who controls the studio’s tool budget?
Consider this against a recent example from your own process.
Could an unpublished three-section draft test the bottleneck? What would count as a useful first-preview improvement?
Consider this against a recent example from your own process.
Agree the result before the pilot.
These are proposed checks to tailor with the people doing the work. They describe an evaluation, not results already achieved.
Draft
Create and read back an unpublished draft containing the three agreed sections and supplied copy.
Preview
Preview opens and content is legible at agreed desktop and mobile sizes.
Review correction
One authorized internal review yields a correction that is applied and retained in the draft.
Quality and value
No critical validation issue remains. First accepted preview meets the pre-agreed time/quality target.
Decision
Studio owner records missing features and whether the next comparable brief can use the same workflow.
The suite
The apps around your workflow.
Start with the app that solves the immediate problem. Bring in the others when the work needs them, with access governed by each app and workspace.
Web
Editable websites, reusable CMS content and reviewed publication.
Brand
Approved identity, assets, voice and claims in a published brand kit.
Design
Brand-led creative projects, variants and reviewed exports.
Bytes
Files, folders, search and sharing for the material behind the work.
Forms
Structured intake, public forms and submissions with defined delivery settings.
Compose
Business documents, saved versions and an assigned review.
Before you get started.
Useful questions for choosing the right starting point.
Can the client review a draft before it is public?
Yes. Topolo Web provides a draft preview separately from the published site. You can revise the draft while the existing public version remains active.
Can a site use its own domain?
Yes. Add the custom domain, configure its required DNS records, then verify ownership and TLS activation. The domain must be active before it can serve the finished site.
Can pages share content?
Yes. CMS collections and reusable menus can support repeated content across pages. Use the same collection where a shared list should stay consistent.
Keep exploring.
Check the product, review the details or talk through your next workflow.
Explore Web
See the Web workspace and its current availability.
Read the Web reference
See the available capabilities and how they work.
Browse related solutions
Find another starting point for your business or role.
Check plans and pricing
Review current plan terms and the apps your workflow needs.
Book a demo
Talk through the process and requirements you want to evaluate.
Keep the next website editable after launch.
Explore Web, or book a demo around your studio’s build, review and handover process.