{T308} We have [[ https://www.mediawiki.org/wiki/API:Data_and_developer_hub | Data and developer hub]] with some content! Declare victory. Now to aggressively improve it. What's most important to improve? I'm open to trusted actionable feedback so long as people understand that this is //focused// third-party developers to access our data sets and experiment with our APIs. == My bias is **content** - T92945: Reflect in dev.wikimedia.org what Wikimedia offers to developers - add more documentation - what? depends on {T92941} and {T93048} # I feel the biggest hole is persona Yanhui (data sets) # then more for persona Alberto (Wikidata) - more Wikidata API improvement === Resourcing: - full-time writer, more writer means more gets done - Q3 goal "Documentation task force including volunteer editors." could help - Outside chance that some developer will be motivated to showcase their own work == presentation - design pass over the Data and developer hub portal - design pass over the showcase pages - T301 skin with navigation is a hard requirement if we're going big. (lots of designer and developer time) UX team's "Blueprint" skin //may// meet our needs - custom skin will require T369: Decide a namespace in mediawiki.org to host the developer hub - Could be ambitious and skin generated code at doc.wikimedia.org and rest.wikimedia.org - smaller design needs - TXXX icon for "next step" - TXXX icon for the hub - TXXX favicon === Resourcing Designer input time, front-end developer, back-end developer == technical - T372: How to redirect from dev.wikimedia.org is easy. - still want T88755, link to [View in sandbox] from API and examples - T??? cross-site search makes this far more usable === Resourcing ? == General doc improvement huge list How pressing is etc, Other: Unordered. T322: Possibility to pair API documentation with user comments T312: Technology selection for the Developer Hub T304: Developer Hub contribution process T313: Future of the current Developer Hub at mediawiki.org