Yes, but the point is that now we don’t have to build a full CMS. Off the shelf ones won’t typically work for the sort of content being edited (i.e. it’s not blog posts etc).
But you do need an Engineer to hit the merge button for you when a build is green.
This is okay now, but could become a major pain when your company grows and Nancy in Accounting who is an aspiring writer starts making _hundreds_ of copy changes with pull requests every week. You're going to really wonder where all your engineering time went when suddenly you have a dozen Nancy in Accountings...or a hundred.
Then somebody sits down with Nancy and reminds her what her job is. If she can't handle it still then you revoke her access or fire her for abusing business tools.
But she gets her job done and probably very well. The point is that you gave _everyone in the company_ the ability to contribute to the product.
If you do that, you are communicating to your employees that everyone is welcome to make contributions to the product. If not, why the f* would you do it?
Because you expect your employees to behave like adults? I assume you don't just give everyone access without and set them free without any training or guidance. If someone can't handle a responsibility you take away the responsibility and/or replace them.
I have access to pretty much every Confluence page at work, including ones other people set up for executives to look at, but I don't go around making changes and editing those pages just because I have access.
People aren't robots. You can hold them accountable for their actions and they can make their own (good or bad) choices.
Fair point. Currently we don’t encourage this across the whole company for copy changes. We mostly teach this to specific people who need to edit specific data.
