Refactor By Merging

Take pages with similar or closely-related content. Decide which name is better. Merge and condense all content to the page with the "good" name synonym. Reduce the "bad" name synonyms to just a link to the "good" one by using "See good name" (SeeAlso). Update all the BackLinks to point to the new single page. Use SixSingleQuotes to unlink any references to the old page name needed for historical purposes. Perhaps someday delete the old pages.

If you are reading these lists, and you have some spare time, merging one or more of these groups would be appreciated by all as part of the permanent WikiSpringCleaning. If you are one of the people who intentionally or unintentionally created redundant pages, please FixYourWiki.

One approach to tackling big groups is to RefactorLowHangingFruit.


Page Groups That Are Candidates for Merging

Big Groups (more than four related pages)

Small Groups (four or fewer related pages)


Refactor To Singular Form

One consequence of the WikiNamePluralProblem is that Wiki tends to spawn paired singular/plural pages (e.g., "FooBar" and "FooBars"). In some cases there's a useful distinction between singular and plural, but there are some cases where it is sensible to refactor to singular form.

[Note: the list below doesn't contain more complicated singular/plural pairs such as UserStory/UserStories.]

If a pair of pages shouldn't be merged (e.g., CategoryBook and CategoryBooks), please remove them from the list. If some more need to be added to the list, do so.

It is sensible to preserve the plural form if it's liable to be recreated, or exists in numerous places. For example, new links to UnitTests appear every few weeks, so keep UnitTests as a redirection to UnitTest. For pages with uncommon names, or those that haven't been changed in a long time, it probably makes sense to refactor to singular form and delete the plural page. Some refactorers however may not follow this convention.

  1. CorporateWiki, CorporateWikis
  2. CulturalAssumption, CulturalAssumptions
  3. DataStructure, DataStructures
  4. DesignPattern, DesignPatterns
  5. ElementaryPattern, ElementaryPatterns
  6. EmbeddedSystem, EmbeddedSystems
  7. EnterpriseJavaBean, EnterpriseJavaBeans : 'Beans' plural is Sun jargon; keep both pages.
  8. EvolutionaryAlgorithm, EvolutionaryAlgorithms
  9. ExceptionPattern, ExceptionPatterns
  10. ExtremeProgrammingPractice, ExtremeProgrammingPractices
  11. ExtremeProgrammingProject, ExtremeProgrammingProjects
  12. ExtremeRole, ExtremeRoles
  13. FunctionalTest, FunctionalTests
  14. GraphicsPattern, GraphicsPatterns
  15. HorizontalStripe, HorizontalStripes
  16. JavaDesignFlaw, JavaDesignFlaws
  17. JavaIdiom, JavaIdioms
  18. JavaUnitClone, JavaUnitClones
  19. OperatingSystem, OperatingSystems
  20. PatternForm, PatternForms
  21. PatternLanguage, PatternLanguages
  22. RefactoringPattern, RefactoringPatterns
  23. RelationalDatabase, RelationalDatabases
  24. SecurityPattern, SecurityPatterns
  25. SisterSite, SisterSites
  26. SmalltalkTutorial, SmalltalkTutorials
  27. SoftwarePattern, SoftwarePatterns
  28. SoftwareProductLine, SoftwareProductLines
  29. TemplateSpecialization, TemplateSpecializations
  30. TestingFramework, TestingFrameworks
  31. UnixOperatingSystem, UnixOperatingSystems
  32. UseCase, UseCases
  33. WebService, WebServices
  34. WikiClone, WikiClones
  35. WikiFarm, WikiFarms
  36. WikiForum, WikiForums
  37. WikiPattern, WikiPatterns

See RefactoringWikiPages, OnceAndOnlyOnceOnWiki, WikiPenance, HailWiki, MergeMe


CategoryWikiMaintenance CategoryWikiRefactoring

EditText of this page (last edited October 25, 2009) or FindPage with title or text search