WordPress documentation – a step backwards

I don’t like the switch to https://developer.wordpress.org

The documentation is noisy and full of bad examples. In the past I remember searching for quick reminders on WordPress functions on how and when to use them, and landing on really useful pages. The information was right there.

Now there’s just a copy of what’s in the code, some abstract software-correct machine driven parameters, lots of drivel that’s of no use to your average WordPress developer, And then follow some examples that always fail to answer what I’m looking for.

It probably looks super useful to core developers/committers who think it provides a wealth of useful information. But WordPress’s success has been to enable the day-to-day WordPress developer – no matter their WordPress involvement – to achieve their web development goals. And this latest iteration on documentation fails to do that.

Published by

TCBarrett

Open Source Architect (Web Geek)

2 thoughts on “WordPress documentation – a step backwards”

  1. I can’t help thinking that half of the motivation to leave was the sheer effort involved in weeding out old/stale/plain wrong advice in the old system.

    From a developer perspective I am training myself to use Dash instead…

  2. Could you fix your captcha code on your contact page, we’re trying to reach you. It says invalid token.

Comments are closed.