mantoshkumar1 / mantoshkumar1/mantoshkumar1.github.io
Define and instrument the professional-conversion funnel with privacy-safe analytics
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 13m
- Merged PRs (30d)
- 2
Description
Priority: High
Problem
The site loads Plausible and already distinguishes AI-referral sources, but there is no documented end-to-end conversion model showing which visitor actions matter or whether the site is helping recruiters, hiring managers, collaborators, and readers progress toward useful outcomes.
Goal
Define a small set of privacy-safe conversion events and instrument them consistently so future product decisions can be based on evidence rather than visual preference.
Scope
- Define the visitor funnel and success events for the site's commercial/public goals.
- Consider events such as: résumé view/download, contact CTA, email/copy-email, LinkedIn/GitHub outbound click, newsletter submit, project live/source click, Insight read-through, Ask Mantosh open, successful Ask Mantosh answer, and evidence/source click.
- Avoid collecting question text, email addresses, IP-derived identity, or other unnecessary personal data.
- Define event names and properties centrally rather than scattering ad hoc analytics calls.
- Verify Plausible configuration and document where analytics are intentionally absent.
- Create a baseline report/view that can answer which paths actually lead to meaningful engagement.
Acceptance criteria
- A concise conversion model is documented.
- A bounded set of privacy-safe events is defined with stable names.
- High-value conversion actions are instrumented and verified in production.
- No sensitive visitor content is sent as analytics event data.
- AI-referral attribution remains compatible with the broader event model.
- A repeatable way exists to review conversion performance before making major UX changes.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing Plausible configuration and AI-referral attribution, then trace current analytics calls across the site. Define the conversion model, central event names and privacy-safe properties, and document where tracking is absent. Verify the high-value events in production and establish a repeatable baseline report or view.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- analytics, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100