Skip to content

docs: SEO landing README + migration example#1

Open
OussemaFr wants to merge 1 commit into
mainfrom
feat/seo-landing-readme
Open

docs: SEO landing README + migration example#1
OussemaFr wants to merge 1 commit into
mainfrom
feat/seo-landing-readme

Conversation

@OussemaFr

Copy link
Copy Markdown
Member

What

Replaces the placeholder README with a migration-focused landing page targeting users coming from the abandoned Node.js Facebook-scraper ecosystem (puppeteer-based packages). Adds one working TypeScript migration example.

The actual SDK lives at SocialAPIsHub/socialapis-js and ships as `socialapis-sdk` on npm. This repo is README-only — its job is SEO and audience entry. No source, no package, no CI here.

Why a separate repo

  1. SEO — the repo name `facebook-scraper-js` matches the GitHub-search queries Node devs actually type. Ranks separately from `socialapis-js` for queries like "facebook scraper nodejs", "puppeteer facebook scraper alternative", "facebook-scraper-with-puppeteer fork".
  2. Audience separation — visitors here are explicitly looking for a Facebook-scraper alternative in JS; the landing README is migration-first, everything else lives further down.

Ships

  • `README.md` — migration narrative + side-by-side BEFORE/AFTER code (puppeteer → socialapis-sdk) + method-by-method mapping + comparison-at-a-glance + pricing
  • `examples/migrate.ts` — working TypeScript migration script using the `FacebookScraper` alias

Mirrors the existing landing-repo pattern

Third landing repo in the family. Same template as:

Test plan

  • README renders cleanly on the GitHub repo page
  • All badges resolve (npm v0.1.1, License MIT, Node ≥18)
  • Internal links resolve (socialapis-js, socialapis-python, socialapis-go, socialapis.io)

Modern TypeScript/JavaScript alternative to the abandoned Node.js
Facebook-scraper ecosystem (puppeteer-based packages, all stale).
This repo is a landing page — the actual SDK lives at
SocialAPIsHub/socialapis-js and ships as `socialapis-sdk` on npm.

Mirrors the structure of SocialAPIsHub/facebook-scraper-python
(kevinzg refugees). Same template, idiomatic JS code samples,
TypeScript types in the response shapes.

Ships:
- README.md — migration narrative, side-by-side BEFORE/AFTER
  code (puppeteer-based scrape → socialapis-sdk one-liner),
  method-by-method mapping table, comparison-at-a-glance,
  pricing
- examples/migrate.ts — working migration script using the
  FacebookScraper alias

Why a separate repo: the repo name itself ("facebook-scraper-js")
matches the GitHub-search queries Node devs actually type. Ranks
separately from socialapis-js for queries like "facebook scraper
nodejs", "puppeteer facebook scraper alternative".
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant