• Review content and compare with on-wiki content to identify potential coverage gaps.
• Interview and collaborate with SMEs in each area to identify key user tasks and potential gaps in portal content.
• Update site structure and content, confirm correct sequencing for content on each page.
• Complete task-completion-focused UXR (tracked in T286087 and related).
• Review and finalize all copy.
• Add any docs not already included in the Key Docs list to the schedule for doc review.
• Resolve all TODOs in markdown files.

Notes

Proposed structure

• Explore featured apps (app-galleries)
  • seealso.org
  • apps-gallery.toolforge.org
  • toolhub.wikimedia.org
  • wikidata.org/wiki/Wikidata:Tools/Visualize_data
• Discover available wikis (content-overviews)
  • List of wikis
  • Browse by language (SiteMatrix)
  • About open licenses
• Reuse wiki content (reuse-content)
  • Browse libraries by programming language (API/Client code)
  • Use the API (Action API)
  • Download content in bulk
  • Tutorials (tutorials-content)
    • Two featured tutorials
    • Link to tutorials page
• Access public datasets (access-data)
  • Wikidata
  • Wikistats
  • Recent changes
  • Tutorials (tutorials-data)
    • Two featured tutorials
    • Link to tutorials page
• Learn with tutorials (tutorials-reuse)
• Enterprise (single link)

Strategy

• Link to introductory content to help orient content reusers without prior experience with Wikimedia.
• Link to tutorials to help content reusers who are new to programming.
• To support users without prior Wikimedia experience, avoid using Wikimedia jargon. For example, “wiki” is more specific and more obvious than “project”.
• There are several APIs that provide overlapping functionality for accessing wiki content. Instead of presenting a list of all available APIs, the Dev Portal should present the most stable, most complete APIs for the task. This includes not linking to APIs marked as experimental or unstable.
• When linking to APIs, link to the API landing page; do not link to specific modules or endpoint groups within an API.
• Separating read-only access (content reuse) and write access (tools and bots) allows us to partition off the complexity involved with editing to make things simpler for content reusers.
• Present all content reuse tutorials on a dedicated page, and present a few featured tutorials on content and data subpages.
• Content reuse journeys do not include hosting projects in Wikimedia Cloud Services.

High level user journey

• Understand that Wikimedia content and data can be reused under open licenses
  • Choose a project, topic, or dataset
    • Choose a method of access
      • Test access
        • Set up attribution
          • Write the code
            • Publish
              • Share