Learning the code and playing with it is a good first step in learning how to code anything else. While it is much simpler than any other code out there, it is safe to say it is just as finicky. When setting up anything on a WikiHow using the advanced editing, it was imperative to take notice and really understand where things where to go, because if there were even one space in the wrong part of the code, it could have messed up the entire page.
More often than not, people who are interested in roleplay take a whack at it when they are either really new to it, have some experience in other kinds of roleplay environments (i.e. forums or Dungeons and Dragons), but it is never really quite the same as online roleplaying.
Imaging a way to explain online roleplaying to those who may not have already done any was rather odd. Teaching someone how to roleplay is not easy, and people kind of pick it up and enjoy it, or they do not. More than anything, it depends on first experiences, friends, interests and arguably the chosen setting. If these factors are not present, even the WikiHow could possibly not save someone from having a bad time.
Narrowing the topic down to Final Fantasy XIV was likely a good choice, simply because it eliminates at least one of those tough factors one chooses when thinking about roleplaying online. The good news is that the WikiHow article can still be applied to other games. It is a flexible guide for someone who really wants to get their feet wet in the world of roleplay.
One of the things mentioned in the WikiHow, and likely the most important, is a love of writing and some basic skills in English. For the most part, roleplayers love what they do. They love writing, the love the craft, the story, all of it from head to toe--or in this case beginning to end. It is so important to have a love of what is going on in roleplay. A mass of people have come together to create an ever growing world that changes as the developers change the game, and keep their own personal stories rolling, even when the credits on the main story have finished rolling. That, quite honestly, is amazing.
Most of the photos used were screenshots of the in-game characters, landscape, and loading screen. Since the topic was narrowed down, it became a much easier thing to photograph. Of course, there are some actual "real life" photos.
Part of roleplaying, as explained in the WikiHow, is knowing when to take a break and enjoy real life, as much as virtual life. Eating, drinking, stretching, and social interaction are very important to keeping roleplay alive. If one person roleplays all day everyday, eventually they will get completely burned out!
The WikiHow is all based on personal experiences and over 8 years of roleplaying both in video games and elsewhere. For someone with that many years under their belt, the passion just kind of flows out like a river, and that goes for anything. The writer, as I am sure is the case with many other WikiHows, has a long relationship and history with their how-to, even for something as mundane as "How to find a job" that contributor must have had some serious bad luck, or a lot of experience with job hunting. Either way, it was likely good in the long run!
The WikiHow creation experience gives a window into finding out how passionate one really is when talking about something they love to do, know how to do, and just want to share with the world. It is amazing how passionate one can get when they don't even realize it, unless it happens to come about when you're just trying to give someone some tips.
The problem, perhaps, with WikiHow is worrying about stepping on legal-toes. That is, copyrights and the like can sometimes prevent a passion from becoming a how-to in the WikiHow-universe. There are a lot of "to whom does this belong" and "what-ifs" that pop up when using images, or thinking up an original topic. Still, it comes with the passion, there are tons of people who may want to or may be writing the same topic at any given moment.
Brainstorming with others really helps get that out of the way. Having people critique ideas and say which they think is truly original and which they think could benefit a lot of people is a really engaging way to get the "is it already done"-phase out of the way. Furthermore, having more than one solid idea--brilliant! This should go without saying, of course, but backup ideas are a good idea. Always know that there is someone out there who thinks similarly to another, sometimes originality clashes. Three ideas is a good start, but five would have given a bit more weight and thought to choosing a final topic.
Overall, while the WikiHow creation process can be tedious, daunting, and perhaps even a bit too straightforward, it was also rather relaxing, and enriching. For someone, reading a WikiHow can really change their life for the better, even if it's just a tiny nudge in one direction or another. For others, there is entertainment value.
For the contributors, there is a content sigh, knowing that their work is done, it is released to the world, for all to enjoy and take a great lesson from.
A salute to all WikiHow contributors who have given the people of the internet something to look forward to, and a salute to the people of the internet who have given those contributors a few nice page views every now and then.

