pwhipp
commented
9 years ago This would be interesting. As it is a potentially large undertaking I'd need to commit a couple of hours into investigating it (including a search for existing stuff) before I can tell you how much work is involved.
I'd guess that implementing a feature like this would be not less than a day of work if we're prepared to be quick and dirty but more likely to be perhaps two or three days if we are to retain compatibility with mezzanine updates.
cccs-ip
... one possibility in lieu of using wikis
CCCS was using 'project' wikis as a quick way of developing content among small teams. Our wikis were helpful especially for the ease with which page could be create, renamed/moved and sorted. It was also handy to have an in-built compare function. Wikis, however, are meant to be open to "everyone"--making access control issues a challenge. For 'internal' wikis, there is only the ability to collaborate behind a private wiki.
There are few good options for publishing collaboratively-developed documents on the web that can facilitate both "public" and "behind the scenes" interactions among collaborators. Wiki articles, for example, cannot be set to as 'visible only to team members who are logged in'--reserving 'public' and 'private' sections of the site.
Our current web framework has a lot of advantages over the wiki, but it is not yet as helpful as a too for collaborative publication, as was the wiki. Changes to content, for example, are lost if one user saves a mistaken change. While good database backup protocol can help to avoid data loss and compromise, it would be better if the database maintained a record of changes (like wikis do) allowing Git diff functions.