Read below for more info on what the team has worked on for this revamp!
Better User Experience and Infrastructure:
New clean and clearer UX design that is aligned with the Waze updated brand. It features new templates for all wiki pages that will enable users to easily find what they’re looking for, navigating through the extensive content Wazeopedia offers with ease.
Communities can decide how their Main Page will look and which sections will be highlighted. You can group articles from different categories to be under one section and give tags to articles.
App Launcher was added and it will enable users to easily reach the WME or the Waze Forum.
Infrastructure Improvements and version upgrade.
Better mobile support.
Content:
Standatzion of the content with new templates and forms the community can edit.
Full Content migration, We didn’t remove any content, so everything from the old wiki should appear.
Revamped Global Wiki:
The current content (which is copied from the US wiki) will be redirected to the US wiki page.
Adding Waze Staff Content: Wazer to Wazer, Social Media Hub, and the Waze Meetup Site have been integrated into the Global page. This will enable users to easily find the information they are looking for about Waze Communities.
Wazeopedia Help Center:
On each page at the top you will see a question mark that will take you to the Help Center.
You can find articles on different topics about Wazeopedia (permissions, how to edit, and more).
How to edit the new Wazeopedia page?
Main page: You can decide how the page will look and which sections and images will be displayed.
Any user can edit the local wikis after logging in with their Waze username.
A few local wikis are restricted so only Wazeopedia Local Champs can edit them. For example, you can see here the list of authorized Local Champs in the UK.
Want to better understand Wazeopedia permissions? Read this article.
This was a misunderstanding. I meant the last field in the form (which was the second of the two fields for submitting a question for the office hour - so you had to fill in a question because it was mandatory). But this was fixed in the meantime.
uploading images is currently only available on the global Wazeopedia. Is this also planned after the beta phase or will it be possible to upload images from the local Wazeopedia?
I find it awkward having to switch between uploads when creating an article.
I was curious if the team could publish the list of bugs/issues that have been submitted from the field to the dev team so we know what has already been reported and we don’t waste time having 50 people submit the same bugs over and over.
.
Is there a way you can provide a method for us to add screenshots to our reports? Currently, the reporter has to provide a method to store the image online somewhere and then include a link in the report.
.
Can we have the Dev team look at the CSS file in the current Wazeopedia and copy the key formatting content over to the new Beta? There appears to be many things that are different between the two files that are not intentional to be changed in the new Beta, but are instead just using the default formatting. We went through a lot of effort in the original Wazeopedia deployment to get the CSS fine tuned and this beta has undone a lot of things that mess up many of our templates in use today.
I noticed FasterinoSpeederino reported a similar problem to something I was seeing. If I had an edit window open for too long without saving the data, I would get the error when saving that the session data was too old (or something like that). I would have to refresh the page and edit the page again. This is not something we had a problem with on the current Wazeopedia sessions.
I would like to give further information in the feedback sheet as requested but it seems that I only have read access although I use the published links.
I’m not even able to comment.
When you comment in the last column Shira noted, it might be helpful to add your name in parenthisis with the date so we can add multiple comments over time and know when someone added new information. You can see what I have been doing in the other entries as an example.
You are very welcome, Shira. I have a lot of years invested in this Wiki and I would hate to lose any of it.
Also, should we start a new folder for Beta feedback among the editors for temporary work around and feedback consolidation on certain changes for how we would adapt to it? For example, we could start a thread on how to work around the current Save Error problem with loss of session data. We could also talk about the issues we are running into for tables. In both cases, we already have bug reports, but it might be helpful for us reviewers to talk about some of the issues we are seeing. For anyone else in this thread, I assume anyone can access my deck I have been consolidating the issues I have found. It might help testers know what has already been reported if those people don’t want to add those issues again.
