Page MenuHomePhabricator

Consider IPA implications for lead
Closed, ResolvedPublic

Description

I think a lot of thought has to be put into how this element interacts with the lead and the formulation of the lead (or not). The lead is one of our most important areas of a page, used in popups, search result etc and the IPA has often been problematic (you can see the IPA help page often being mentioned in search results for instance).

I think this should be a separate ticket, to make sure it gets the attention it deserves.

Event Timeline

TheDJ renamed this task from Consider IPA implications for lead generation to Consider IPA implications for lead.May 27 2022, 8:08 PM

Interesting points! I know we're a little way off any design work, but this is definitely something we'll need to consider β€” are you thinking along the lines of "cluttering" the lead?

Interesting points! I know we're a little way off any design work, but this is definitely something we'll need to consider β€” are you thinking along the lines of "cluttering" the lead?

Well the current IPA (and download button/help link) already clutter the lead at times (especially the textual fallback version of it). We probably shouldn't make it worse, and probably attempt to make it better ;)

Thanks for cutting this task and for reminding us to consider! The lead, and the impact on search based on the lead, has definitely been top of mind as our designer @nayoub plans out the design research ahead of us

We may need to wrap the IPA output in data-nosnippet (https://developers.google.com/search/docs/advanced/crawling/special-tags#inline-directives) to prevent it from appearing in SERPs

TheresNoTime changed the task status from Open to Stalled.Aug 17 2022, 8:29 AM
TheresNoTime claimed this task.

@TheDJ I'm pretty sure T315404: Wrap Phonos output in data-nosnippet is going to resolve most of the considerations you raised β€” can you think of any others?

TextExtracts hides elements with the configured CSS class. I don't think we should add .ext-phonos to that list, but instead perhaps we should add .noexcerpt to the Phonos output? I see it currently is being picked up by TextExtracts, with all the metadata in the <span> tag as well.

TextExtracts hides elements with the configured CSS class. I don't think we should add .ext-phonos to that list, but instead perhaps we should add .noexcerpt to the Phonos output? I see it currently is being picked up by TextExtracts, with all the metadata in the <span> tag as well.

Didn't know about that! But yes, we probably should 😌

@TheresNoTime, are we ready to close this? Or should we keep it open a bit longer?

@TheresNoTime, are we ready to close this? Or should we keep it open a bit longer?

Let's boldly close it πŸ˜„