Docs: Add Proxies & Configure Proxy

[tembo]

Description

Adds SDK docs for the new Proxies feature and 'Configure proxy' page.

Changes

Covers proxy types (overview, datacenter, ISP, residential, mobile, custom).

Want me to make any changes? Add a review or comment with @tembo and i'll get back to work!

---

TL;DR

Adds comprehensive documentation for the new Proxies feature, covering various proxy types and their integration with Kernel browsers.

Why we made these changes

To provide users with clear and detailed guides on how to set up, manage, and utilize the new Proxies feature, a significant addition to the platform's capabilities.

What changed?

• New "Proxies" Documentation Section:
  • Created a top-level proxies/ directory with an overview.mdx page explaining how to create, list, use, and delete proxies.
  • Added detailed pages for each proxy type: datacenter.mdx, isp.mdx, residential.mdx, mobile.mdx, and custom.mdx, each with specific configuration examples.
• Browser Integration:
  • Updated the browsers/stealth.mdx page to cross-reference the new Proxies documentation for configuration details.
• Site Structure:
  • Updated docs.json to add the new "Proxies" section and its pages to the site's navigation structure.
• Repo Maintenance:
  • Updated .gitignore to exclude Python virtual environments (venv) and cache (__pycache__) files.

Validation

• Docs render correctly in the staging environment.
• Links between new and existing pages are working as expected.
• Technical accuracy of the content has been verified.

^{Description generated by Mesa. Update settings}

[tembo]

Requesting review from @juecd who has experience with the following files modified in this PR:

• docs.json

[mesa-dot-dev]

Performed full review of a33766f...abbed72

Analysis

Based on the provided analysis, there are no architectural issues identified with the pull request. The analysis exclusively highlights strengths of the documentation architecture, information hierarchy, and user experience design. It mentions clear organization, consistent patterns, good cross-referencing, code example consistency, progressive disclosure, practical context, and best practices integration - all presented as positive aspects of the implementation.

Since no architectural issues were identified in the analysis, there are no potential problems to report.

Tip

⚡ Quick Actions

This review was generated by Mesa.

Actions:

• Configure your agents

Slash Commands:

• /review - Request a full code review
• /review latest - Review only changes since the last review
• /describe - Generate PR description. This will update the PR body or issue comment depending on your configuration
• /help - Get help with Mesa commands and configuration options

^{8 files reviewed | 0 comments | Review on Mesa | Edit Reviewer Settings}

[juecd]

I'm going to propose / push some changes on this, so please don't merge this yet

[masnwilliams]

@juecd gotcha 👍

Also want to double check that the code examples tembo generated here are real 👀 @sjmiller609

[sjmiller609]

I corrected the docs to make them more accurate. I'm having issues with the mobile and residential proxy examples not working when highly targeted geolocation is specified. I'm thinking this might be related to bright data onboarding, so I want to hold off on merging this until we finish unlocking the bright data proxies all the way (should be tomorrow after we meet with them for KYC).

[sjmiller609]

going to add known limitations to docs and clarify some wording