MissCheetah isn’t out of touch, I simply asked her to let me try to make the guide for her. At the time, she didn’t even know I was going to do more than just text. She figured I was going to do some “fancy” text formatting or something like that. I kept the guide’s true content a secret until I was able to finalize it and get it posted.
The amount of work wasn’t trivial. Far from it. I’d had some bare-bones HTML learning under my belt, but nothing that prepared me for what I had to learn. You see, this forum’s software doesn’t use straight HTML 4 or straight HTML 5, it uses a hybrid amalgomation of the two, and which syntax is required for which function is totally arbitrary. There is no pattern to it at all other than Blizzard chose what they did for…reasons.
As I was unable to use a straight version of either HTML 4 or 5, I had to learn what worked and what didn’t by trial and error. And as I hadn’t dealt with even HTML 4 before (I learned my HTML back in the Netscape Navigator days using WYSIWYG editors), I also had to learn both versions of HTML syntax.
The first version of the guide everyone got to see took me well over 80 hours of trial and error and learning new code. And because Discourse form software prevents one from mixing HTML with proper markdown code (e.g. BBCode), I had to do it entirely in HTML, right down to image linking and resizing. All of that was done by hand. No editors other than what this forum provides. I used this forum software editor’s dual window mode to show a live preview of what I was working on at the time. It works great for smaller chunks of code, but the entirety of the guide loaded at once breaks the window and requires moving both sides by hand to line up with each other so I can see what my code did while having it on my screen. Any changes causes the preview window to close all flyouts and forces me to realign the two sides yet again.
Right now the entirety of the cosmetic guide is 33 pages of hand typed code. I did this because I wanted to. It was both a learning opportunity and a way to give something nice back to the Diablo 3 community. So I asked MissCheetah for her original guide text and went from there. Since this forum was capable of more than mere text and clickable links, I thought I’d try to give players a real cosmetic guide that let them see what they were farming for before they farmed for it, all in one convenient location.
I think it would have been a bit much asking MissCheetah to try and learn the whacko HTML code required for a visual guide on the new forum software. So far the best I’ve seen for other guides is a bit of fancy text formatting and maybe a table of contents with anchors to link to, and a few pictures for demonstration. It’s been a learning process for every guide writer. Not like we had much of a choice given the weird way HTML 4 and 5 had to be mixed together in order to make things work right.
So MissCheetah isn’t out of touch, her area of expertise is simply not (currently) in in-depth forum coding. Her expertise lies with helping others get the correct information whenever possible, along with some tech support for the more common issues. My area of expertise is in-depth tech support. The HTML coding was just a bonus for taking on the guide project. MissCheetah runs circles around me blindfolded when it comes to informational support. And you won’t find a more neutral person around to do it either. Being helpful while maintaining neutrality actually makes her more in touch, not less. You’ll be hard pressed to find someone more in touch with the players here than she is.
Don’t mistake style for intent. I may know the forum code better, but that doesn’t make me more in touch by any stretch of the imagination. MissCheetah, on the other hand, interacts with the community more than most others here, on virtually every issue we’ve got. And she interacts with players on each side of a given issue and actively listens to what we have to say. She can’t do anything about what we want or don’t want, but by no means does that make her out of touch.
There’s no TL;DR here. Sorry, not sorry.