Instead of making a page completely ReadOnly, it could get a PageFlag which restricts access in that existing content of a page cannot be changed further, but text could still be appended at the bottom of a page.
Pages that only faciliate discussions may benefit from such an editing restriction. And after all, making a page AppendOnly is less restrictive than making it ReadOnly, which is handy if there is too much trashing of a page’s content (annoying if it happens on the ProjectFrontPage).
| status | wiki engines |
| Implemented | MetaWiki:ErfurtWiki, Swiki/CoWeb, YawsWiki |
| Developing | - |
| Intend to Develop | - |
| Considering | - |
| Rejected | - |
It’s contrary to the idea to collaboratively work on a topic and advance a text, because bugs and errors cannot be fixed if a page becomes AppendOnly. However, YawsWiki allows anyone who knows a password to make non-append changes or remove the AppendOnly flag on a page region.