I've seen this guide has changed a lot since when it was Wii.guide.
My main issue with it is that the pages are bloated, loaded with wordy content. While it's good information, I think that since the Wii is often modded by the younger demographic, they are going to find the pages to be too long, and then might skip steps.
If I were to sell a book for Wii modding (which I'm not), I'm sure there would be a Table of Contents, and a decent layout so people can find information in the book. I can't say that about this guide, it needs some structure.
For example, this page is an example. It explains how to install themes for the Wii Menu. However, directly below that is a quick tutorial on how to install themes for WiiFlow Lite. Someone who isn't paying attention might just think that's somehow related to installing stuff for the Wii Menu. This issue is present on the page for bricks, WiiConnect24, Nintendo WFC pages - it's not the easiest to discern that each are subsections.
Not only that, but the buttons to choose a path to generate a CSM say "Any", "Wii", or "vWii". There isn't even a note saying to pick an option or which one is recommended.
My advice is:
- Break these pages up into smaller pages. It will not only make reading the page easier on the eyes, it will look tidier.
- Create a style guide. Adhere to grammatical rules, designs for pages, etc. Maybe some code can be written to see if incoming PRs match said rules. Currently, the grammar and wording used across the guide are not cohesive, but making some guidelines will help develop a sense of a standard.
- KISS - Keep it simple stupid. You can strike some kind of balance where the guide is very informative but easy to understand for the people that are not tech savvy. Try not to use terms on each page that some might not be familiar with.
- Ask yourself why you'd care to read anything Larsen has to say. Obviously this is a joke, but seriously... I've been less social in the Wii community for the past year... but I still like working on small Wii related projects silently. I also like to give advice out of passion and how much I learned from the Wii over the years, regardless of what people think of me
I've seen this guide has changed a lot since when it was Wii.guide.
My main issue with it is that the pages are bloated, loaded with wordy content. While it's good information, I think that since the Wii is often modded by the younger demographic, they are going to find the pages to be too long, and then might skip steps.
If I were to sell a book for Wii modding (which I'm not), I'm sure there would be a Table of Contents, and a decent layout so people can find information in the book. I can't say that about this guide, it needs some structure.
For example, this page is an example. It explains how to install themes for the Wii Menu. However, directly below that is a quick tutorial on how to install themes for WiiFlow Lite. Someone who isn't paying attention might just think that's somehow related to installing stuff for the Wii Menu. This issue is present on the page for bricks, WiiConnect24, Nintendo WFC pages - it's not the easiest to discern that each are subsections.
Not only that, but the buttons to choose a path to generate a CSM say "Any", "Wii", or "vWii". There isn't even a note saying to pick an option or which one is recommended.
My advice is: