Hang and I chatted. The short list of design items we'd like tackle first:

• incorporate a main and secondary 'feed' of articles.
• incorporate discussions within the design to be more apparent
• look into designing landing pages for tags/categories

Good feedback. I can fix the issue when there is no bio. I just changed a setting. Now it won't appear if the bio is empty.

I've added a plugin to provide this capability. Let's see how well it works for our needs.

when would we want this done by?

@mcruzWMF I consider the first question in the task resolved. They are now documented in the editorial guidelines and enabled in the blog editing interface.

@Qgil Can we file a separate task for the resource loading across domains issue? It might be related, but it also might be a configuration in the calls (WordPress is using a webhook from Discourse for example) between Discourse/WordPress.

@Tgr, that tip has made some progress. I now have:

I've contacted the developer with a feature request. There is a task tracking the request: https://github.com/publishpress/PublishPress/issues/449

We actually have this plugin installed on the blog! Initially I was thinking of using the featured image in WordPress for adding images to post, which doesn't work with @Samwilson's excellent plugin. We shifted to putting an image at the top of the article right before we announced and the use of this plugin escaped my thought.

reoccurring is an erroneous use of the word. I meant recurring. :)

I posted the message to the seven wiki village pumps (Arabic, Indonesian, Italian, Japanese, Persian, Spanish, Thai).

Removed the calls to Google for fonts. Thanks Andre for the reminder.

I fixed the first two regarding the background image.

I saw the loop when I tried to sign up with my volunteer account in a private window in Safari (Mac OS) yesterday. I saw, "Refused to execute a script because its hash, its nonce, or 'unsafe-inline' does not appear in the script-src directive of the Content Security Policy." in the console.

Drafts are ready for the next steps.

The Readers Web team recently had an offsite. One discussion was the next steps for AMC. Here is a rough outline of next steps

Resolving this task.
No ripples in the water
The sand is smooth and quiet

Thanks for the ping. I've added a note to the next issue of Tech News to let folks know of the change. It will go out on 2019-04-22

This was added to Tech News in March: https://meta.wikimedia.org/wiki/Tech/News/2019/10
The change was made to the Wikipedia portal first: T216793
Then the wikis: T175877#5063452

I don't think this is only effecting Chrome (Blink) users. I'm able to reproduce on iOS using Safari (Webkit). I see this behavior when both logged out and logged in. As you can see it's also effecting other links such as "Cur, Prev, and Undo" as Andre pointed out. So not Thanks-specific and not Chrome specific. :/

Not sure why this was proxied to Phabricator. :)

Pedanticism alert!

I'm resolving this task for a few reasons. One, it was started two quarters ago. :) and two, it's rather vague and has included a bunch of discreet work. Reviwing the progress and satisfaction of my work can get a little challenging when it's 6 months between satisfaction surveys. :) Three, the work within this task encompass the initial work around AMC up to, and including, the first deployment to the three target wikis. It's a good time as any to make a break. I'll work with @ovasileva to setup tasks for me for the quarter.

Message regarding new features on mobile set to the three target Wikipedias.

It's been suggested to me to expand the table in the desertion to help with clarity. Show how the results differ for logged-out user on English Wikipedia (where logged out users can't create new prices in the mainspace) and how the results differ for logged-out users on a wiki (like French Wikipedia) where they can.

Yep, find a time and I'll be there.

Some updates

• The project page is now marked for translation (except for updates):
  • https://www.mediawiki.org/wiki/Reading/Web/Advanced_mobile_contributions

The feedback is appreciate, but I think there's a little confusion. This task is about adding a feature to search results on mobile to be more like desktop. For example if I search for "not a real page" on English Wikisource (both logged-out or logged-in) I see a red link under the search box that says "Create the page "Not a real page" on this wiki!" from which I can create a new page. The same search results on mobile do not show a red link under the search box. That is the change this task proposes.

@CKoerner_WMF would it be possible to request translations of our project page in Spanish, Arabic, and Indonesian? These are the languages we'll be launching with so it seems important to have those setup. Thoughts?

Message was posted by security to wikimedia-l, wikitech-l, and wikitech-ambassadors mailing lists.

It looks like we still have to decide which properties are supported before we document them. :)