GoArch:Perfection is not required
 | This page documents an Archive policy. It describes a widely accepted standard that all editors should normally follow. To propose changes, use this sub-page. |
One of the most disconcerting features of the wiki system is its incompleteness. At any given time, there are probably going to be more pages that are in some stage of incompletion than finished, polished articles. And this is a good thing—it means the wiki is expanding!
This may go against common sense—most people are used to seeing web pages as completed, static works that don't change (and probably don't need to change). When writing a page, you may have the urge to make sure the article is finished and polished before you post it. You need to fight that urge! It's better to have a rough, unfinished article that can be refined and revised instead of no article at all.
The key to the lack of perfection is the opportunity for collaboration. You may only post a rough, vague skeleton of an article (or even less, and just a stub), but that's okay, because other archivists can pitch in and add their own ideas. It's like the old cliché goes: two heads are better than one.
And ultimately, this process will attain perfection, because everyone is working together towards a common goal. That goal is just a lot further off than it might seem.
See also[edit source]
Content in this section is based on policies created by Memory Alpha. In accordance with Memory Alpha's licensing terms, the material on this page is licensed under the Creative Commons Attribution/Non-Commercial license.
