> For the complete documentation index, see [llms.txt](https://docs.varbase.vardot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.varbase.vardot.com/content-designers/from-client-needs-to-a-varbase-plan/hand-over-a-site-after-launch.md).

# Hand Over a Site After Launch

Launch is the start of the site's life, not the end of the project. Plan training, updates, support and how success is measured before the launch date.

## What to Plan

* **Training and handover** by role, with each role's own test account. Hand over an editors' handbook: the one-page workflow guide, the role matrix, content standards and the launch checklist, plus these docs.
* **Updates**: Varbase releases about every two to three weeks; security releases follow the Drupal schedule. Agree who applies them, how fast, and how they are tested on staging. Budget regular small updates.
* **Support**: the community (the Varbase issue queue on drupal.org, the Varbase Slack, the public code) and professional support from Vardot or another capable Drupal team. See [How to Get Support](https://docs.varbase.vardot.com/overview/how-to-get-support.md).
* **Measure success**, agreed before launch: can visitors find what they need and complete key tasks; how long editors take to publish and how often they need help; is the site secure, accessible and up to date.
* **A roadmap, not a finish line**: improve content and structure first, then add features in phases, such as a new language or AI help.
