x
Did this guide help you? If so please give them a vote or leave a comment.
You can even win prizes by doing so!
Vote
Comment
I liked this Guide
I didn't like this Guide
Thank You!
Your votes and comments encourage our guide authors to continue
creating helpful guides for the League of Legends community.
These are going to be the things that we are going to be looking through ideally with this review.
STRUCTURE: This is basically how you code, place and use code from a tidy and neat viewpoint.
CONSISTENCY: Basically how often you switch things up. Some parts might be a mess and others great.
INCLUDINGS: These are things that could be added like Runes, Items, Matchups or entire sections.
MY CONCERNS: Things that I find not really interesting to apply to a guide or just filler.
This section of ones guide as you know should be both detailed and easy to read without being too overwhelming.
You have notes on your runes and your items, it's straight forward, simple and isn't too much of an overwhelming sight like some people have in their guides. Though one thing I would try to add if I were in your shoes, is a way to make this section tidier. Instead of having Plated Steelcaps and Mercury's Treads multiple times in multiple builds.
Consider something simplistic and easy to understand, as most people will simply copy paste (in order as shown on your guide) the items, rather than rationally understanding why (this) and (that) works better in any given situation.
Overall, this section is okay on the information provided. It'll be up to you if you decide to make those changes.
As you may know this next section is the "cheat sheet" portion of the guide right below items and runes.
You have a lot of text here. Which is good to have, but all of the [EXTREME] this [IDEAL] that.
It's unnecessary due to the fact that the guide will already give that highlight right above it, and in the section they are clicking on. Might want to manually remove it, as it just becomes filler text.
Severely lacking.
I understand, not everyone has enough time to run around and learn how to use BBCODE. But it would do you a world of good if you were to take a gander at any of the guides located HERE and HERE!
Once you get a handle for how a guide should "Look" take a stab at coding up some at the very least, basic tables or columns to make things look neat, then fill out some sections with video references and more in-depth information.
Put some effort in your body text, which comes in the form of BBCODE, along with fixing and tidying up some of the cheatsheet section, and you'll have yourself a really decent looking guide.
Don't punch me! ~Cat