Open JoeyStk opened 1 year ago
What kind of further information is needed? Anything we can help with? This issue would probably solve the translations' problem we have with automatic translations translating addresses as well.
@osmers could you please provide some user stories? :-) Probably at least one for content creators and one for app users?
As a CMS user I want to be able to centrally manage contact information in order to minimize work when information changes As a CMS user I want adresses to be non-translateable without having to mark each address as "do not translate" in order to have consistency and minimal work As a CMS user I want the same layout incl. icons for all addresses in order not to worry about consistency As a user I want all addresses to be in the same format so that I can always find all necessary information in the same space @karthik-integreat @nassabay @dkehne can you see if you have any other user stories for this?
I would add:
Are there any questions remaining - should we ask Toni for UI/UX input? With more and more languages a central contact management would make changing information easier (yes, they can simply translate a page again, but I get that for just one phone number or name it's a bit sad to use translation budget, plus the central management eliminates mistakes and makes the layout consistent) - so I would like to move the issue to a milestone within 2024. Maybe @svenseeberg @timobrembeck @JoeyStk can write any other questions they have here.
I don't know why this issue is blocked. To me it looks like it could be worked on. Maybe we can discuss in the next grooming if we can maybe split this is up, but for now AFAIK it's good to go?
@JoeyStk yes, let's discuss this in the next grooming, plus maybe this issue: https://github.com/digitalfabrik/integreat-cms/issues/1878 since we can maybe combine them in some way?
Is this still blocked and are there still questions? Let's discuss in issue grooming today.
For next issue grooming: Provide a to list with everything that needs to be done and discuss how this could be separated into multiple issues
Blocked by the corresponding design ticket
Motivation
We want to introduce a centralized contact database which allows maintaining contact information in one place. The contact addresses can then be embedded in pages or attached to locations.
User Stories
Proposed Solution
Alternatives
Additional Context
This needs further specification
Design Requirements