Making WordPress.org

Opened 7 months ago

Closed 2 months ago

Last modified 5 weeks ago

#4649 closed defect (wontfix)

Remove content hiding mechanism on make.wordpress.org

Reported by: jonoaldersonwp Owned by:
Milestone: Priority: low
Component: Make (Get Involved) / P2 Keywords: seo


On pages like https://make.wordpress.org/community/2018/02/15/potential-addition-of-a-new-onboarding-team/, the #content container loads with a display: none attribute. This is removed by JS when the page is loaded.

This functionality should be removed, as it's harmful for SEO.

Change History (8)

#1 @jonoaldersonwp
7 months ago

  • Component changed from WordCamp Site & Plugins to Make (Get Involved) / P2

#3 @dd32
7 months ago

Is this a functionality of the upstream breath/o2 theme/plugin?

#4 @dd32
2 months ago

  • Resolution set to invalid
  • Status changed from new to closed

Closing as invalid as this is how the O2 software works. If a change is wanted, that needs to be reported and fixed in the upstream project (We will not be reinventing the wheel on dotorg).

#5 @jonoaldersonwp
2 months ago

  • Resolution invalid deleted
  • Status changed from closed to reopened

As in previous scenarios, I disupte that this is invalid simply because the problem is 'upstream'. O2 caters for many users, with many different preferences, and many different scenarios. Scoping a universal solution for all of them is an enormous project. Implementing a local solution for our needs is easier. This isn't reinventing the wheel, it's being pragmatic around how we find opportunities to achieve something remotely resembling best practice on dot org, without having to move mountains to do so.

#6 @dd32
2 months ago

  • Resolution set to wontfix
  • Status changed from reopened to closed

As stated, this is a core part of the o2 software we've chosen to use, and at this stage we're not going to change this at all.

#7 @jonoaldersonwp
2 months ago

We chose to use it without an understanding of the negative impact it'd have on our SEO. Now that that's apparent, I don't think it's unrealistic to challenge that choice.

That said, I understand that it'd be a significant undertaking to rip it out and replace it, so, why don't we just apply the laughably tiny fix I've suggested?

It's also pretty apparent that O2 isn't maintained. See https://github.com/Automattic/o2/issues.

So, we can ignore this whilst the site haemorrhages indefinitely, or, we can apply some small patches to fix it locally for us.

E.g., we could overwrite the 'hiding' behaviour by simply adding the following CSS.

#main #content { display: block; }

That might lead to a little bit of jank as the JS kicks in and hydrates the post, but, it'd address part of the immediate problem.

I'd be happy to spec up a bunch of small changes like this (like linking the post title without JS), which we could ship with minimal effort.

#8 @jonoaldersonwp
5 weeks ago

This remains a serious issue and needs addressing.

Note: See TracTickets for help on using tickets.