The demand for more XML content has shifted the work of creating it from technical writers to other departments of a company. Since these people work only occasionally on content creation the investment to have them set up the necessary tools does not pay off.

The idea of having a self-service project template that has all the configuration in place can be applied in other scenarios such as creating similar documentation for multiple products. For example, customizable products whose documentation has a standard format but the parameters can differ, datasheets for microchips or release notes for a software product.

For cloud-based services, the ease of setup is at odds with other business driving factors such as security, legal compliance, and brand exposure. For example, if a company provides a back-end service as using a freemium pricing model, they want the user to be aware that about that service. So, it is not uncommon that during the setup users will be exposed to a screen presenting that service.

However, in an enterprise environment, these factors are not that relevant which can provide an even more intuitive user on-boarding experience. For example, a back-end service can is usually licensed by the company and configured by a system administrator and is totally transparent to the end-user.