Skip to content

docs: Add guide on building custom extensions (e.g. browser plugins) #1936

@vdusek

Description

@vdusek

Context

In #1921 (and discussion #1920), a third-party stealth-browser integration example was proposed for the "Avoid getting blocked" guide. We decided not to feature fresh third-party tools directly in our docs, since a docs example is effectively an endorsement and we want to keep the bar at proven maturity and adoption.

Internal discussion: https://apify.slack.com/archives/C06ENBV1B9Q/p1779877268101609

Proposal

  • Add a docs page describing how to build custom extensions for Crawlee — e.g. subclassing PlaywrightBrowserPlugin to integrate alternative browser backends, custom HTTP clients, etc.
  • Third-party projects can then host their own integration guides on their side and we can link to selected ones from this page, instead of maintaining tool-specific examples in our docs.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation.t-toolingIssues with this label are in the ownership of the tooling team.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions