Decided on /service-name/api-spec.json (for example: /device-analytics/api-spec.json) per T333593#8861889

@SGupta-WMF Considering that the endpoint to serve the spec will need to be unique for each of the different services, we'll need to decide on a convention for the routes. After talking this over with Bill, we were thinking it would be best to serve one spec per service at /service-name/api-spec.json. For example: /device-analytics/api-spec.json. Does this sound reasonable to you?

Thanks for the update, @Sfaci!

Hi @Pppery, There's quite a few things from this task that still need to be fixed, so let's keep it open.

we are going to add them in Wikitech for the moment (in https://wikitech.wikimedia.org/wiki/Machine_Learning/LiftWing), and maybe we can reference them in the API portal when they are good enough? What do you think? To avoid duplicating too much the efforts (since we'll have internal-WMF users and external-APIGateway ones).

Thanks, @hnowlan! I agree about the standard filename within the gateway.

@elukey, I added a section for the custom rate limits applied in this patch. Feel free to correct it if I interpreted the patch incorrectly.

Hi @hnowlan, Bill suggested I ping you for your thoughts on this or to point us towards the right person to ping.

I spoke with Bill about this during code mob today. To summarize, we do not currently have a way to install swag as part of the service image (as configured in .pipeline/blubber.yaml), so we are unable to run swag as part of CI. In addition, the commands in the Makefile that we currently use for local development are also used in CI, so we cannot consolidate any of them with the docs command. Therefore our best incremental step for now is to create a make docs command and encourage its use through the README and wiki page. Since swag must be installed locally in order to generate the docs, I've added an error message that prompts the user to install swag if make docs fails.

Thanks for your comments, @bd808 and @Ladsgroup!

Hi everyone, I've updated the task description with a proposal to use the technical decision making process to manage development policies. Please share your feedback and questions here on the task.

For example, revscoring could point to https://github.com/wikimedia/revscoring, and outlink could point to its description on wikitech. Is there a way to do it? Would it be ok? I fear that some technical terms are very specific, for example people may need to know what model they are querying etc..

🎉 Nice work! I fixed up the navigation so the pages appear correctly in the sidebar. (For pages to appear in the sidebar, the DEFAULTSORT number on each page must be in sequence, without duplicates.) I also made a few small fixes, most notably moving API_reference/Service/Lift_Wing/Get_revscoring_drattopic_prediction to API_reference/Service/Lift_Wing/Get_revscoring_drafttopic_prediction to fix a typo. (I opted not to leave behind a redirect since these pages are so new.) I also added Lift Wing to the changelog to make it official.

Adding a note here that I've updated the links on:

Thanks for the patch, @MarcoAurelio! I was able to reproduce the issue locally using MonoBook. I'm seeing that your patch fixes the issue at larger screen widths, but I'm still seeing the issue at around 1450px and narrower (although because you've reduced the padding at least the whole text is visible now).

Thanks, @MarcoAurelio! That looks great

Thanks for the extra info!

@Aklapper Did you end up trying again? Did the request go through?

Thanks for opening this, @MarcoAurelio.

This patch needs review and help with a few outstanding questions I left on the patch. I'll unassign myself so a reviewer can pick it up.

Setting as stalled per the previous comment

This is done! Docs for how to access the dashboard live at https://www.mediawiki.org/wiki/Developer_Advocacy/Developer_Portal/Implementation#Analytics I also added a note to the Wikitech page about our experience with the CSP header.

I've added the Lift Wing team to the documentation editors group, so you're ready to start adding docs. I've created a landing page and an endpoint page to help you get started. (Feel free to rename these pages if you'd prefer other titles.) Let me know if you have any questions!

Hi @elukey, I've added everyone on the list to the documentation editors group 🎉 You all should now be able to create, edit, and move pages in the API Portal. I'll follow up about creating the content in T325759: Add documentation about LiftWing to the API Portal

Thanks, @Milimetric!

I wasn't able to reproduce this, so closing for now. Feel free to reopen

Thanks, @bd808!

Hi @Ottomata, Would it be possible to add developer.wikimedia.org to Matomo? Looking at the docs, it seems like we need a Matomo admin to add a site.

Depends on T289791: Define a new content strategy for the API Portal

@VirginiaPoundstone, I'm happy to leave this open until we get the proper reviews.