Your new site is now largely complete, and the goal is to confirm everything works as expected and to make sure your team is comfortable managing the site before it goes live.
Staging Site
After your pages are built and content is migrated, we share access to the staging site where your team can review the final, working draft of the site. The staging site is where all work happens before launch. It allows us to build, test, and refine the site without affecting your live website. Once everything is reviewed and approved, the staging site is “pushed live” and becomes your active website. The staging site is then hidden, and we use it internally if we need to do any development updates down the road.
Training
Training is designed to give your team confidence managing the site on day one and beyond. Anyone responsible for updating content or managing the site after launch should attend. Training is recorded for future reference. We break it into two sessions so you can learn the essentials first, then go deeper once you’ve had time to explore.
Session 1 focuses on day-to-day site management.
We walk through the most common tasks your team will handle, such as editing pages with PageBuilderLS, updating text and images, managing posts, and understanding how the content management system is structured. This session is practical and task-oriented, so administrators can start making updates right away.
Session 2 goes deeper and answers your questions.
After you’ve had time to use the site in the staging environment, we reconvene to cover more advanced topics, address questions that came up, and walk through more advanced scenarios. This session is tailored to your needs and how your team plans to use the site. This session can take place before or after site launch.
Training Reference Materials
We share the recordings of the training sessions, and we provide a reference guide that outlines common tasks and is helpful for onboarding new team members in the future.
Quality Assurance (QA)
We complete a full internal quality assurance process, testing functionality, layouts, responsiveness, and accessibility. Your team also reviews the staging site carefully and logs any issues or questions you encounter. We address reported bugs and resolve any issues.
We typically allow up to 2 weeks for pre-launch QA so your team has time to review the site carefully and practice editing. This window can be adjusted if needed, but it’s important that all issues, questions, and concerns are reported during this period. Items surfaced after this phase concludes may be handled post-launch or evaluated separately depending on scope and impact.
