The fact that there is also doc.wikimedia.org (justified in its existence btw) kind of points to there being too many weird duplicating websites for this. mw.org and doc.wm.org can definitely fulfill the need for these two.

Please see https://www.mediawiki.org/wiki/Developer_Portal and subpages for information about why we felt that a narrow, non-wiki site would be a better initial entry point for discovering information about the how to get involved in Wikimedia technical spaces.

In T358303#9570818, @bd808 wrote:

Please see https://www.mediawiki.org/wiki/Developer_Portal and subpages for information about why we felt that a narrow, non-wiki site would be a better initial entry point for discovering information about the how to get involved in Wikimedia technical spaces.

Then close api.wikimedia.org? api.wikimedia.org is the 4th result in Google by "wikipedia api", under mediawiki.org and Wikipedia "API" article, and the 2nd result by "wikimedia api". developer.wikimedia.org is nowhere to be seen. This not exactly serves the discoverability mission that is outlined on the page you linked:

Some documentation should be more discoverable, some documentation is dispersed or duplicated across several websites, some of our documentation is outdated, some of our technology areas could be more discoverable.

"Upon arriving on the MediaWiki and Wikitech home pages, I was instantly lost." -- Ashwin Bhumbla
"MediaWiki documentation is not only infamously incomplete, but also terribly scattered." -- Waldyrious

> xkcd comic about 10 standards (OK, I'm kidding)

Another point to consider is that outsiders don't know the word "Wikimedia". They are often even puzzled if Wikimedia is a legit site and not a scam where they slipped in "m" instead of "p".

FYI we can't see that image.

In T358303#9574510, @Jack_who_built_the_house wrote:

Then close api.wikimedia.org? api.wikimedia.org is the 4th result in Google by "wikipedia api", under mediawiki.org and Wikipedia "API" article, and the 2nd result by "wikimedia api". developer.wikimedia.org is nowhere to be seen. This not exactly serves the discoverability mission that is outlined on the page you linked:

api.wikimedia.org is a different initiative by a different team started at a different time. I actually personally agree that it serves an unclear audience and purpose, but I do not have any idea who currently has the institutional authority within the Foundation to make a decision to sunset that never fully completed project.

We won't merge developer.wikimedia.org into mediawiki.org. There is documentation on https://www.mediawiki.org/wiki/Developer_Portal for past decisions.

but I do not have any idea who currently has the institutional authority

Not sure either. https://wikitech.wikimedia.org/wiki/API_Portal#Maintainers ; https://www.mediawiki.org/wiki/Platform_Engineering_Team/API_Value_Stream#API_Portal (historical); https://www.mediawiki.org/wiki/Wikimedia_Technical_Documentation_Team#API_Portal may provide hints.

Hi all, Thanks for this feedback. The API Portal is waiting on decisions from product management to determine next steps, but I'll provide an update here once I know more.