Guest User

Wikis need someone like you

a guest
Jul 1st, 2026
35
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
Diff 12.19 KB | None | 0 0
  1. @@ -6,40 +6,43 @@ may expect if you have used Wikipedia, but just a small group of
  2.  dedicated fans who want to document everything they can about what they
  3.  love.
  4.  
  5. -Every wiki out there exists because there was a very passionate fan who
  6. -wanted to document something they loved. A daunting challenge like this
  7. -requires all the hands it can get to help, and helping is as easy as
  8. -hitting the "Edit" button or joining the community to help in other
  9. -ways.
  10. -
  11. -The reality of most wikis is that they are maintained by very few users.
  12. -You may be surprised to learn that most wikis are just 2 or 3 people
  13. -keeping up with the content, the design, the tools to help themselves,
  14. -and who knows what else.
  15. -
  16. -One of the best parts of editing a wiki is that every contribution makes
  17. -a difference, and there are many ways you can contribute. Wikis welcome
  18. -a large variety of people and skills.
  19. +Every wiki exists because there was a very passionate fan who wanted to
  20. +document something they loved. A project like this requires all the
  21. +hands it can get to help, but most often wikis are maintained by few
  22. +people (a lot of times it is just 2 or 3 people) who have to handle not
  23. +only the information, but also design the wiki and find the tools to
  24. +help themselves.
  25. +
  26. +You can help a wiki in many ways, and starting is as easy as hitting the
  27. +"Edit" button or joining the community to talk with them. One of the
  28. +best parts of editing a wiki is that every contribution makes a
  29. +difference, and there are many ways you can contribute. It is very
  30. +satisfying to see thousands of people benefit from something you wrote,
  31. +a screenshot you uploaded, a typo you fixed or a guide you improved to
  32. +help readers for years.
  33. +
  34. +Wikis welcome a large variety of people and skills.
  35.  
  36.  ## Writers and proofreaders
  37.  
  38.  Probably the most obvious way to help a wiki is by reviewing existing
  39. -pages, or writing about information that is missing. You don't really
  40. -need to know everything about the topic. You can contribute by finding
  41. -pages with information that could be better explained, or maybe improve
  42. -the way the information is presented to readers.
  43. +pages, or writing about information that is missing. You don't need to
  44. +be an expert on the topic. You can contribute by finding pages with
  45. +information that could be better explained, or maybe make the
  46. +information easier to understand.
  47.  
  48. -All wikis have somewhere a "Random page" button you can use to visit
  49. -articles at random. In just a couple of clicks, you might find an
  50. -interesting page that you can add information to.
  51. +All wikis have a "Random page" button somewhere in the sidebar or at the
  52. +top that you can use to visit articles at random. In just a couple of
  53. +clicks, you might find an interesting page that you can add information
  54. +to.
  55.  
  56.  ## Researchers
  57.  
  58.  Wikis are never complete, and there is always something missing. Maybe a
  59. -hidden mechanic in a video game, or a very easy-to-miss easter egg in an
  60. +hidden mechanic in a video game, or an easy-to-miss easter egg in an
  61.  episode. Even if you don't consider yourself a good writer, you can help
  62. -simply by sharing in detail those discoveries with the community. Other
  63. -editors can help you to put it into words to write it into an article.
  64. +simply by sharing those discoveries in detail with the community. Other
  65. +editors can help turn your discoveries into a polished article.
  66.  
  67.  With wikis being a popular meeting point for passionate fans, you are
  68.  very likely to find more people interested in obscure or hidden details
  69. @@ -47,34 +50,32 @@ that you can share.
  70.  
  71.  ## Resource gathering and creation
  72.  
  73. -Similar to researchers, you can also contribute with screenshots, icons
  74. -or other resources from the video game or TV show. Wikis not only need
  75. -the textual information, but also good visual materials to go next to
  76. -it.
  77. +Similar to researchers, you can also contribute screenshots, icons or
  78. +other resources from the video game or TV show. Wikis not only need the
  79. +textual information, but also good visual assets to accompany it.
  80.  
  81.  You can also go further by creating useful resources for other fans,
  82.  like diagrams, maps, audio recordings or even high-quality scans for
  83. -real life products. Many wikis already have tools to create interactive
  84. -maps, and most of the time you only need the map's image and to place
  85. -each one of the markers.
  86. +real-life products. Many wikis already have tools to create interactive
  87. +maps, and you often only need the map's image and to place the markers.
  88.  
  89.  ## Designers and artists
  90.  
  91. -Have you noticed that a lot of wikis look very similar to each other?
  92. -Even though wikis come with a pre-built appearance that is more than
  93. -enough to share the information with other fans, there's an entire world
  94. -of possibilities when it comes to customizing wikis. Because most wikis
  95. -are maintained by only a few people, and sometimes even a single person,
  96. -there is plenty of room for someone with design experience to make a
  97. -real difference in the wiki's appearance (visual identity, color
  98. +Have you noticed that a lot of wikis look similar to each other? Even
  99. +though wikis come with a pre-built appearance that is more than enough
  100. +to share the information with other fans, there's an entire world of
  101. +possibilities when it comes to customizing wikis. Because most wikis are
  102. +maintained by only a few people, and sometimes even a single person,
  103. +there is plenty of opportunity for someone with design experience to
  104. +make a real difference in a wiki's appearance (visual identity, color
  105.  palette, icons, page layouts, and a lot more you can help with).
  106.  
  107.  If you like designing or have a good eye for art, your skills might be
  108.  very welcome to improve how their pages look. For the most part, all you
  109.  need is some knowledge of [CSS](https://en.wikipedia.org/wiki/CSS), but
  110.  even if you have never heard of it, the community may already have
  111. -people who know how to make it and are only waiting for someone to help
  112. -them with a direction for a design.
  113. +people who know how to implement it and are only waiting for someone to
  114. +help provide creative direction.
  115.  
  116.  > [!TIP] Learn more about wiki design
  117.  > Watch out for an upcoming post about how are wikis designed and what
  118. @@ -84,13 +85,13 @@ them with a direction for a design.
  119.  ## Front-end developers
  120.  
  121.  Whether you know how to make designs or are just familiar with HTML and
  122. -CSS, you can help the wiki build their visual identity. Although you
  123. -won't have access to popular CSS frameworks, wikis can be highly
  124. -customized using plain CSS.
  125. +CSS, you can help shape a wiki's visual identity. Although you won't
  126. +have access to popular CSS frameworks, wikis can be highly customized
  127. +using plain CSS.
  128.  
  129.  You can bring a design to life, whether it comes from you or from the
  130. -community's design ideas. You can also make sure the wiki has reusable
  131. -and easy to maintain CSS, a consistent appearance across all pages, and
  132. +community's design ideas. You can also make sure a wiki has reusable and
  133. +easy-to-maintain CSS, a consistent appearance across all pages, and
  134.  designs that remain accessible on both desktop and mobile devices.
  135.  
  136.  ## Back-end developers
  137. @@ -98,9 +99,9 @@ designs that remain accessible on both desktop and mobile devices.
  138.  Wikis run software called
  139.  [MediaWiki](https://en.wikipedia.org/wiki/MediaWiki). In most wikis, you
  140.  won't have direct access to the code running on the servers, but
  141. -back-end developers are still very helpful for the community through
  142. -tools to assist with their endeavors, and advanced templates using
  143. -wikitext and Lua modules to present the information in pages.
  144. +back-end developers are still very helpful for the community by building
  145. +tools that make editing easier for other editors, and advanced templates
  146. +using wikitext and Lua modules to present the information in pages.
  147.  
  148.  Many wikis also have extensions that might be easier to understand and
  149.  unlock their full potential, such as database-like storage mechanisms
  150. @@ -111,17 +112,18 @@ through [Cargo](https://www.mediawiki.org/wiki/Extension:Cargo) or
  151.  
  152.  Wikis allow a high level of automation through the [MediaWiki Action
  153.  API](https://www.mediawiki.org/wiki/API:Main_Page). There are already
  154. -many libraries for most popular languages to write scripts that can help
  155. -the wiki with automated changes across pages.
  156. +libraries for most popular programming languages to write scripts that
  157. +can help a wiki with automated changes across pages.
  158.  
  159. -With this help, editors can spend more time improving content instead of
  160. -manually replacing the same word in hundreds of pages, one by one.
  161. +By automating repetitive tasks, editors can spend more time improving
  162. +content instead of manually replacing the same word in hundreds of
  163. +pages.
  164.  
  165.  > [!CAUTION] Beware of pitfalls
  166. -> Automation can be very tempting to some people, to the point where it
  167. -> actually makes work more difficult for editors. Try to always think from
  168. -> the perspective of the other community members and understand the wiki's
  169. -> needs before trying to over-automate things.
  170. +> Automation can be very tempting to some people, to the point where
  171. +> it actually makes work more difficult for editors. Try to always think
  172. +> from the perspective of the other community members and understand a
  173. +> wiki's needs before trying to over-automate things.
  174.  >
  175.  > Stay tuned for a future blog post about these pitfalls and some
  176.  > warning signs to watch.
  177. @@ -129,14 +131,18 @@ manually replacing the same word in hundreds of pages, one by one.
  178.  ## Organizers and coordinators
  179.  
  180.  Even though wikis are collaborative projects run by volunteers, they
  181. -need people who can coordinate the wiki's goals, content and ongoing
  182. -projects. Most wikis try to look as professional as they can, which
  183. -involves making sure pages look consistent in writing style, structure
  184. -and layout, as well as making sure other editors are collaborating with
  185. -the rest of the community rather than working alone and making decisions
  186. -on their own.
  187. -
  188. -Helping the wiki's direction does not mean giving everybody else orders,
  189. +need people who can coordinate a wiki's goals, content and ongoing
  190. +projects.
  191. +
  192. +Most wikis not only want to share information with other fans, but also
  193. +present it consistently across pages. This means agreeing on writing
  194. +style, page layouts, naming conventions, and how content should be
  195. +organized. Coordinators help to guide and focus those efforts while also
  196. +making sure contributors are collaborating with the rest of the
  197. +community rather than working alone and making decisions on their own,
  198. +pulling the wiki in different directions.
  199. +
  200. +Helping a wiki's direction does not mean giving everybody else orders,
  201.  but listening to the community and helping others find something they
  202.  can enjoy helping with, while still making sure that everybody's efforts
  203.  are appreciated and align with what the wiki is trying to become.
  204. @@ -144,7 +150,7 @@ are appreciated and align with what the wiki is trying to become.
  205.  ------------------------------------------------------------------------
  206.  
  207.  Any skill you have, from writing to design and from organizing to
  208. -programming, has a place where you can help the wiki and make the
  209. +programming, has a place where you can help a wiki and make the
  210.  community grow to welcome even more people.
  211.  
  212.  One of the best parts of helping a wiki is the nice people you will
  213. @@ -153,11 +159,14 @@ do. So the next time you notice a typo, or find a detail that is not
  214.  mentioned anywhere in a wiki, or think "someone should make this page
  215.  easier to understand", remember that someone can be you.
  216.  
  217. -You don't need permission to help.
  218. +You don't need permission to help. You can pick any page you know well,
  219. +click "Edit" and improve one sentence. That's how almost every editor
  220. +started, and also how every wiki grows.
  221.  
  222.  > [!NOTE] LLM Disclosure
  223. -> This blog post was entirely written by a person. However, an LLM
  224. -> was used to proofread and give feedback about the ideas and structure.
  225. ->
  226. +> This blog post was entirely written by a person. However, an LLM was
  227. +> used to proofread the text and provide feedback on its structure and
  228. +> ideas.
  229. +>
  230.  > You can find a comparison for the original version and the edited
  231.  > version at [this Github diff](https://google.com).
Advertisement
Add Comment
Please, Sign In to add comment