Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feedback requested: overall UI design #17

Open
dabreegster opened this issue Feb 12, 2024 · 1 comment
Open

Feedback requested: overall UI design #17

dabreegster opened this issue Feb 12, 2024 · 1 comment

Comments

@dabreegster
Copy link
Collaborator

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.

image
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?

image
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.

@rouelibre1
Copy link

About translations I believe StreetComplete uses https://poeditor.com/
There is also https://crowdin.com/

@dabreegster dabreegster pinned this issue Mar 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants