Marking this as invalid, as we are pursuing a static content/server-side-rendering approach.

Fabulous! Thank you so much for the effort, all <3 Officially moving this to our 'Demo Ready!' column now that the data is flowing :)

Closing this as invalid; duplicate of work completed under PP3.5.2: T433534: [Hypothesis] PP3.5.2 REST API v2 Beta Launch which enabled shared error responses on schema.wikimedia.org. Approach is a repeatable pattern for other values like pagination, which will be explored further in PP3.5.2b in Q2 FY26/27.

Moving to the API Platform Team active code review column. @KineticPelagic & @AnneT -- could you please review the updates to the docs and make sure you're aligned on the corresponding architectural changes?

Thanks for the patch, @Gkm563 ! Appreciate the consideration and contribution, as well as your patience for me getting back to you.

My understanding is that the developer portal is not currently behind the CDN. Does that change what URL we need to point at?

If it is only reading lists, I do not have concerns breaking it. Could you confirm that's the only side effect/change though?

@aaron is going to try to get the core change deployed today. We might need support from @phuedx and/or @KCVelaga_WMF to verify that the events are firing and ending up where they are supposed to within Test Kitchen.

@ArielGlenn -- Looking through the specific properties and existing structure, I think that's fine to leave commonmetadata as an array of nondeterministic key/value pairs. Based on the current response, it looks like it's already formatted as a generic array of key/value pairs anyway, so it should be fine to leave it like that if we truly don't know what the content will be.

Cool beans. I was literally in the process of writing this when I saw your reply too --

FYI -- I added a global search epic here: T438507: Content hosted through the Wikimedia Developer Portal is searchable through the main search bar

Adding to API Platform sprint board so we can do a light code review for the new API module. @KineticPelagic -- since it looks like you're on chore duty today, could you take a look?

Flagging that this will become a blocker for the contributors team in Q2.

Could you tell me more about how "not fixed" it is? Are they user defined values? And I'm assuming they're always in that format of type, nullable, description, additional properties? Is additional properties always a boolean? Where are the additional properties if it's true?

In T426852#12254925, @ArielGlenn wrote:

@HCoplin-WMF I have tweaked the naming convention section, it should cover what you've proposed. I think. See https://www.mediawiki.org/w/index.php?title=Documentation%2FAPI_documentation%2FRegistering_external_modules&diff=8577012&oldid=8571768