Wazeopedia Revamp in Beta - Share Your Feedback!

Map Editors Community Wazeopedia Discussions
21

Sound great @kentsmith9 !

Feel free to start a new thread and link to the relevant slide if there is and we can discuss the topic together.

I will update that the developers are working on the open bugs and Hannah and I are updating the Community bugs sheet-shared with the community accordantly.

Thank you all and have a wonderful day!

Shira

22

@shirapashu,

I think we should create a sub forum like “Wazeopedia 2022 Beta Discussions” for these posts to prevent confusion about issues that would not be seen in the current WP.

If you agree that would be best, I don’t have admin rights in the new forum, so you can either create the sub forum on your side or add me back to the admin list again. :wink:

23

(This post has been copied/moved to the beta subform https://www.waze.com/forum/viewtopic.php?t=356099)

@Shira,

I have a major concern with a core change in the new beta I will articulate here. I have entered three or four bugs already on elements around tables that I believe are driven from this one element in the revamp.

Problem statement

I presume the revamp of Wazeopedia is driven by the desire to change the look and feel of Wazeopedia and that includes how visual tables look on the page. However,
tables can be used for both visual presentation of data and also for invisible positioning controls. MediaWiki defines these positional uses of tables and we have used that mechanism for a large percentage of the pages in use today.

The new beta has changes to the core CSS table functions that affect a vast majority of the Wiki in a negative way. These changes appear to completely restrict some of the variables on tables to the point that they cannot be overridden by editors to meet their needs for positional, non-visual table use.

Recommendation

  • Have the dev team present the core desired visual table for the new revamp so we understand the look and feel. That will also help understand other changes that we might run into.
  • Have the dev team create a new CSS table class like “Wazetable” similar to the current “Wikitable”. This table class can be newly inserted by the community editors into all pages that use visual tables to match the desired style of the revamp. This will prevent the unintended change to all other non-visual uses of tables.
  • Return the core CSS for tables back to the original Wazeopedia form that matches the MediaWiki definitions for the current table classes.

This will be a huge win for both Waze in their revamp of the loop and the community editors who have to implement all these changes to our hundreds of pages in use today.

(P.S. Can we get a new subforum for the Wazeopedia Beta so we can start threads like this and not have them get lost in this one announcement thread? As I noted, I not have admin rights any more in the new forum.)

24

Hey @kentsmith9 ,

Thank you for your feedback! I will discuses it with the dev team and circle back once I have news.

I opened a new sub-forum for Wazeopedia beta, feel free to move your post/ copy it to the new sub-forum.

Thank you,

Shira

25

Thanks. I have copied that Table style code issues in https://www.waze.com/forum/viewtopic.php?t=356099 if anyone wants to discuss that further.

1 Like
26

Hey,

Thank you for sharing your feedback on the revamped Wazeopedia beta!

The developers worked on the bugs you raised and fixed more issues that came up and we are ready to go LIVE to production this week!!

I have updated Kent’s deck with the status of the bugs he shared with us.

What’s next?

Nov 20th, there will be an editing freeze for Wazeopedia for 24 hours, you can see everything is READ ONLY mode.

Nov 21th- We will live go to production.

If you have any questions/feedback feel free to email me at shira@waze.com or post on the forum.

All the best,

Shira

1 Like