Skip to content
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
50 changes: 50 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,3 +34,53 @@ You can check out [the Next.js GitHub repository](https://github.com/vercel/next
The easiest way to deploy your Next.js app is to use the [Vercel Platform](https://vercel.com/new?utm_medium=default-template&filter=next.js&utm_source=create-next-app&utm_campaign=create-next-app-readme) from the creators of Next.js.

Check out our [Next.js deployment documentation](https://nextjs.org/docs/deployment) for more details.

## Autopilot Growth Plan (Frontend Interview Content + SEO Blogs)

### Quick audit (current state)

- The project already has an automated ingestion pipeline at:
- `GET /api/pipeline?token=CRON_SECRET` (collects content from Medium, Dev.to, Telegram, Hashnode)
- `GET /api/pipeline/process?key=CRON_SECRET` (AI formatting, slug/summary/company normalization)
- Interview pages and review flow already exist (`/interview-experience`, `/admin`, and DB-backed moderation/status fields).
- The missing piece for "autopilot mode" is scheduling and a daily operating cadence.

### Goal

- Publish **10-15 high-quality frontend interview experiences per day** from reputable companies.
- Add supporting frontend engineering blog content to increase SEO and top-of-funnel traffic.

### Execution plan

1. **Enable secure automation**
- Set environment variables:
- `CRON_SECRET`
- `NEXT_PUBLIC_SUPABASE_URL`
- `NEXT_PUBLIC_SUPABASE_ANON_KEY`
- `SUPABASE_SERVICE_ROLE_KEY`
- `GEMINI_API_KEY`
2. **Schedule daily jobs**
- Run ingestion daily (example: 02:00 UTC):
- `/api/pipeline?token=<CRON_SECRET>`
- Run processing daily after ingestion (example: 03:00 UTC):
- `/api/pipeline/process?key=<CRON_SECRET>`
3. **Tune for daily 10-15 quality posts**
- Keep strict narrative filtering (already present in sources such as Medium).
- Adjust per-source fetch limits and tags if daily approved content is below target.
- Maintain auto-approval only for strongly relevant frontend interview narratives; send weaker matches to review.
4. **Traffic-focused blog strategy**
- Publish 3-5 SEO blog posts/week focused on:
- Frontend interview prep trends
- Company-specific frontend interview breakdowns
- React/JavaScript/TypeScript interview round patterns
- Interlink each blog to relevant interview-experience pages and tags.
5. **Monitoring and quality guardrails**
- Track daily metrics: fetched, approved, published, duplicate rate, and source mix.
- Weekly prune low-quality sources/tags and expand high-performing ones.

### Suggested 30-day rollout

- **Week 1:** configure secrets, scheduler, and baseline metrics.
- **Week 2:** tune source filters/tags until stable 10-15/day output.
- **Week 3:** begin SEO blog cadence and add internal links.
- **Week 4:** review traffic + engagement, then iterate sources and topics.