Page MenuHomePhabricator

Organize current and new content in the API: namespace at mediawiki.org
Open, NormalPublic

Description

Now that we have decide that Web-APIs-Hub must be integrated with the API: namespace at mediawiki.org, we need to plan a good organization of the new content with the existing content (basically the documentation of api.php action API for any MediaWiki installation).

For a good integration, we need

Event Timeline

Qgil created this task.Jul 8 2015, 10:21 AM
Qgil raised the priority of this task from to Normal.
Qgil updated the task description. (Show Details)
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJul 8 2015, 10:21 AM
Spage claimed this task.Aug 3 2015, 9:25 PM
Spage raised the priority of this task from Normal to High.
Spage added a project: ECT-August-2015.
Spage added a comment.EditedAug 10 2015, 9:34 AM

My plan:

  • API:Main_page becomes API:PHP action API (or whatever the bike shedding results in).
  • API:Web APIs hub gets a little more information so it can guide users to the various APIs.
    • Then I think it can serve as a general-purpose introduction, and definitely the one in How to contribute.
    • This pictures-and-less-wordy "Showcase-Explore-Build" is a little "adventurous" for mediawiki.org, but much existing content will continue to link to the PHP action API main page.
  • the Table of contents navigation drawn by Template:API could straddle both the general APIs and the specific PHP action API pages (see this rev).
    • eventually have to figure out how to handle in Blueprint

Just to be clear, "API:Web APIs hub" will be the new main page of the namespace, right?

API:Main_page becomes API:PHP action API (or whatever the bike shedding results in).

To a third-party developer "PHP action API" could mean it can only be used from PHP.

Just to be clear, "API:Web APIs hub" will be the new main page of the namespace, right?

Effectively. I don't know that "API:Main_page" is special. mw:API redirects to it. I will identify links to existing main page and decide if their intent is Web APIs in general or the PHP action API.

API:Main_page becomes API:PHP action API (or whatever the bike shedding results in).

To a third-party developer "PHP action API" could mean it can only be used from PHP.

Yes, not perfect but can we improve it? (MediaWiki) "action API" sounds pretty cool actually. I left out the link to bikeshedding in this wikitech-l thread.

To a third-party developer "PHP action API" could mean it can only be used from PHP.

Yes, not perfect but can we improve it?

https://lists.wikimedia.org/pipermail/wikitech-l/2015-August/082699.html

Spage moved this task from Ready to Go to Doing on the ECT-August-2015 board.

Tuesday 2015-09-01T18:00 UTC (11am San Francisco time) we will be having an IRC office hour about

If you're interested in developing with, documenting, or promoting MediaWiki/Wikimedia APIs, you should attend. I hope by having a realtime conversation we can come to a shared understanding faster.

In API_talk:Main_page I propose renaming API:Main_page to "API:Introduction to the action API". I've also tweaked the navigation template.

Spage lowered the priority of this task from High to Normal.Oct 13 2015, 6:18 PM

Lowering priority, as "How to contribute" links to new Web APIs hub and it's in the action API navigation.

Aklapper removed Spage as the assignee of this task.Sep 23 2016, 2:11 PM