Already +2'd this patch, but wanted to note here that the page appears for me at http://localhost:9000/build-info.txt not http://localhost:9000/build-info/

Completed this section of work in preparation for Dev Portal launch:

Yes! That sounds like a good idea

I think we can call this done. Thanks, Andre!

The Twitter card now appears on https://cards-dev.twitter.com/validator but it's missing the image. I'm not sure why or how to troubleshoot.

Thanks for the tip! Hopefully that did it

Looking at the Twitter docs, it seems like svg files aren't supported. How about something like this instead of one of the illustrations:

Removing the parent task since it causes this task to show up under the MVP launch parent task

I think we can call this done based on https://wikitech.wikimedia.org/wiki/Developer.wikimedia.org#Production_deployment

Removing the parent task since it causes this task to show up under the MVP launch parent task

I completed a basic review of this page. There are several pages linked from this page that have outdated or fixme templates, but I don't think resolving those is within the scope of this review, although I noted them in my metrics sandbox.

Thanks! This is helpful. I think seeing that titles are included in the search index is enough to call this resolved

I added some notes to the task from a presentation I saw recently about how to evaluate for accessibility

So is T309087 currently possible? Or it requires the change proposed by this task?

I think we're close enough to launch to evaluate and close this

In April, I used placeholder content in Hebrew to evaluate the site's support for RTL. This revealed a few issues with the translation system in general that were resolved, and a few issues with RTL styles that were also resolved. Now that the integration with translatewiki has been enabled and the placeholder content has been removed, we cannot do an evaluation with an RTL language speaker until the site has content in that language. Closing this as complete for the MVP

A few questions about this:

Resolved by https://gitlab.wikimedia.org/repos/commtech/toolforge-docs/-/merge_requests/34

Resolved by https://gitlab.wikimedia.org/repos/commtech/toolforge-docs/-/merge_requests/32

On second thought, I don't think the single search button is going to work for this since it needs to have a selector and a button. I think the form is the best way to do this

Is that sufficient? :)

Thanks!

Thanks!

I'd change the translatable string part to <abbr title="Frequently asked questions">FAQ</abbr>

Overall, the page looks great: organized by audience, responsive on mobile. There are a few things I would change (if I had admin rights):

Added an example to the quickstart section, removed the overview header, and made copy edits. Changes

I've also updated https://www.mediawiki.org/wiki/Skin:WikimediaApiPortal#Site_footer and https://api.wikimedia.org/wiki/MediaWiki:FooterLinks to avoid future confusion

Ah yes, I remember now. We moved the footer links out of MediaWiki:FooterLinks into the message file. Thanks for your help, @TheresNoTime!