Topic on Talk:Requests for comment/Multi-Content Revisions

Are we going to be stuck with a situation where documentation of a template/module/script can't be edited by most users without unprotecting the entire template/module/script itself? This page seems to indicate as much: "[T]here is a need for ... bundling different kinds of information on a single page ... to allow the different kinds of information to be watched, protected, moved, and deleted together." Will individual slots also be able to be watched, protected, etc. individually?

My take:

• Watched individually seems unlikely to me.
• Protected individually is a requirement if we want to be able to move template documentation into a slot. Without that, template documentation would have to remain a subpage.
• "Moved individually" would be something like a history merge/split and could probably use more thought.
• "Deleted individually" might generally turn out to be the same thing as editing the page to remove/blank the slot. Deleting all the history of one slot while not deleting other slots would, again, probably be something like a history split.
• Whether we'd need individual-slot RevDel is an option question, I believe.

> Protected individually is a requirement if we want to be able to move template documentation into a slot. Without that, template documentation would have to remain a subpage.

I note that even file descriptions + files has been discussed for MCR, and for that the same basic requirement would exist.

I agree that i would like to see a bit more discussion and forethought about how these kinds of interactions would work in an MCR world. They are critical to get right.

Files and their descriptions are already being done in a sort of proto-MCR style. There the 'upload' protection controls the file "slot" and the 'edit' protection controls the description "slot".