@Nemo_bis we are looking into this on some other tasks now along with In the News and the Featured article: https://phabricator.wikimedia.org/T150806

@Tgr thanks for looking over

In T152284#2917596, @Tgr wrote:

It's probably best to use "first link/image within <some class>" instead of being more specific, as link and image markup cannot be created by hand (links cannot get classes at all; image markup is a mess that changes wildly depending on what wikitext directives you use and is completely different in Parsoid).

In T152284#2917428, @Tacsipacsi wrote:

I just followed your idea:

<div class="tfa-summary">
    <a class="image tfa-thumbnail">
        <img />
    </a>
    <p>Summary lorem impsum dolor sit amet.</p>
    <p>It may be several paragraphs long.</p>
    <div class="tfa-article">
        <a>Full article</a>
    </div>
</div>

As long as that is the only content within the div, that will work.

You can define as the first <a> in .tfa-article, then it will work most of the time. Of course, there’s no absolutely foolproof solution, humans are very clever in finding new ways to break tools. :)

Adding Gergo to review the spec as well

@Tacsipacsi Ahh, I think I am following. So you suggest wrapping ALL the content for the TFA in a div, is that correct?

In T152284#2914335, @Tacsipacsi wrote:

Should I comment here or on the talk page?

@Tacsipacsi The holidays slowed me down a bit, but here is a straw man for the markup being proposed. Please let me know if you have any thoughts or proposed changes.

Note: story links are now ordered from the MCS. The first link can be assumed to be the primary article for the story:

@Halfak format sounds good to me… thanks!

Discussed at Friday engineering chat

Discussed at Friday Engineering chat

@Halfak thanks that will be helpful. I updated the description to fit the new template. Do you have thoughts on the group size or supplies for the session?

@Halfak I can facilitate, but I am far from an expert in ORES… would you be able to provide some support (especially in AI knowledge).

Hey @srishakatux I do plan to facilitate this topic. I am updating the description now

@JMinor is this behavior right… we don't remove old content when the primary language changes right?

@Tacsipacsi You are correct, we will need templates / main pages updated across all languages. We are working on a markup spec to support this right now!

Once the above PR is merged we will need to update our parsing to take advantage of the API changes

Still has an outstanding pr: