Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- @@ -1,16 +1,17 @@
- In a previous post, [Wikis need someone like
- -you](/posts/PnCibT-join-a-wiki), the intention was to introduce how
- -different roles and different skillsets can be incredibly helpful for
- -many wiki communities. The target for that post is the casual reader who
- -isn't much familiar with wikis, but it left an interesting idea in the
- -air of different ways to perceive wikis.
- -
- -Even though wikis have a small number of roles, it would be incorrect to
- -try to categorize a community by its members' user groups. Beyond the
- -surface, wikis aren't just composed of administrators, interface
- -administrators and permission administrators; instead, many communities
- -prefer to group their members by more useful categories: design,
- -templates, gadgets, automations, topic research, and so on.
- +you](/posts/PnCibT-join-a-wiki), the goal was to show how different
- +skills and responsibilities can be incredibly valuable for many wiki
- +communities. The target for that post is the casual reader who isn't
- +much familiar with wikis, but it left an interesting idea in the air of
- +different ways to perceive wikis.
- +
- +Although most wikis define only a handful of official user groups, it
- +would be misleading to describe a community solely through those
- +permissions. Beyond the surface, wikis aren't just composed of
- +administrators, interface administrators and permission administrators;
- +instead, many communities prefer to group their members by more useful
- +categories: design, templates, gadgets, automations, topic research, and
- +so on.
- If you have visited different wikis around, some of them even give names
- to those roles. Some wikis don't have designers, but instead they are
- @@ -19,40 +20,40 @@ technical users, they may have **Engineers**, **Inventors** or
- **Tinkerers**. I am not here to argue whether a role can be called one
- way or another, since this is a really endearing aspect of wikis.
- -Some communities may see themselves as town, cities or kingdoms. Even if
- -you are not a big fan of this kind of soft roleplay, just try to play
- +Some communities may see themselves as towns, cities, or kingdoms. Even
- +if you are not a big fan of this kind of soft roleplay, just try to play
- along and you may end up enjoying your time around those communities.
- ## Content roles
- One of the roles that I have found more often recently in wikis are
- -**Lorekeepers**. Maybe it's because video games are investing more
- -nowadays in lore than before, some wikis even need to have a dedicated
- -channel in their Discord servers for lore discussion and analysis.
- -Lorekeepers are around most of the time to moderate those discussions
- -and verify any findings before they are incorporated in an article,
- -since wikis usually want to keep speculation at a minimum.
- +**Lorekeepers**. Maybe it's because video games place a greater emphasis
- +on world-building and lore nowadays than before, some wikis even need to
- +have a dedicated channel in their Discord servers for lore discussion
- +and analysis. Lorekeepers are around most of the time to moderate those
- +discussions and verify any findings before they are incorporated in an
- +article, since wikis usually want to keep speculation at a minimum.
- Next, still in the Content department, you will sometimes find people
- -who help others in proofreading, correcting texts or just guiding them
- +who help others with proofreading, correcting texts or just guiding them
- about how to write or organize the information across the wiki. They are
- sometimes called **Curators**, but I have met wikis that went a bit more
- creative with names like **Archivists** or **Scholars**.
- A similar role that is not often found is what I have found some wikis
- -call **Cartographers**, who gives more care to how content is
- +call **Cartographers**, who pay closer attention to how content is
- interconnected and look for ways to help readers to navigate through it.
- They will be often looking for intuitive ways to group pages beyond the
- broader categories, usually through navbox or other navigational
- -templates; the best example are navigation templates to browse other
- -episodes from the same season in a TV show at the end of each episode's
- +templates; one good example are navigation templates to browse other
- +episodes from the same season in a TV show at the end of each episode
- pages; or abilities in a video game that share effects, sets or maybe
- are related in the lore.
- In video game wikis, there are often two groups of people that are
- closely related but have different work. When there is part of the video
- game's source code that can be extracted, **Researchers** or
- -**Dataminers** try to analyze and explore it to find mechanics and
- +**Dataminers** try to analyze and explore it to understand mechanics and
- explain bugs. On the other hand, **Testers** create specific scenarios
- to check how different parts of the game behave to find interactions or
- even bugs as well, especially when the video game offers a debug console
- @@ -60,13 +61,12 @@ or allows modding.
- Of course, you can't forget the **Writers**, who have the courage to
- create the pages and write any information they find, as well as
- -updating other pages related to make sure things stay in
- -synchronization.
- +updating related pages to keep information consistent.
- ## Design roles
- -Designers are a very broad group that encompass a variety of skills.
- -Starting with images, wikis often need logos, background, icons and
- +Designers are a broad group that encompasses a variety of skills.
- +Starting with images, wikis often need logos, backgrounds, icons and
- other UI elements; nowadays, I find more wikis making an amazing use of
- border images. This is where **Artists** shine, sometimes also called
- **Illustrators**.
- @@ -75,8 +75,8 @@ Just like wikis have content to be standardized when it comes to format,
- layout, and structure, design-wise elements should be consistent with
- each other, and keeping track of this "visual identity" is its own role,
- although wikis rarely have people focused on it and instead rely on all
- -others editors noticing differences. Very few wikis have a **Design
- -Directors**, **Design Leads** or **Visionaries** that makes sure the
- +other editors noticing differences. Very few wikis have a **Design
- +Directors**, **Design Leads** or **Visionaries** who make sure the
- interface, templates and gadgets look similar and make a consistent use
- of borders, rounded borders, colors, and typographies. They don't need
- to be the ones implementing all designs, but manage a design convention
- @@ -85,7 +85,7 @@ and oversee that the wiki follows it.
- Turning those design ideas into reality is usually the work of people
- who know how to use CSS. I haven't found many creative names for this
- responsibility, and some wikis directly call them **CSSers**. At a more
- -professional level, not only they add the styles necessary to make the
- +professional level, not only they write the styles necessary to make the
- wiki look like what the community wants, but also keep the stylesheets
- organized and easy to maintain.
- @@ -93,27 +93,29 @@ organized and easy to maintain.
- So far, we have explored the parts that readers would usually notice,
- but wikis have a more hidden part in the background that supports the
- -efforts of all other contributors. The "wiki back-end" encompasses all
- -work done in templates, Lua modules, gadgets, and automation tools. Many
- -of these roles rarely have a name in communities, and instead are known
- -as "the person who deals with code". In this section, I am going to call
- -them "Specialists", but would definitely love to learn about names used
- -in other wikis.
- +efforts of all other contributors. The technical side of a wiki includes
- +templates, Lua modules, gadgets, automation tools, and everything that
- +supports contributors behind the scenes.
- +
- +Many of these roles rarely have a name in communities, and instead are
- +known as "the person who deals with code". In this section, I am going
- +to call them "Specialists", but would definitely love to learn about
- +names used in other wikis.
- **Template Specialists** are the first type of technical user that joins
- -a wiki, since templates are one of the very first concept you learn in
- -wikis to make your editing efforts easier. When something needs a
- -special formatting, or typing a certain information becomes repetitive,
- -template specialists will often be quick to create a template that makes
- -the experience easier for editors. Not only will they introduce
- -infoboxes and navboxes, but other ways to organize information such as
- -cards, grids and list formattings.
- -
- -Although templates are very powerful and flexibles, there is a moment
- -where they may start to fall short or become difficult to maintain and
- -extend; **Lua Specialists** are the next group that participates in
- -template creation for things that are easier to implement in an actual
- -programming language.
- +a wiki, since templates are one of the first concepts you learn in wikis
- +to make your editing efforts easier. When something needs a special
- +formatting, or typing a certain information becomes repetitive, template
- +specialists will often be quick to create a template that makes the
- +experience easier for editors. Not only will they introduce infoboxes
- +and navboxes, but other ways to organize information such as cards,
- +grids and list layouts.
- +
- +Although templates are incredibly powerful and flexible, there is a
- +moment where they may start to fall short or become difficult to
- +maintain and extend; **Lua Specialists** are the next group that
- +participates in template creation for things that are easier to
- +implement in an actual programming language.
- Moving on from templates, wikis may have two types of **JavaScript
- Specialists**: people that write scripts to improve the way wikis are
- @@ -123,17 +125,17 @@ adding or improving features like search methods for categories of
- pages, buttons that change how information is presented, and even
- calculators.
- -The other type of JavaScript Specialist deals more with in-wiki editor
- -tools through gadgets, maybe to update pages, help with housekeeping,
- -have better access to MediaWiki features, and many other ways that help
- -the other community members with what they're doing.
- +Other JavaScript Specialists focus more with in-wiki editor tools
- +through gadgets, maybe to update pages, help with housekeeping, have
- +better access to MediaWiki features, and many other ways that help the
- +other community members with what they're doing.
- There is also a broad group that can't be easily split into more
- detailed groups without getting too specific, which are **Extension
- Specialists**, although **Data Specialists** may be a slightly better
- -name. Their focus is usually to make it easier to keep information in
- -sync across pages through extensions like DynamicPageLists, Cargo, or
- -Bucket.
- +name. Their focus is usually to make it easier to keep information
- +synchronized across pages through extensions like DynamicPageLists,
- +Cargo, or Bucket.
- Finally, we have **Bot Specialists** or **Automation Specialists**. Most
- of them start with tools like AutoWikiBrowser or Pywikibot to run easy
- @@ -147,18 +149,19 @@ analyzing edits as they are done.
- If you participate in a wiki, you may have realized that you fulfill
- many of the mentioned roles yourself, and even other roles that were not
- mentioned. This is normal, there is a lot of overlap between them and
- -community members rarely limit themselves to only one when they might be
- -interested in different forms to participate; additionally, some wikis
- -may not have many members and instead will need to wear many hats.
- +contributors rarely limit themselves to just one when they might be
- +interested in different forms to participate; additionally, smaller
- +wikis often rely on contributors wearing several hats at once.
- You can think of them more like responsibilities or things that a wiki
- may need instead of individual roles. This can help you to explore other
- ways you can help a wiki, even if it doesn't relate as much with what
- -you currently help with; many people find new interests in trying things
- -in a wiki, that's how a lot of technical users and designers learned
- -they enjoyed filling those roles. You don't need to be an expert to start any role, and wikis
- +you currently help with; many people discover entirely new interests
- +simply by trying something outside their comfort zone on a wiki; that's
- +how a lot of technical users and designers learned they enjoyed filling
- +those roles. You don't need to be an expert to start any role, and wikis
- offer a great learning experience for different skills.
- -*Do you know any wikis that gives creative names to these roles? Or any
- +*Do you know any wikis that give creative names to these roles? Or any
- other roles in wikis? What roles do you feel comfortable in filling?
- Would love to hear about that.*
Add Comment
Please, Sign In to add comment