Guest User

Make a town

a guest
Jul 9th, 2026
27
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
Diff 12.88 KB | None | 0 0
  1. @@ -1,16 +1,17 @@
  2.  In a previous post, [Wikis need someone like
  3. -you](/posts/PnCibT-join-a-wiki), the intention was to introduce how
  4. -different roles and different skillsets can be incredibly helpful for
  5. -many wiki communities. The target for that post is the casual reader who
  6. -isn't much familiar with wikis, but it left an interesting idea in the
  7. -air of different ways to perceive wikis.
  8. -
  9. -Even though wikis have a small number of roles, it would be incorrect to
  10. -try to categorize a community by its members' user groups. Beyond the
  11. -surface, wikis aren't just composed of administrators, interface
  12. -administrators and permission administrators; instead, many communities
  13. -prefer to group their members by more useful categories: design,
  14. -templates, gadgets, automations, topic research, and so on.
  15. +you](/posts/PnCibT-join-a-wiki), the goal was to show how different
  16. +skills and responsibilities can be incredibly valuable for many wiki
  17. +communities. The target for that post is the casual reader who isn't
  18. +much familiar with wikis, but it left an interesting idea in the air of
  19. +different ways to perceive wikis.
  20. +
  21. +Although most wikis define only a handful of official user groups, it
  22. +would be misleading to describe a community solely through those
  23. +permissions. Beyond the surface, wikis aren't just composed of
  24. +administrators, interface administrators and permission administrators;
  25. +instead, many communities prefer to group their members by more useful
  26. +categories: design, templates, gadgets, automations, topic research, and
  27. +so on.
  28.  
  29.  If you have visited different wikis around, some of them even give names
  30.  to those roles. Some wikis don't have designers, but instead they are
  31. @@ -19,40 +20,40 @@ technical users, they may have **Engineers**, **Inventors** or
  32.  **Tinkerers**. I am not here to argue whether a role can be called one
  33.  way or another, since this is a really endearing aspect of wikis.
  34.  
  35. -Some communities may see themselves as town, cities or kingdoms. Even if
  36. -you are not a big fan of this kind of soft roleplay, just try to play
  37. +Some communities may see themselves as towns, cities, or kingdoms. Even
  38. +if you are not a big fan of this kind of soft roleplay, just try to play
  39.  along and you may end up enjoying your time around those communities.
  40.  
  41.  ## Content roles
  42.  
  43.  One of the roles that I have found more often recently in wikis are
  44. -**Lorekeepers**. Maybe it's because video games are investing more
  45. -nowadays in lore than before, some wikis even need to have a dedicated
  46. -channel in their Discord servers for lore discussion and analysis.
  47. -Lorekeepers are around most of the time to moderate those discussions
  48. -and verify any findings before they are incorporated in an article,
  49. -since wikis usually want to keep speculation at a minimum.
  50. +**Lorekeepers**. Maybe it's because video games place a greater emphasis
  51. +on world-building and lore nowadays than before, some wikis even need to
  52. +have a dedicated channel in their Discord servers for lore discussion
  53. +and analysis. Lorekeepers are around most of the time to moderate those
  54. +discussions and verify any findings before they are incorporated in an
  55. +article, since wikis usually want to keep speculation at a minimum.
  56.  
  57.  Next, still in the Content department, you will sometimes find people
  58. -who help others in proofreading, correcting texts or just guiding them
  59. +who help others with proofreading, correcting texts or just guiding them
  60.  about how to write or organize the information across the wiki. They are
  61.  sometimes called **Curators**, but I have met wikis that went a bit more
  62.  creative with names like **Archivists** or **Scholars**.
  63.  
  64.  A similar role that is not often found is what I have found some wikis
  65. -call **Cartographers**, who gives more care to how content is
  66. +call **Cartographers**, who pay closer attention to how content is
  67.  interconnected and look for ways to help readers to navigate through it.
  68.  They will be often looking for intuitive ways to group pages beyond the
  69.  broader categories, usually through navbox or other navigational
  70. -templates; the best example are navigation templates to browse other
  71. -episodes from the same season in a TV show at the end of each episode's
  72. +templates; one good example are navigation templates to browse other
  73. +episodes from the same season in a TV show at the end of each episode
  74.  pages; or abilities in a video game that share effects, sets or maybe
  75.  are related in the lore.
  76.  
  77.  In video game wikis, there are often two groups of people that are
  78.  closely related but have different work. When there is part of the video
  79.  game's source code that can be extracted, **Researchers** or
  80. -**Dataminers** try to analyze and explore it to find mechanics and
  81. +**Dataminers** try to analyze and explore it to understand mechanics and
  82.  explain bugs. On the other hand, **Testers** create specific scenarios
  83.  to check how different parts of the game behave to find interactions or
  84.  even bugs as well, especially when the video game offers a debug console
  85. @@ -60,13 +61,12 @@ or allows modding.
  86.  
  87.  Of course, you can't forget the **Writers**, who have the courage to
  88.  create the pages and write any information they find, as well as
  89. -updating other pages related to make sure things stay in
  90. -synchronization.
  91. +updating related pages to keep information consistent.
  92.  
  93.  ## Design roles
  94.  
  95. -Designers are a very broad group that encompass a variety of skills.
  96. -Starting with images, wikis often need logos, background, icons and
  97. +Designers are a broad group that encompasses a variety of skills.
  98. +Starting with images, wikis often need logos, backgrounds, icons and
  99.  other UI elements; nowadays, I find more wikis making an amazing use of
  100.  border images. This is where **Artists** shine, sometimes also called
  101.  **Illustrators**.
  102. @@ -75,8 +75,8 @@ Just like wikis have content to be standardized when it comes to format,
  103.  layout, and structure, design-wise elements should be consistent with
  104.  each other, and keeping track of this "visual identity" is its own role,
  105.  although wikis rarely have people focused on it and instead rely on all
  106. -others editors noticing differences. Very few wikis have a **Design
  107. -Directors**, **Design Leads** or **Visionaries** that makes sure the
  108. +other editors noticing differences. Very few wikis have a **Design
  109. +Directors**, **Design Leads** or **Visionaries** who make sure the
  110.  interface, templates and gadgets look similar and make a consistent use
  111.  of borders, rounded borders, colors, and typographies. They don't need
  112.  to be the ones implementing all designs, but manage a design convention
  113. @@ -85,7 +85,7 @@ and oversee that the wiki follows it.
  114.  Turning those design ideas into reality is usually the work of people
  115.  who know how to use CSS. I haven't found many creative names for this
  116.  responsibility, and some wikis directly call them **CSSers**. At a more
  117. -professional level, not only they add the styles necessary to make the
  118. +professional level, not only they write the styles necessary to make the
  119.  wiki look like what the community wants, but also keep the stylesheets
  120.  organized and easy to maintain.
  121.  
  122. @@ -93,27 +93,29 @@ organized and easy to maintain.
  123.  
  124.  So far, we have explored the parts that readers would usually notice,
  125.  but wikis have a more hidden part in the background that supports the
  126. -efforts of all other contributors. The "wiki back-end" encompasses all
  127. -work done in templates, Lua modules, gadgets, and automation tools. Many
  128. -of these roles rarely have a name in communities, and instead are known
  129. -as "the person who deals with code". In this section, I am going to call
  130. -them "Specialists", but would definitely love to learn about names used
  131. -in other wikis.
  132. +efforts of all other contributors. The technical side of a wiki includes
  133. +templates, Lua modules, gadgets, automation tools, and everything that
  134. +supports contributors behind the scenes.
  135. +
  136. +Many of these roles rarely have a name in communities, and instead are
  137. +known as "the person who deals with code". In this section, I am going
  138. +to call them "Specialists", but would definitely love to learn about
  139. +names used in other wikis.
  140.  
  141.  **Template Specialists** are the first type of technical user that joins
  142. -a wiki, since templates are one of the very first concept you learn in
  143. -wikis to make your editing efforts easier. When something needs a
  144. -special formatting, or typing a certain information becomes repetitive,
  145. -template specialists will often be quick to create a template that makes
  146. -the experience easier for editors. Not only will they introduce
  147. -infoboxes and navboxes, but other ways to organize information such as
  148. -cards, grids and list formattings.
  149. -
  150. -Although templates are very powerful and flexibles, there is a moment
  151. -where they may start to fall short or become difficult to maintain and
  152. -extend; **Lua Specialists** are the next group that participates in
  153. -template creation for things that are easier to implement in an actual
  154. -programming language.
  155. +a wiki, since templates are one of the first concepts you learn in wikis
  156. +to make your editing efforts easier. When something needs a special
  157. +formatting, or typing a certain information becomes repetitive, template
  158. +specialists will often be quick to create a template that makes the
  159. +experience easier for editors. Not only will they introduce infoboxes
  160. +and navboxes, but other ways to organize information such as cards,
  161. +grids and list layouts.
  162. +
  163. +Although templates are incredibly powerful and flexible, there is a
  164. +moment where they may start to fall short or become difficult to
  165. +maintain and extend; **Lua Specialists** are the next group that
  166. +participates in template creation for things that are easier to
  167. +implement in an actual programming language.
  168.  
  169.  Moving on from templates, wikis may have two types of **JavaScript
  170.  Specialists**: people that write scripts to improve the way wikis are
  171. @@ -123,17 +125,17 @@ adding or improving features like search methods for categories of
  172.  pages, buttons that change how information is presented, and even
  173.  calculators.
  174.  
  175. -The other type of JavaScript Specialist deals more with in-wiki editor
  176. -tools through gadgets, maybe to update pages, help with housekeeping,
  177. -have better access to MediaWiki features, and many other ways that help
  178. -the other community members with what they're doing.
  179. +Other JavaScript Specialists focus more with in-wiki editor tools
  180. +through gadgets, maybe to update pages, help with housekeeping, have
  181. +better access to MediaWiki features, and many other ways that help the
  182. +other community members with what they're doing.
  183.  
  184.  There is also a broad group that can't be easily split into more
  185.  detailed groups without getting too specific, which are **Extension
  186.  Specialists**, although **Data Specialists** may be a slightly better
  187. -name. Their focus is usually to make it easier to keep information in
  188. -sync across pages through extensions like DynamicPageLists, Cargo, or
  189. -Bucket.
  190. +name. Their focus is usually to make it easier to keep information
  191. +synchronized across pages through extensions like DynamicPageLists,
  192. +Cargo, or Bucket.
  193.  
  194.  Finally, we have **Bot Specialists** or **Automation Specialists**. Most
  195.  of them start with tools like AutoWikiBrowser or Pywikibot to run easy
  196. @@ -147,18 +149,19 @@ analyzing edits as they are done.
  197.  If you participate in a wiki, you may have realized that you fulfill
  198.  many of the mentioned roles yourself, and even other roles that were not
  199.  mentioned. This is normal, there is a lot of overlap between them and
  200. -community members rarely limit themselves to only one when they might be
  201. -interested in different forms to participate; additionally, some wikis
  202. -may not have many members and instead will need to wear many hats.
  203. +contributors rarely limit themselves to just one when they might be
  204. +interested in different forms to participate; additionally, smaller
  205. +wikis often rely on contributors wearing several hats at once.
  206.  
  207.  You can think of them more like responsibilities or things that a wiki
  208.  may need instead of individual roles. This can help you to explore other
  209.  ways you can help a wiki, even if it doesn't relate as much with what
  210. -you currently help with; many people find new interests in trying things
  211. -in a wiki, that's how a lot of technical users and designers learned
  212. -they enjoyed filling those roles. You don't need to be an expert to start any role, and wikis
  213. +you currently help with; many people discover entirely new interests
  214. +simply by trying something outside their comfort zone on a wiki; that's
  215. +how a lot of technical users and designers learned they enjoyed filling
  216. +those roles. You don't need to be an expert to start any role, and wikis
  217.  offer a great learning experience for different skills.
  218.  
  219. -*Do you know any wikis that gives creative names to these roles? Or any
  220. +*Do you know any wikis that give creative names to these roles? Or any
  221.  other roles in wikis? What roles do you feel comfortable in filling?
  222.  Would love to hear about that.*
  223.  
Add Comment
Please, Sign In to add comment