CMS has been designed to address the Webmaster bottleneck. To eliminate this problem, CMS uses a number of different components and interfaces. The components serve four basic purposes: to enable dynamic Web page rendering, to help authors publish their content, to manage the CMS server, and to enable developers to build CMS sites.
The server component is the heart of CMS. Previously, this piece was responsible for a good portion of the CMS workload. However, over the last few releases, CMS has evolved and distributed a number of functions to other components. The primary client used to be the Site Manager application. However, the Web Author applications and the Visual Studio .NET integration are now used for many features previously available only through the Site Manager.
Support for the .NET platform has brought more flexibility into the architecture of CMS. For example, the new application context provides CMS developers with new development and integration options.
CMS is a powerful platform for creating content-centric applications. As new technologies have emerged, CMS has leveraged them. At the time of writing, the next release of CMS is still being designed. However, it is logical to expect that CMS will provide more features built on top of the .NET platform.