With many years under our belt, there is content that we have access to but we only have access to it after going through a couple of pages to get to it. I was thinking of creating a new namespace dedicated to wiki related archives. This namespace is not for user archives.

The title on the page would appear as k6yg4GB.png

The title on a page such as a forum would appear as KmfWtii.png

What this is doing is literally taking all of the content from a page and putting it to a new page in a different archive. The best part of this is that the history of the page will be transferred with it as well.

This would be very beneficial to the wiki because it would mean we have easy-to-access archives without confusion. And this means that we won't have to use an archive template any longer.

Current archives have the chance of not having the history included when the page moves to the new namespace. That is due to the content of the page having been copied to a new page to create the archive. DangerousDangerously 16:54, April 30, 2013 (UTC)

Discussion and Voting

Support Support: As the suggester. DangerousDangerously 16:55, April 30, 2013 (UTC)
Oppose Oppose: There's nothing wrong with "Page/archive." For easy access, just categorize all of the /archive pages under "Category:Archives" or something. The Puzzle Master 01:17, May 1, 2013 (UTC)
Comment Comment: The thing with that is that many people don't know about categories and don't know that the archives exist. With a new namespace it's clear and obvious that the archives exist. And you can't move an old forum to "Forum:Title/Archive" because then "Forum:Title" would no longer exist. But with a new namespace it would be "Archive:Forum:Title" or some other variation to make it so that it's not "Word1:Word2:" because that looks bad. DangerousDangerously 01:45, May 1, 2013 (UTC)

Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.