MediaWiki talk:Gadget-TripPlanner Voyage Tips and guide

Thanks for all the work you’ve put into this gadget!

After reviewing the current implementation, I’ve gathered some technical and UX feedback to help get this ready for a wider launch. There are a few areas where we can tighten up the code and some UI bits that could use a polish. I hope this is helpful. Let me know if anything needs expanding or clarifying!

Firstly some very low hanging fruit:

• Storage & Frameworks: Please switch from localStorage to mw.storage to stay within the MediaWiki environment. Also, could you swap out deprecated jQuery functions like .done() and .fail() for .then()?
• Coordinate Handling: The current logic assumes coordinates are always in decimal format. We should ensure it handles Degrees, Minutes, Seconds (DMS) as well.
• Clean-up: Also, keep an eye out for "dead code" (like m.on('popupopen') that can be cleared out to make the structure easier to follow.
• Please do not rely on HTML structure as it is not covered by

mw:Stable_interface_policy/Frontend. Please use mw.util.addPortletLink api for adding items to menus.

• Visuals & Accessibility: The dark mode is currently a bit too bright with low contrast, which hits accessibility. Also, the current icon feels a bit "clipart" compared to the site's aesthetic; a black icon would likely fit the look and feel much better. Let's also ensure buttons follow best practices for touch sizes on mobile devices. Right now they are very small.
• Clicking the backpack icon also creates a dialog inconsistent with other dialogs. It looks more jquery.ui then Vue. Could we update this to use @wikimedia/codex and vue to fit better with the general look and feel of the site ir at very least mirror the styling there? Using Vue on long term would also likely address a lot of accessibility/consistency issues. For example Vue dialogs close on escape key.
• The "Move" function and "Drag and Drop" (specifically on mobile devices) are feeling a bit buggy/incomplete at the moment (I can share a video for this one if that is helpful - just ask). The concept of how to populate days from the backlog felt a little alien to me compared to other sites I use so maybe we could collect some more feedback about this specifically?

• The existing insertion creates layout shifting (CLS) on both mobile and desktop, which requires the re rendering of the page. We know Google heavily penalises against this in the SEO as it leads to bad UX (e.g if a user tries to click a button that then shifts position and causes them to click another). Given wikivoyage already has had SEO challenges in its lifetime this is a must fix for me if you want to add it for anonymous users. To fix I see two approaches. Firstly you could move it into the user menu dropdowns on both Minerva and Vector 2022. Alternatively if you want to keep the existing positioning use some CSS to reserve space.

• I think the Route Calculator—while cool—will be a bit too advanced for most of our users. most readers might struggle with the concept of an ORS API Key so perhaps we could detect one based on the presence of a global variable in user js and provide a link to instruct how to set that up?
• The external service call to openrouteservice.org is a little concerning from a security point of view. Could we use a wmcloud proxy instead? Note that a Content-Security-Policy will be added to Wikimedia projects in the near future that will block this from working in future as it is currently written.

• I have shared this already: the ReadingLists extension is launching soon.

Instead of building this from scratch, we could pivot to use that as the foundation. We could localize "Lists" as "Trips" and use your gadget to enhance them (e.g., adding download options). This would make the feature much more maintainable (especially if we could utilize the bookmarkicon in articles) while letting the gadget serve as a "hot bed" for innovation for new features. I’m happy to chat through how we can adapt your current work to fit that model if that is something you are willing to talk through more. The concept of reading lists on Wikivoyage doesn't make sense so being able to repurpose it as a Trips feature seems like a good idea. Jdlrobson (talk) 13:29, 22 February 2026 (UTC)Reply

Ping @Andree.sk - not sure if you missed this?

I've updated the gadget to display for all logged in users by default (not anonymous users) while we work on this feedback. Jdlrobson (talk) 16:20, 14 March 2026 (UTC)Reply

Actually I did miss it :-) Thanks for the ping and extensive feedback, I'll go through it and get back to you! -- andree 16:28, 14 March 2026 (UTC)Reply