Closing this ticket as the dashboard is complete. Thanks!!

Hi @catherine.kelsey.wmde - all good! Thanks for making the follow up ticket. Didn't realize this required going into another table. I'm glad it's documented for the future but would say that this last step is not urgent/shouldn't be prioritized. We have the data we need for decision making and I can always manually check if a page is a redirect or not.

Thanks @AndrewTavis_WMDE - The above list is just an example of some of the redirects so that the right field can be identified to then tag all the redirects included. It is not exhaustive.

@catherine.kelsey.wmde - thanks for the reminder! Sorry, this slipped through.

@catherine.kelsey.wmde Looks great!! Thanks for already updating.

Hi @catherine.kelsey.wmde - thanks for setting up a meeting to discuss. Overall it looks great and we're really happy to be able to see these numbers. Super helpful!

Missing pages for page views and referrers:

• https://www.wikidata.org/wiki/Wikidata:Wikibase_GraphQL
• https://www.wikidata.org/wiki/Wikidata:REST_API
• https://www.wikidata.org/wiki/Wikidata:Introduction
• https://www.wikidata.org/wiki/Wikidata:Development

I understood it more as being able to search for everything related to Berlin for example, without having to put individually - place of birth, place of death, place of residence, place of work, etc.

@Ifrahkhanyaree_WMDE These are good points and I've added them to the notes /feedback collected for the download interface. I think it's fine to close the ticket for now

In T404359#11174138, @CDobbins wrote:

@ECohen_WMDE, how do you want to do the public key confirmation? One of the most common methods is to put your pubkey on your Mediawiki page, usually in the Contact section. You could also submit a Gerrit patchset. Feel free to reach out to me here (preferred) or on Slack (Chris Dobbins) or IRC (ChrisDobbins901_) if you have any questions.

@Bugreporter - True, it's already split. Sorry I missed that!

@ovasileva I think it might make sense to split this ticket.

Merged into T329570: Add option to edit interlanguage links as an option on the language selector empty state because they address the same issue with slightly different solutions (how to add sitelinks from the empty state of language switcher in Vector 2022).

@thiemowmde This makes sense! Thanks for the diagram. When we look at it later today, I'll mention that we should start testing at 34 and go from there.

@thiemowmde Thanks for sharing this reference.

It's not a problem in Safari on iOS, so it doesn't seem to be an across the board issue. And I think external maps should be visible as well.

In T315861#8507928, @awight wrote:

In T315861#8504914, @lilients_WMDE wrote:

The focus rectangle of the teardrop markers has a big area below the marker. Is that intended?

Good question for Product! I can say that the focus rectangle has always been this shape so it's not a recent regression, but +1 that it looks bad. It's an artifact of how Kartographer draws the drop shadow, and it might be possible to work around with clever CSS.

To clarify though: I think this is a nice to have. I've added it to the help text, so if this doesn't work for some reason, then the option to use local is still covered in some way.

because setting nothing falls back to the default local

I don't think local is the default. It should be the content language of the current wiki, which is why this option is preselected. So I wouldn't add any empty option.

@lilients_WMDE I think if the ordering is with the language name first and code following (as specified), the prefix search is acceptable. Infix search might be more ideal but I don't think it's a reason to choose a different component. I'm guessing there is no option for infix with combobox?

Moved caption help text to the caption ticket