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

Improving i18n strings for WordCamp / WordPress event sites #1356

Open
enrico-sorcinelli opened this issue Aug 9, 2024 · 0 comments
Open

Comments

@enrico-sorcinelli
Copy link

Components / Tools

WordCamp / WordPress event sites.

Description

I'm currently working setting up Rome Core Days WordPress event site.
This search (probably not comprehensive and/or with false positive) returns about 34 files containing "WordCamp" on wordcamp.org i18n strings. For example, the camptix field description "Do you have a serious allergy that could affect your experience at WordCamp?" IMHO might be a little bit misleading if I'm registering for an event that isn't strictly a WordCamp.
In the past I didn't paid to much attention to that since I had always worked on a WordCamp sites.

Stakeholders

  • Attendees
  • Event Organizers

How does this new feature contribute to the goals

Is this a feature that people need? I think so 🙂. I first discussed in meta-wordcamp a few days ago receveing some positive feedbacks.

Acceptance Criteria

Some suggestions/ideas:

  • It could be used generically a string like "WordPress event" (or simlpy "event") as for example appears in other ticket field descriptions like "It will be the first time you participate in a WordPress event". I know, changing those i18n strings will break all related translations that would need to be updated. 🙂
  • We can add a settings to mark a site as WordCamp or WordPress event and consequently use two different i18n strings (perhaps this setting might exist yet in the network admin dashboard of the WordCamps?).

Priority

Medium

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

1 participant