In the previous chapter, we implemented one of the more complicated features of building a modern SPA frontend: server-side rendering. We had to make quite a lot of changes to the application to prepare it for SSR, as well as fix a number of bugs that cropped up when attempting to render browser-reliant components on the server. However, the application itself is now as feature-complete as it's going to be for the purposes of this book.
In this final chapter, we're going to improve our current deployment mechanism by implementing a Continuous Integration (CI) and Continuous Deployment (CD) pipeline using Visual Studio Team Services (VSTS). VSTS isn't the only option available to us, as there are many different ways that we can build a CI/CD pipeline, but as we're hosting within Azure, it makes a lot of sense...
