You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The design of the new tool is partly informed by feedback about the previous tool, but I'm mostly trying things out / flying blind without wireframes. If anybody would like to help wireframe things or offer design advice, I'd love the help.
This screenshot demonstrates a few patterns:
The top bar has breadcrumbs for nav, showing the flow through the app. I think this is a big improvement over the old tool
The top right has links to other modes. I don't think the styling is very clear right now, or if this is a good place for these links
The help text per mode is very long. Maybe it should be a modal popup the first time you visit that page, or have a Help button somewhere, or be a collapsible card?
The main edit mode is pretty clunky right now. You have to press a button before adding a filter, instead of just clicking a road. There will be more edit tools here eventually -- the one-way control and turn restrictions. Maybe something closer to the old tool would be better -- a bottom bar or control panel on the map, since the interactions are for the map.
Translations / localization
I've never set this up for any project before, ever. From the technical side it doesn't look too bad, now that the frontend UI is just a Svelte app. https://github.com/kaisermann/svelte-i18n looks fine. For creating the translations, Transifex and Weblate look popular -- have people used others?
A bigger question is about what should be translated. Right now most of the text in the app is quite placeholder. The long paragraphs of help text are just a first cut. And depending where someone's trying to use this, maybe "LTN", "modal filter" etc aren't the relevant terms -- "liveable neighbourhood", "no-traffic zone", "superblock", etc might be more appropriate.
The text was updated successfully, but these errors were encountered:
The design of the new tool is partly informed by feedback about the previous tool, but I'm mostly trying things out / flying blind without wireframes. If anybody would like to help wireframe things or offer design advice, I'd love the help.
This screenshot demonstrates a few patterns:
The main edit mode is pretty clunky right now. You have to press a button before adding a filter, instead of just clicking a road. There will be more edit tools here eventually -- the one-way control and turn restrictions. Maybe something closer to the old tool would be better -- a bottom bar or control panel on the map, since the interactions are for the map.
Translations / localization
I've never set this up for any project before, ever. From the technical side it doesn't look too bad, now that the frontend UI is just a Svelte app. https://github.com/kaisermann/svelte-i18n looks fine. For creating the translations, Transifex and Weblate look popular -- have people used others?
A bigger question is about what should be translated. Right now most of the text in the app is quite placeholder. The long paragraphs of help text are just a first cut. And depending where someone's trying to use this, maybe "LTN", "modal filter" etc aren't the relevant terms -- "liveable neighbourhood", "no-traffic zone", "superblock", etc might be more appropriate.
The text was updated successfully, but these errors were encountered: