cvmake — Next.js 作品集模板

SHA-256: 9f577065799df207b67bff2bed5df29a9284817205cb1b31c79fde0b963a177f

2026-10-14T18:52:35.234Z

# cvmake

> Open-source CV builder. YAML in, PDF out.

[![npm](https://img.shields.io/npm/v/@codevena/cvmake-cli?logo=npm&label=cvmake-cli)](https://www.npmjs.com/package/@codevena/cvmake-cli)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
[![CI](https://github.com/Codevena/cvmake/actions/workflows/ci.yml/badge.svg)](https://github.com/Codevena/cvmake/actions/workflows/ci.yml)
![Next.js](https://img.shields.io/badge/Next.js-16-black?logo=nextdotjs)
![TypeScript](https://img.shields.io/badge/TypeScript-5.6-3178c6?logo=typescript&logoColor=white)

**→ Template showcase: [cvmake.codevena.dev](https://cvmake.codevena.dev) · Live editor: [cveditor.codevena.dev](https://cveditor.codevena.dev)**

<p align="center">
  <img src="docs/collage-4templates.png" width="800" alt="One YAML, four templates — classic-serif, swiss, bauhaus, noir all rendered from the same example.en.yaml" />
  <br/>
  <em>One YAML file. Four templates. Switch by changing one line.</em>
</p>

---

## Showcase

<table width="100%">
  <tr>
    <td width="25%" align="center"><img src="docs/screenshots/academic.png" width="200" alt="academic"><br/><b>academic</b></td>
    <td width="25%" align="center"><img src="docs/screenshots/bauhaus.png" width="200" alt="bauhaus"><br/><b>bauhaus</b></td>
    <td width="25%" align="center"><img src="docs/screenshots/classic-serif.png" width="200" alt="classic-serif"><br/><b>classic-serif</b></td>
    <td width="25%" align="center"><img src="docs/screenshots/corporate.png" width="200" alt="corporate"><br/><b>corporate</b></td>
  </tr>
  <tr>
    <td width="25%" align="center"><img src="docs/screenshots/creative-accent.png" width="200" alt="creative-accent"><br/><b>creative-accent</b></td>
    <td width="25%" align="center"><img src="docs/screenshots/editorial.png" width="200" alt="editorial"><br/><b>editorial</b></td>
    <td width="25%" align="center"><img src="docs/screenshots/magazine.png" width="200" alt="magazine"><br/><b>magazine</b></td>
    <td width="25%" align="center"><img src="docs/screenshots/modern-minimal.png" width="200" alt="modern-minimal"><br/><b>modern-minimal</b></td>
  </tr>
  <tr>
    <td width="25%" align="center"><img src="docs/screenshots/monochrome-dark.png" width="200" alt="monochrome-dark"><br/><b>monochrome-dark</b></td>
    <td width="25%" align="center"><img src="docs/screenshots/noir.png" width="200" alt="noir"><br/><b>noir</b></td>
    <td width="25%" align="center"><img src="docs/screenshots/swiss.png" width="200" alt="swiss"><br/><b>swiss</b></td>
    <td width="25%" align="center"><img src="docs/screenshots/tech-dev.png" width="200" alt="tech-dev"><br/><b>tech-dev</b></td>
  </tr>
</table>

## Why cvmake

You have a CV. You want to keep it in version control, render it to multiple templates,
maintain it in two languages, and not pay $9/month forever for the privilege. cvmake does that.

- **One YAML file is the truth** — diff in git, search with grep, copy between machines.
  No Word document mystery formatting.
- **12 polished templates** — academic, bauhaus, classic-serif, corporate, creative-accent,
  editorial, magazine, modern-minimal, monochrome-dark, noir, swiss, tech-dev — each with
  multiple color palettes. Same content, instant restyle.
- **Multilingual by default** — author `cv.de.yaml` + `cv.en.yaml` side-by-side from one
  schema, switch via CLI flag.
- **High-fidelity PDF output** — the browser preview and the PDF run the same React
  components, the same template CSS and the same vendored fonts, so what you arrange is
  what you get. They are not byte-identical: the preview is a live DOM, the PDF is a
  Puppeteer print render, and only the second one paginates.
- **CLI or browser** — `npx @codevena/cvmake-cli build cv.yaml` for terminal users,
  [the live editor](https://cveditor.codevena.dev) for everyone else.
- **MIT, no lockin** — your data stays on your machine. Fork the schema, fork a template,
  add your own. The project is small enough to actually read.

## Quickstart

### Install + render in one shot

```bash
# 1. Scaffold a commented starter CV (cv.yaml)
npx @codevena/cvmake-cli init cv.yaml

# 2. Edit cv.yaml with your data, then render it
npx @codevena/cvmake-cli build cv.yaml
```

No clone required. `init` drops a ready-to-edit, schema-valid `cv.yaml`
(use `--lang de` for German). The first `build` downloads Chromium
(~150 MB, one-time) which is needed for high-fidelity PDF rendering.

### Already have a JSON Resume?

Convert an existing [jsonresume.org](https://jsonresume.org) file and get all
12 templates instantly:

```bash
npx @codevena/cvmake-cli import resume.json cv.yaml
npx @codevena/cvmake-cli build cv.yaml
```

### Or clone for contribution / customization

```bash
git clone https://github.com/Codevena/cvmake
cd cvmake
pnpm install
pnpm build      # builds the workspace packages once

# Copy the example to your local-only CV (cv.*.yaml is gitignored)
cp data/cvs/example.de.yaml data/cvs/cv.de.yaml

# Render a PDF
pnpm cvmake build data/cvs/cv.de.yaml
```

Output PDF lands in `out/cv.pdf` by default.

## Templates

| ID | Style |
|---|---|
| `academic` | Serif, two-column publication-style layout |
| `bauhaus` | Geometric shapes, primary palette, Futura |
| `classic-serif` | Traditional resume with serif typography |
| `corporate` | Restrained corporate single-column |
| `creative-accent` | Colored accent block, modern sans-serif |
| `editorial` | Magazine-style with strong typography |
| `magazine` | Display serif, italic, two-column body — Vogue-style |
| `modern-minimal` | Minimal, lots of whitespace |
| `monochrome-dark` | Dark theme, high contrast |
| `noir` | Cinematic dark, cream serif, gold accent, prose entries |
| `swiss` | Strict grid, Helvetica, red accent — pure information design |
| `tech-dev` | Developer-focused with code-style accents |

Each template ships with two to four color palettes — 34 across the twelve. List them all:

```bash
pnpm cvmake list-templates
```

## Tech Stack

- **Monorepo** — pnpm 9 workspaces + Turbo
- **Schema** — Zod
- **Rendering** — React 18 + Puppeteer (headless Chrome → PDF)
- **Web UI** — Next.js 16 (App Router) + Tailwind CSS 4
- **CLI** — Commander 12
- **Testing** — Vitest, Playwright (e2e), visual regression via pixelmatch

## Releasing

(Maintainers only.) All 4 published packages bump in lockstep:

```bash
pnpm -r --filter "@codevena/cvmake-{cli,core,schema,templates}" \
     exec pnpm version <major|minor|patch>
git add -p   # review the version bumps
git commit -m "release: vX.Y.Z"
git tag "v$(node -p "require('./apps/cli/package.json').version")"
git push origin main --tags
```

The tag push triggers `.github/workflows/release.yml`, which first verifies on
Node 20 and 22 (build, unit tests, integration tests, and a pack/install smoke
test against the real tarballs), then publishes all 4 packages.

**Authentication is npm Trusted Publishing via OIDC — there is no `NPM_TOKEN`.**
All 4 packages have a trusted publisher configured (verified 2026-09-09). The
settings live at `https://www.npmjs.com/package/<pkg>/access`:

| Field | Value |
|---|---|
| Organisation/User | `Codevena` |
| Repository | `cvmake` |
| Workflow filename | `release.yml` |
| Environment | *(leave empty — this workflow declares none)* |

The publisher must also permit **direct `npm publish`** — a newly created one
defaults to staged publishing, which this workflow does not use. All four
currently permit both `npm publish` and `npm stage publish`.

Two constraints worth knowing before changing the publish step: `pnpm publish`
cannot do OIDC (support landed in pnpm 10; this repo pins 9.12.0), and
`npm pack` does not rewrite the `workspace:*` protocol, which npm then rejects
on the consumer side. The workflow therefore packs with pnpm and publishes the
resulting tarballs with npm — and it packs exactly **once**: the `pack` job
produces the four tarballs, `verify` smoke-tests those files, and `publish`
pushes the same bytes. `scripts/publish-packages.mjs` checks the tag against all
four manifests, validates every supplied tarball (name, version, no leaked
`workspace:` protocol) before publishing anything, and skips packages already in
the registry, so a partial failure is resumed by re-running the workflow for the
same tag. (It can also pack for itself when run locally without `--tarball-dir`.)

## Contributing

See [CONTRIBUTING.md](CONTRIBUTING.md). Bug reports, template ideas, and pull requests welcome.

See [ROADMAP.md](ROADMAP.md) for what's planned and [CHANGELOG.md](CHANGELOG.md) for what has shipped.

## License

MIT — see [LICENSE](LICENSE).