Why I built a CV maker with 0 dependencies, 0 backend, and 0 signups published: true
The online resume builder market is fundamentally broken. You spend an hour carefully crafting your experience, adjusting the margins, and tailoring your bullet points. You click "Export"... and BOOM. A hidden paywall po
The online resume builder market is fundamentally broken. You spend an hour carefully crafting your experience, adjusting the margins, and tailoring your bullet points. You click "Export"... and BOOM. A hidden paywall pops up asking for $19.99/month.
As an Operations Manager and developer, I absolutely hate useless friction. So I spent my nights engineering a solution that respects users.
I built ForgCV.
-The Philosophy
Zero Signups: No accounts, no email verification, no onboarding wheels.
- 100% Privacy-first: No database. Your data never leaves your browser and stays completely local (LocalStorage).
- Pure Performance: No React, no Vue, no heavy framework. Just Vanilla JS and Tailwind CSS. It loads in under a second.
The Technical Challenge: Pixel-Perfect PDFs
One of the biggest hurdles was generating a clean, ATS-optimized PDF directly on the client side without a backend server. Getting a multi-language layout (supporting 8 languages) to render beautifully with custom print margins took weeks of tuning.
I relied heavily on clean, semantic HTML structure so automated application tracking systems (ATS) can parse the text perfectly.
The tool is live, 100% free, and open-source:
π https://forgcv.com
I'd love to hear your thoughts on the architecture! How do you usually handle heavy client-side document generation?
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.