Content refactorings

From WhyNotWiki

Aliases: Organizational refactorings (rename to?)

This is to collect examples of the types of refactorings one commonly needs to do in order to write / organize information...

[edit] Copy some content to another location and have both share a common ancestry

Requires: [Revision control system / copy command (category)]

Example: Merb started as a category on "Meeting with Ezra...". But then it grew and needed its own page. Since "Meeting with Ezra..." was marked as "read-only"/"archived"/"for historical purposes"/"history" (it was notes from a meeting; meetings are very finite; once the meeting is over and it is reported upon, nothing will ever be added to that meeting or taken away from the meeting; it's history), I don't want to remove it from that article. Rather, I want to copy from there (duplication! aah!).

But not just copy and paste, as that wouldn't retain any of the revision history and wouldn't store where it was copied from. So we need an operation that includes that metadata(ancestory, revision history). Sort of like svn copy does.

[edit] Move to more specific category

Needed to move Ruby on Rails from Category:Software development to Category:Web application frameworks, after the latter, more specific category was created.