Change #1125555 had a related patch set uploaded (by Alex Paskulin; author: Alex Paskulin):

[wikimedia/developer-portal@main] content: Add resources for high-volume access

https://gerrit.wikimedia.org/r/1125555

[Updated March 13, 2025 following Tech Docs Team feedback]

I've opened a patch with suggested copy and layout that matches the rest of the site. Feedback welcome! Here are a few notes about our recommendations, including two requests. Our intention is to ensure the content is correct and consistent in order to create the best user experience and ease of maintenance going forward.

Organization:

After discussing with the team, we recommend including the bot traffic page within the
"Use content and data" section of the site. Although I appreciate the legal distinction between reusing project content and accessing Wikimedia infrastructure, I don't think that users of the site will be making this distinction. High-volume and commercial users are accessing Wikimedia infrastructure because they want to use project content for something. As such, they are more likely to discover the bot traffic page as part of the use case they identify with (using content).

Looking at the pageview data for the site, the "Use content and data" section is the second most popular section after "Get started". The pageviews for each section decrease as the topics become more specific and as they appear farther down the homepage. Having a highly specific section like "High-volume and commercial access" at the bottom of the homepage will likely be less discoverable and receive less pageviews than nesting it within "Use content and data". The tradeoff is that the URL for the page will be https://developer.wikimedia.org/use-content/bot-traffic/ instead of https://developer.wikimedia.org/bot-traffic/

Another option that is worth considering is using a page on the Foundation Governance Wiki for this content instead of using the Developer Portal. There are two main benefits to this:

• Foundation Wiki contains official Wikimedia Foundation policies, and as such, it would lend a greater authority to the bot traffic page than it would have on the Developer Portal.
• Foundation Wiki is also quicker and easier to update than the Developer Portal. Foundation Wiki can be updated with a simple wiki edit, while the Developer Portal needs a task opened, a patch submitted, and a weekly deployment made in order for updates to take effect.

Content:

• [Request] The Robot policy page currently has a notice stating that the page may be outdated or incorrect. The Dev Portal only links to pages without this type of notice because it can undermine readers' trust. Because of this, I've omitted this link from my patch, but I'm happy to add it whenever the notice is removed, either for this initial deploy or later on.
• Regarding the two email contacts, unfortunately the Dev Portal doesn't have the capability for forms. We could use direct mailto: links, but this is likely to create spam for these emails. Instead, we recommend creating intermediary wiki pages for each of these contacts that list the email address. This also helps provide more context about who the user is contacting and makes it easier to update these emails if they change.
  • For partnerships@, I found a page on Meta, which I've gone ahead and included in my patch. I've also updated the link text to refer to the "Partnerships team" instead of the "Technical Partnerships team" since that is what is documented on the wiki page. I'm happy to change this once a page for the Technical Partnerships team exists.
  • [Request] I wasn't able to find a page for bot traffic, so I've omitted it from the patch. I'm happy to add it once a wiki page exists for it.
• I used the standard format for the content page, with descriptions and link text instead of images.
• I rephrased the page intro to provide more context while being as concise as possible and emphasizing the ask ("We highly recommend proactively ensuring...").

Screenshots:

@Cpetrillo Hi, why is this task access-restricted to all logged-in users instead of being public?

@Aklapper didnt see that I made it users-only. Should be public now

Updating the deploy target to 3-27-25 due to working group feedback and timeline for approvals from folks with conflicts this week.

(Please use a readable date format to avoid misunderstandings - thanks! :)

After some discussion with @Cpetrillo, we've agreed that:

• Adding a link to the Robot policy page on Wikitech will be managed as a separate request once the outdated banner has been removed.
• Links to the two emails will use intermediary stub pages on Wikitech (Bot traffic and Technical partnerships; edits welcome!) until more complete pages are created by those groups later this calendar year. This helps with spam prevention, maintainability, and consistency.

I've also shortened some of the text per review feedback. See the diff between patchsets 4 and 4.

Latest screenshots:

Change #1125555 merged by jenkins-bot:

[wikimedia/developer-portal@main] content: Add resources for high-volume access

https://gerrit.wikimedia.org/r/1125555

Change #1131785 had a related patch set uploaded (by BryanDavis; author: Bryan Davis):

[operations/deployment-charts@master] developer-portal: Bump container to 2025-03-26-234702-production

https://gerrit.wikimedia.org/r/1131785

Change #1131785 merged by jenkins-bot:

[operations/deployment-charts@master] developer-portal: Bump container to 2025-03-26-234702-production

https://gerrit.wikimedia.org/r/1131785