Library / SDK
BartoszJarocki/cv avatar
BartoszJarocki/cv

BartoszJarocki/cv: a print-friendly CV built on Next.js

Print-friendly, minimalist CV page

9,680 stars1,060 forksTypeScriptMIT

At a glance

What is it?
A single-page Next.js app that renders a minimalist CV from one TypeScript data file, with a print-friendly layout. It suits engineers who want to edit a resume in code and deploy it themselves.
Who is it for?
Adopt it if you are comfortable editing TypeScript and want a CV you can version, print and host yourself. Skip it if you need a CMS, multi-language content or a visual editor, because the README describes none of those.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 24 days ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 21, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • BartoszJarocki/cv9,680 ★ · +5
Star history
Repository2026-09-222026-11-21
BartoszJarocki/cv9.7k9.7k

5 Stars in the last 60 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

What BartoszJarocki/cv actually replaces

Most resume tools assume you will drag boxes around a canvas and export a PDF. This project takes the opposite position: the resume is a data structure, the page is a React component tree, and the print output is a stylesheet concern. The README describes it as a "simple web app that renders a minimalist CV with print-friendly layout", and the repository confirms that framing. There is no admin panel, no database and no authentication in the top-level entries.

The intended user is a developer who already keeps a personal site or a GitHub Pages deploy and wants the CV to live in the same workflow. Editing means opening src/data/resume-data.ts and changing values. Reviewing means reading a diff. Publishing means pushing to a host that runs Next.js. If your resume changes twice a year and you dislike re-formatting a Word document each time, that trade is favourable. If you want to hand the file to a recruiter who will edit it, it is not.

One data file, six section components

The project structure in the README is unusually explicit, which makes the data flow easy to follow. Everything the reader sees starts in src/data/resume-data.ts, exported as a constant named RESUME_DATA. That object is imported by page-level components under src/app/components: header.tsx, summary.tsx, work-experience.tsx, education.tsx, projects.tsx and skills.tsx. Each component corresponds to one section of the page.

The consequence is that adding a section is a code change, not a config change. You add a component alongside the others in src/app/components. That is a real cost; the README documents customization as editing the data file, with the palette defined as six oklch colour roles in src/app/globals.css and mapped onto Tailwind colour names by tailwind.config.js.

Installing it and editing your first resume

The README's getting-started block is the shortest path. It clones the repository, installs with pnpm, and starts the Next.js dev server on port 3000. The package manager matters here: pnpm-lock.yaml is committed and package.json sets packageManager to [email protected], so mixing in npm or yarn will not match the lockfile.

bash
git clone https://github.com/BartoszJarocki/cv.git
cd cv
pnpm install
pnpm dev
# open http://localhost:3000
# edit src/data/resume-data.ts to customize

After pnpm dev, the terminal prints the local URL and the browser shows the rendered CV. From there, the README's customization example shows the shape of the data object you are editing: name, location, siteUrl, about and summary, with the comment "// ... more fields" standing in for the rest.

typescript
// src/data/resume-data.ts
export const RESUME_DATA = {
  name: "Your Name",
  location: "Your City, Country",
  siteUrl: "https://cv.example.com", // where this CV is deployed
  about: "One line under your name", // also the meta description and share image text
  summary: "A paragraph for the About section",
  // ... more fields
}

The README does not enumerate every field, so read src/data/resume-data.ts before assuming a key exists.

Print output is the whole point, and the hardest part to verify

A CV that looks fine in a browser and breaks across a page boundary is useless. The project claims a print-friendly layout. What the README does not provide is a print stylesheet walkthrough, any guidance on page-break rules, or a sample PDF. If you need a specific page count, you will be tuning that yourself.

The same gap applies to ATS parsing. Many employers still run resumes through text extractors, and a React page rendered to PDF produces whatever the browser's print engine emits. The README does not claim ATS compatibility and nothing here measures it. Treat the printed output as something to check against a real job application before you rely on it.

There is also no versioning or rollback story. The README does not document rollback, and the repository has no published GitHub releases, so a bad edit is corrected by reverting a commit. That is normal for a personal site and awkward for anyone expecting staged drafts.

How it compares with JSON Resume and hosted builders

JSON Resume takes the data-driven idea further by standardising the schema itself. Its format is a published specification with themes that consume it, so a resume written once can be rendered by many tools. This project inverts that: the schema is local to src/data/resume-data.ts, and the renderer is the app. You get a specific design and a working print layout out of the box, but no portability if you later want a different theme or a different generator, because your content is shaped to this project's types.

Hosted builders sit at the other end. They give you a visual editor, templates and PDF export without a build step, at the cost of your resume living inside someone else's product. BartoszJarocki/cv sits in the middle: more control than a builder, less portability than JSON Resume, and a deployment story (a Vercel button in the README) that neither of the others matches directly.

Toolchain, licence and the cost of keeping it current

The stack is deliberately current: Next.js 16, React 19, TypeScript 5, Tailwind CSS 3.4, Biome 2.0.6 for linting and formatting, a Radix UI dialog primitive, and Geist for type. The scripts in package.json split lint, format and check into plain and auto-fix variants, so pnpm check is the single command for a clean tree and pnpm check:fix writes the fixes.

That currency is also the maintenance bill. Next.js and React major versions move quickly, and a personal CV repo tends to be touched rarely, which means upgrades arrive in one large jump rather than small ones. The last push was on 2026-10-28, so the dependency set reflects that date rather than today. Budget an afternoon for a major Next.js bump.

The licence is MIT, which permits commercial use, modification and redistribution provided the copyright notice and permission notice are retained. The repository contains a single LICENSE file at the top level, and there is no separate licence for the resume content itself, which is worth noting because the sample data in resume-data.ts is the author's own. Replace it rather than ship it. This is a description of the licence text, not legal advice.

Editorial conclusion

Adopt it if you are comfortable editing TypeScript and want a CV you can version, print and host yourself. Skip it if you need a CMS, multi-language content or a visual editor, because the README describes none of those. Before committing, open src/data/resume-data.ts and confirm its shape matches your history, then run pnpm build and print the result to check the layout survives your longest job title.

Frequently asked questions

How do I install BartoszJarocki/cv and run it locally?

Clone the repository, run pnpm install, then pnpm dev, and open http://localhost:3000. The README lists those steps and notes that src/data/resume-data.ts is the file to edit.

Do I need to know React to change the content of BartoszJarocki/cv?

No for content: the README says all resume content lives in the single file src/data/resume-data.ts. Mostly yes for structure: adding a section means editing the components under src/app/components, while a section whose data is empty, such as projects: [], is skipped by the page.

Can I self-host BartoszJarocki/cv with Docker?

The top-level entries list no Dockerfile or docker-compose file and the README gives no Docker steps. It documents pnpm build and pnpm start for a production server, and a Vercel clone button next to the title.

Is BartoszJarocki/cv free to use for a commercial job application?

The project is MIT licensed, which permits commercial use and modification as long as the copyright and permission notices are kept. The README does not state separate terms for the sample resume content, so replace the data in src/data/resume-data.ts with your own.

Official sources

  1. BartoszJarocki/cv on GitHub
  2. Issues
  3. License: MIT
  4. Project website
  5. README
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/bartoszjarocki-cv.svg)](https://hysenlabs.com/projects/bartoszjarocki-cv)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/bartoszjarocki-cv.svg)](https://hysenlabs.com/projects/bartoszjarocki-cv)

Was this useful?