svache wrote:I suggest a change back to what it was, a similar design as in all wiki's. The current version looks like, to say it very blunt, as something a 4 year old would've done.
Personally I really don't see why it had to be changed.
I'd really suggest you read http://www.waze.com/wiki/index.php/Talk:Main_Page
I'd seriously be interested in your response to the points there. As to why it had to be changed: It was unhelpful, unscalable to an increase in countries, languages and activities, unstructured, incomplete, undirected, unclear, inconsistent, unfriendly. And not providing any support or guidance to new users. There were other problems too. But hey, if you think it was better, revert it back.
As to a similar design to all wikis. Have a look at http://en.wikipedia.org
- all this is covered in the discussion page, but a case can be made - I'm trying to make it, that a front page can be exceptional.
Let me start by saying that it is not the actual information that I didn't like, I agree with your points regarding to the information but that was not my point, it was the looks, the design.
I think, before doing anything with such an impact, you should have opened a thread on the forum to discuss it. Not a discussion on the Wiki as much less people read it (from a quick view on that page you pointed out, I noticed only one person besides you commented there). You get a better reach and response in the forums (just look at this thread for example). The current changes, in my opinion, are similar to working for Waze and changing the webdesign drastically without any colleague knowing, you're bound to get questions when you do that (offtopic: I wouldn't mind to see some professional changes to the website itself though, but that's more from my view as webdeveloper).
Again, I was not after the information on the Wiki, just the looks.
As for both links that you pointed out (the ones in the quote above, not those further down), I like the German version better. The colors make it look a bit cluttered, the German version is more unified and peaceful. Right now it is as if you want to reinvent the wheel, but like Robin also said on the 'talk page', the original way the content mechanism works, works really well.
There's also said something about languages and such. There are a couple of MediaWiki language extensions that work really well with this.
One other problem you might be facing here is the width of the page here. Maybe it would be an idea for Waze to actively break out of the set widths in their Wiki and make it variable to screenwidth (like the original Wiki's do). The current width of the wiki (and I mean the main column, not the navigation pane) is about 745 pixels width, which is just too small for multiple columns with the current font height.
If Waze changes the widths of the Wiki, preferably variable to screensize, then you can easily make a two-column lay-out. But right now, I wouldn't do it as it makes it look a bit unprofessional and cluttered.
To be honest, I disagree with you here. The subheadings are actually a great way to quickly find what you need. The less clicks a user has to do, the better the user experience. I might change my view when the list becomes very very long, but right now it doesn't show too many subheaders.
But, now we're on that issue anyways, I'd like to add that the navigation pane on the side is being used too little. The main information should basically be there. When someone is on a sub-subarticle, they shouldn't have to go back all the way to the main page to select another topic and to click their way from there. If you take those 6 main headers, why not put them in the sidebar so people don't have to keep clicking between the articles and mainpage?
As for the discussion further down the topic, putting people off or not with the known issues and such. I think it is a good idea to warn people that Waze is still pretty much learning and that there are known issues. However, I also think we should not put people off. To be honest, in my personal case, I would never have started with Waze if I knew all the known issues beforehand. I would've gone for a different navigation app (I actually still don't use Waze that much for navigation, but more for the social aspect. If I need directions, I rather use my standalone nav device or the Google app since I changed to Android. Waze still cannot be trusted fully). I think it is important to find a balance where we inform people about all the issues, but not as far as to where they're put off to even try Waze. If they want to go deeper into that information, they can always look on different pages within the Wiki.
Also, don't forget that even if the front page of the Wiki shows nothing but known issues, even with big bold letters, you will still see people writing those things in the forums as lots of them don't even bother to check the Wiki. The problem starts also, amongst other things, with the support page itself, it shows little support options. When you then read the technical FAQ, you find only standard information and I can imagine that many users start to think at that point 'never mind the wiki, I'll skip through to the forums'. Also, just look at the forums, many questions have been asked about the same, and even the same questions and such pop up in the same threads. Many people don't bother to read before they post and that is something that cannot be changed easily because it needs a change of themselves.
As for people leaving road recording on, I even see experienced users, and sometimes even area managers do that. It should automatically be turned off when someone exits the Waze app, that way people cannot accidentally leave it on and it would avoid some of the problems. But like you said, it wouldn't hurt to actually inform them about it.
btw, my apologies for the long post