Another type of inclusion: skilled versus unskilled, technical versus non-technical. Background toot: publishing markdown for a git-hosted website.
Most static site generators require non-technical users to push markdown content to a repo via a PR. This is highly intimidating I’ve heard many times. Too much friction for many, and they don’t correct the grammar mistakes in your docs. Plus PR’ing is almost nowhere explained in a truly simple way to understand. Us techies take a lot of technical background for granted, it seems. FedeProxy as intermediary might offer a dead easy UI to do this.
(For “United Software Development” this inclusion may extend further to non-technical stakeholder involvement in design process)