Skip to content

MARKETING_PLAN.md

Latest commit

 

History

History
452 lines (320 loc) · 12 KB

MARKETING_PLAN.md

File metadata and controls

452 lines (320 loc) · 12 KB

Developer Marketing Plan: javascript-proxy-headers

This document outlines a comprehensive marketing strategy to promote javascript-proxy-headers within the JavaScript/Node.js developer community.

Executive Summary

Goal: Establish javascript-proxy-headers as the go-to solution for proxy header handling in JavaScript HTTP libraries.

Target Audience:

  • Developers building web scrapers
  • Developers using proxy services (especially ProxyMesh customers)
  • Library maintainers of HTTP clients
  • DevOps engineers managing proxy infrastructure

Key Messages:

  1. First library to solve proxy header send/receive for JavaScript
  2. Supports all major HTTP libraries (axios, got, undici, node-fetch, superagent)
  3. Same proven approach as python-proxy-headers

Part 1: Package Registry Publishing

1.1 npm Publishing

Status: Ready to publish

Steps:

  1. Create npm account or use existing ProxyMesh account
  2. Run npm login with credentials
  3. Verify package.json metadata is complete
  4. Run npm publish --dry-run to check package contents
  5. Run npm publish to publish
  6. Verify at https://www.npmjs.com/package/javascript-proxy-headers

Post-publish:

  • Add npm badge to README
  • Set up npm provenance (GitHub Actions workflow)
  • Consider scoped package: @proxymesh/proxy-headers

1.2 GitHub Packages

Steps:

  1. Add GitHub Packages publish workflow to .github/workflows/
  2. Configure package.json with GitHub registry
  3. Publish on release/tag

1.3 JSR (Deno Registry)

Steps:

  1. Add jsr.json configuration file
  2. Ensure ESM compatibility
  3. Publish via npx jsr publish
  4. List at https://jsr.io/

Part 2: Documentation Sites

2.1 ReadTheDocs

Status: Configuration complete, needs import

Steps:

  1. Go to https://readthedocs.org/dashboard/
  2. Click "Import a Project"
  3. Connect GitHub account if not already
  4. Select proxymeshai/javascript-proxy-headers
  5. Build will auto-trigger
  6. Configure custom domain if desired: javascript-proxy-headers.readthedocs.io

2.2 Update README Badges

Add badges for:

  • npm version
  • npm downloads
  • ReadTheDocs build status
  • License
  • Node.js version

Part 3: Awesome Lists (PRs to Submit)

3.1 awesome-nodejs

Repository: https://github.com/sindresorhus/awesome-nodejs Stars: 65,103 Section: HTTP (currently lists got, undici, node-fetch, axios, superagent)

Action: Submit PR to add to HTTP section

Proposed addition:

- [javascript-proxy-headers](https://github.com/proxymeshai/javascript-proxy-headers) - Send and receive custom proxy headers during HTTPS CONNECT tunneling. Supports axios, got, undici, node-fetch, superagent.

PR Steps:

  1. Fork repository
  2. Edit readme.md
  3. Add entry in alphabetical order within HTTP section
  4. Submit PR with title: "Add javascript-proxy-headers to HTTP section"
  5. Reference that it extends libraries already in the list

3.2 awesome-web-scraping (JavaScript)

Repository: https://github.com/lorien/awesome-web-scraping Stars: 7,787 File: javascript.md Section: Network OR new section "Proxy Server"

Action: Submit PR to add to Network or Proxy Server section

Proposed addition to Network section:

* [javascript-proxy-headers](https://github.com/proxymeshai/javascript-proxy-headers) - Send and receive custom headers during HTTPS proxy CONNECT tunneling. Extends axios, got, undici, node-fetch, superagent.

PR Steps:

  1. Fork repository
  2. Edit javascript.md
  3. Add to Network section after existing HTTP clients
  4. Submit PR with title: "Add javascript-proxy-headers to JavaScript Network section"

3.3 awesome-proxy (if exists/create)

Action: Search for or create a proxy-focused awesome list

Steps:

  1. Search GitHub for "awesome proxy" lists
  2. If suitable list exists, submit PR
  3. Consider creating awesome-proxy-tools if none exists

Part 4: Library Documentation PRs

4.1 axios Ecosystem/Community

Repository: https://github.com/axios/axios Opportunity: axios has a community ecosystem page

Action: Submit PR to add to ecosystem documentation

Steps:

  1. Check for ECOSYSTEM.md or community section
  2. Fork axios repository
  3. Add javascript-proxy-headers as "Proxy Support" extension
  4. Submit PR referencing the proxy header limitation (axios/axios#3459)

Proposed content:

### Proxy Extensions
- [javascript-proxy-headers](https://github.com/proxymeshai/javascript-proxy-headers) - Send custom headers to proxies and receive proxy response headers during HTTPS CONNECT

4.2 got Ecosystem

Repository: https://github.com/sindresorhus/got Opportunity: got links to related packages in README

Action: Open issue or PR suggesting addition to related packages

Steps:

  1. Check got's README for "Related" or "Ecosystem" section
  2. Open issue: "Add javascript-proxy-headers to related packages"
  3. Explain that it extends got with proxy header support
  4. If welcomed, submit PR

4.3 undici Documentation

Repository: https://github.com/nodejs/undici Opportunity: undici is official Node.js project, may accept ecosystem links

Action: Open discussion about proxy header extensions

Steps:

  1. Check undici documentation for ecosystem/plugins section
  2. Open GitHub Discussion (not issue): "Proxy header extension: javascript-proxy-headers"
  3. Describe the use case and implementation
  4. Ask about listing in documentation

4.4 node-fetch Wiki/README

Repository: https://github.com/node-fetch/node-fetch Opportunity: node-fetch has a wiki with ecosystem info

Action: Check wiki for community extensions

Steps:

  1. Review node-fetch wiki
  2. If community section exists, request addition
  3. Otherwise, open issue suggesting documentation improvement

4.5 superagent Ecosystem

Repository: https://github.com/ladjs/superagent Opportunity: superagent lists plugins in README

Action: Submit PR to add plugin

Steps:

  1. Review superagent README plugins section
  2. Fork and add javascript-proxy-headers
  3. Submit PR: "Add javascript-proxy-headers proxy plugin"

Part 5: Direct Maintainer Outreach

5.1 Identify Key Maintainers

Library Maintainer(s) Contact Method
axios Matt Zabriskie, contributors GitHub issues
got Sindre Sorhus GitHub, Twitter @sindresorhus
undici Node.js team GitHub Discussions
node-fetch node-fetch org GitHub issues
superagent Lad team GitHub issues

5.2 Outreach Template

Subject: javascript-proxy-headers - Proxy extension for [library]

Message:

Hi,

I've created javascript-proxy-headers, a library that extends [library] to support 
sending custom headers to proxies and receiving proxy response headers during HTTPS 
CONNECT tunneling.

This solves a common pain point for developers using proxy services (like ProxyMesh) 
that rely on custom headers for features like country selection or IP assignment.

The library is at: https://github.com/proxymeshai/javascript-proxy-headers

Would you be open to:
1. Mentioning it in [library]'s ecosystem/related projects?
2. Any feedback on the implementation approach?

Thanks for maintaining such a great library!

5.3 Outreach Priority

  1. superagent - Most likely to accept plugin listing
  2. got - Sindre is responsive, maintains awesome-nodejs
  3. axios - Large community, high impact
  4. undici - Official Node.js, good for credibility
  5. node-fetch - Moderate activity

Part 6: Content Marketing

6.1 Blog Posts

Topics to write:

  1. "How to Send Custom Headers to HTTPS Proxies in Node.js"
  2. "Solving the Proxy Header Problem in JavaScript"
  3. "Comparing Proxy Support Across JavaScript HTTP Libraries"

Where to publish:

  • Dev.to
  • Medium (JavaScript/Node.js publications)
  • Hashnode
  • ProxyMesh blog

6.2 Example Blog Post Outline

Title: "How to Send Custom Headers to HTTPS Proxies in Node.js"

Sections:

  1. The problem: Why proxy headers don't work with HTTPS
  2. How CONNECT tunneling works
  3. The solution: javascript-proxy-headers
  4. Examples for each library
  5. Real-world use cases (country selection, session management)

6.3 Video Content

Ideas:

  1. Short demo video (2-3 min) showing the problem and solution
  2. Tutorial video walking through implementation
  3. Conference talk proposal for Node.js conferences

Part 7: Community Engagement

7.1 Stack Overflow

Action: Answer proxy-related questions and mention the library

Steps:

  1. Search for questions about:
    • "axios proxy headers"
    • "node-fetch proxy custom headers"
    • "https proxy CONNECT headers node"
  2. Provide helpful answers
  3. Mention javascript-proxy-headers as a solution where appropriate
  4. Do NOT spam - only answer where genuinely helpful

Example questions to monitor:

7.2 Reddit

Subreddits:

  • r/node
  • r/javascript
  • r/webdev
  • r/webscraping

Action: Share when appropriate, engage in proxy discussions

7.3 Discord/Slack Communities

Communities to join:

  • Node.js Discord
  • Reactiflux (Node.js channels)
  • Various web scraping communities

Part 8: GitHub Presence

8.1 Repository Optimization

Checklist:

  • Add topics/tags: proxy, http, axios, node-fetch, got, undici, https, tunnel
  • Add social preview image
  • Pin repository on ProxyMesh org profile
  • Add "Used by" section once adopted

8.2 GitHub Sponsors

Action: Set up GitHub Sponsors for the project

8.3 Cross-link Repositories

Update these repos to link to javascript-proxy-headers:

  • python-proxy-headers (Related Projects section) ✓
  • proxy-examples (JavaScript section) ✓
  • scrapy-proxy-headers (Related Projects)

Part 9: SEO & Discoverability

9.1 npm Keywords

Already included in package.json:

  • proxy, http, https, connect, tunnel, headers
  • axios, fetch, got, undici, superagent
  • proxymesh, web-scraping, http-client

9.2 GitHub Topics

Add to repository:

  • proxy
  • http-client
  • axios
  • node-fetch
  • got
  • undici
  • web-scraping
  • https-proxy

Part 10: Metrics & Tracking

10.1 Key Metrics to Track

Metric Source Target (6 months)
npm weekly downloads npm 1,000
GitHub stars GitHub 100
Documentation views ReadTheDocs 500/month
Referral links from libraries GitHub 3 libraries

10.2 Tracking Tools

Action Items Summary

Immediate (Agent can do with GitHub account)

# Action Repository/Platform Type
1 Add GitHub topics to repo proxymeshai/javascript-proxy-headers Settings
2 Create PR for awesome-nodejs sindresorhus/awesome-nodejs PR
3 Create PR for awesome-web-scraping lorien/awesome-web-scraping PR
4 Create PR for superagent plugins ladjs/superagent PR
5 Open Discussion on undici nodejs/undici Discussion
6 Open issue on got sindresorhus/got Issue
7 Update python-proxy-headers README proxymesh/python-proxy-headers PR
8 Update scrapy-proxy-headers README proxymesh/scrapy-proxy-headers PR

Requires Human Action

# Action Notes
1 npm publish Requires npm login
2 ReadTheDocs import Requires RTD account
3 Blog post writing Content creation
4 Video creation Content creation
5 Stack Overflow answers Ongoing engagement
6 Maintainer outreach emails Personal communication

Timeline

Week 1:

  • Publish to npm
  • Import to ReadTheDocs
  • Add GitHub topics
  • Submit awesome list PRs

Week 2-3:

  • Library documentation PRs
  • Open discussions with maintainers
  • Cross-link related repositories

Week 4+:

  • Content marketing (blog posts)
  • Community engagement
  • Monitor and respond to feedback

Plan created: February 28, 2026