Added a proposed design, looking for feedback 👨🏽‍💻

In T209107#4752795, @Prtksxna wrote:

Added a proposed design, looking for feedback 👨🏽‍💻

Why a border around the Almost there... box?

In T209107#4752795, @Prtksxna wrote:

Added a proposed design, looking for feedback 👨🏽‍💻

I think the design of this page looks good. The border Niharika asks about seems useful to me--it gives the notice a bit more prominence, which it needs. If anything, since the user will fail in her objective of setting up an event if she doesn't understand this point, I'd do more, like adding some color.... But I'm OK with this as is if you are.

Moving this to To be Estimated. (I withdrew my previous questions; I remember how this works now.)

In T209107#4754309, @Niharika wrote:

Why a border around the Almost there... box?

Yeah, I added it to give it more prominence, especially since a lot of visual attention currently goes to the other gray boxes.

Categories without participants (T205734) probably won't happen in the near-term, but something like the worklist filter without participants is very much feasible and more likely to happen soon-ish. In that case participants OR a worklist would be required, so ideally the messaging would allow for this. Keep in mind the messages are marked for translation, so it's best to think ahead. 11 translations exist for the current message "This event has not been completely configured. In order to generate statistics, you must add one of the following: " which is then followed by a comma-separated list of the required filters.

Change the wording of the notice as follows:

• ... To generate metrics, ...

The message "generate statistics" is scattered around the application, hopefully it's okay to keep with this language? I may be wrong but "metric" would refer to the type or measurement, e.g. "pages created". The word "statistic" may be more exacting in this context, referring to the data gathered using each predefined metric.

please change the example text in the wiki field to "wiki name"

The current placeholder "en.wikipedia" is solely there to indicate the expected format. "wiki name" may be ambiguous, e.g. "English Wikipedia" will not work. They'll surely figure out the format (thanks to autocompletion), so maybe we could just use "wiki" instead of "wiki name"?

In T209107#4944390, @MusikAnimal wrote:

Categories without participants (T205734) probably won't happen in the near-term, but something like the worklist filter without participants is very much feasible.... Keep in mind the messages are marked for translation, so it's best to think ahead. 11 translations

You'll notice this is titled the "interim" design. That is, this will be the design until we release Worklist, which will involve a complete redesign of the setup page (in Release II). Sorry that wasn't clear; I've added some language to that effect. My apologies to the translators, but interim solutions are the unavoidable cost of an Agile process.

Change the wording of the notice as follows:

• ... To generate metrics, ...

The message "generate statistics" is scattered around the application, hopefully it's okay to keep with this language? I may be wrong but "metric" would refer to the type or measurement, e.g. "pages created". The word "statistic" may be more exacting in this context, referring to the data gathered using each predefined metric.

Thanks for pointing out that "metrics" is not used properly; I've changed the language in the Description—though not to "statistics." Statistics is a little narrow for what we're generating, which includes things like the usernames of editors and the titles of articles created. I've changed it to "event data".

please change the example text in the wiki field to "wiki name"

The current placeholder "en.wikipedia" is solely there to indicate the expected format. "wiki name" may be ambiguous, e.g. "English Wikipedia" will not work. They'll surely figure out the format (thanks to autocompletion), so maybe we could just use "wiki" instead of "wiki name"?

Hmmm. I don't think "Wiki" is any more clear than "Wiki name," which is at least parallel to "Category name." We could say: Wiki (e.g., en.wikipedia). But not all languages have an abbreviation like "e.g." and that is getting a little long anyway. As you say, there is autocomplete, so format will not really be a problem.

I don't think "Wiki" is any more clear than "Wiki name," which is at least parallel to "Category name." We could say: Wiki (e.g., en.wikipedia). But not all languages have an abbreviation like "e.g." and that is getting a little long anyway. As you say, there is autocomplete, so format will not really be a problem.

"Category name" is the name of the category, whilst the wiki is actually the domain. We already have a message "Wiki", so using it would be consistent with what we say elsewhere, e.g. settings page where you enter "wikis", at the top of Event Summary, and the column heading on the Edit List page. Sorry for the nitpick! Just trying to keep things consistent and avoid redundant messaging. For future reference, if it at all helps, you can review existing messages at https://github.com/wikimedia/eventmetrics/blob/master/i18n/en.json. We don't necessarily re-use them, but we should maybe try to if the context is the same.

In T209107#4944786, @MusikAnimal wrote:

I don't think "Wiki" is any more clear than "Wiki name," which is at least parallel to "Category name." We could say: Wiki (e.g., en.wikipedia). But not all languages have an abbreviation like "e.g." and that is getting a little long anyway. As you say, there is autocomplete, so format will not really be a problem.

"Category name" is the name of the category, whilst the wiki is actually the domain. We already have a message "Wiki", so using it would be consistent with what we say elsewhere, e.g. settings page where you enter "wikis", at the top of Event Summary, and the column heading on the Edit List page. Sorry for the nitpick! Just trying to keep things consistent and avoid redundant messaging. For future reference, if it at all helps, you can review existing messages at https://github.com/wikimedia/eventmetrics/blob/master/i18n/en.json. We don't necessarily re-use them, but we should maybe try to if the context is the same.

OK, changing to "Wiki."