- in my experience most cms implementations are handled by a partner or vendor with some expertise. few businesses have the direction/leadership in place to hire a few devs of the intended cms and start hacking away.
- if you are targeting enterprise you need to market to C-level (or slightly below) marketing people, not devs. marketing holds the keys here and any technical people are usually just along for the ride.
- non-cms content (coming from business systems/integrations) will come into play quickly, figure out a simple blueprint to extend the cms object model to account for this.
- though these were enterprise setups they were usually way off the mark by the time we talked to actual system users. think multiserver architecture, requirements to edit the most obscure content that will never be touched after launch, integrations that dont make sense, access to inaccessible data, etc. probably 30% of the time it should've been something simpler like wordpress, netlifyCMS, etc., 30% should have been static content, 20% should have been completely custom and 20% were actually a good fit for the cms.
- set up examples of common site layouts/components and a WYSIWYG implementation for each. non technical users will expect to be able to change EVERYTHING and page templates quickly turn into a mess trying to keep it all together. episerver has a pretty good system for this IMO.