Having Spent Many Years With the Product, Can You Believe I Still Speak Highly of It?

We have set up content authoring teams with different permissions. There are people whose job it is to simply curate content, but they need to have it reviewed and do not publish themselves. There are people who approve the work of content authors and also schedule the publishing of content when it makes sense to do so. Then, there are people in the viewers' group. They can see content before it's published and can give opinions on legal-speak, etc. Other groups are assigned specific permissions for special parts of the site. We also have multiple sites. This means additional teams are responsible for their own complete site content. They can run A/B tests, use shared content blocks between sites, or have custom functionality built for them specifically for their needs. Older static sites are easily migrated into the CMS, leveraging the power of the CMS and freeing up developers from having to maintain basic site content on behalf of the business stakeholders. This means they can be more focused on solving real business problems.

Let's talk about the Alloy Demo Site. Developers can spin up a fully functional demo site in minutes. It can be used to test ideas as a sandbox to play around in. Plus, the source code gives pointers in the right direction. Small projects can be done in weeks and larger ones take months. It takes longer to finalize the design than it does to build the templates and the blocks. What also takes time is understanding what you can get out of the product in terms of leveraging its capabilities. Often, more time is spent on how it looks than how it's meant to work. More effort spent on leveraging the search functionality and designing the site structure really pays off.