As part of the new content strategy for the API Portal (T289791), prototype an API Page for the Device Analytics API.
Working page: https://api.wikimedia.org/wiki/Device_Analytics_API
As part of the new content strategy for the API Portal (T289791), prototype an API Page for the Device Analytics API.
Working page: https://api.wikimedia.org/wiki/Device_Analytics_API
I'm curious how this works out in practice. The way we divided the AQS API into services was more for implementation reasons than user-facing reasons, and I'm not sure how happy we'll be with dividing the documentation along those same lines.
I'm not saying I think it is a bad idea to experiment with it, just saying it is something to think about as we move forward.
Removing AQS2.0 since this work is for the organization of the API Portal, not a requirement for AQS 2.0
Resolving this for now pending changes in product management and direction. We can re-open this at a later time if needed.