This topic describes the stages of website development and deployment, and things to consider when planning the implementation of your solution. Episerver is a scalable platform that you can deploy in many ways: on a single server, virtual machines, web farm network clusters, in a cloud-based or locally hosted environment.
Planning and preparing
There are many good approaches for development of a website, from classic to iterative. How you plan, build, design, integrate, test, and deliver your solutions relies on approaches to standardizing your process to make it easy to maintain and enhance your solutions.
Development usually takes place on a developer workstation and the solution is then deployed to a test environment. After successful testing, the solution is deployed to a live production web server.
You should coordinate your requirements, deployment architecture, systems integration needs, and infrastructure up front. Good planning and preparation saves a lot of time and effort over the life of a website.
Before you deploy a website, consider the following:
- What preparations do you need?
- What technical aspects must be considered during development?
- How should you build content?
- How is the acceptance testing done?
- Should you migrate content from an existing website, or create a new website from scratch?
- What features do you want implemented on the website?
- How will you host and maintain the website: on-premises or using a cloud-based solution?
See also the Episerver system requirements when planning your implementation.
Primary development of your solution has a strong focus on requirements and iterative delivery, with frequent communication with your end users and customers. The more you communicate and show progress during this phase, the more solid your efforts and results will be as you move into integration and testing.
After you complete core development, thoroughly test and verify your system, including the public-facing portion, business logic you have developed, the back-end systems, and all interfaces you have with third-party systems and controls. Also, test your solution in conjunction with the expected business processes and operational support teams that will be operating and managing the solution.
Deploying an Episerver solution requires planning and timing to roll out your solution to a live or production environment to ensure your customer's experience is a good one. Your deployment may take different forms such as a cut-over from an existing system, or launch your new site from a new system.
The final stage is ongoing maintenance, enhancements, and improvements that are part of growing and supporting your Episerver solution.
Last updated: Mar 27, 2017