Contribute

Design a template.
Ship it to the world.

temploracraft's template marketplace is open. Design a template in the canvas, publish it via GitHub, land in the gallery on the next redeploy. MIT-licensed, credited to you, free forever.

Start designing →Write JSON directly ↗

Three steps.

Community templates are what makes the gallery interesting. Yours will live at app.temploracraft.com/templates as soon as the PR merges.

01
Design
Open the canvas author tool. Drag placeholders (fullName, experience[].title), tune typography, decide on layout. You’re composing flexbox sections + text nodes; the tool writes valid template.json for you.
02
Publish
Click Publish. Connect your GitHub (a scoped public_repo token, one click). The tool forks vineethpawar/temploracraft-templates, creates a branch, writes your template.json + README.md, and opens the PR on your behalf. Prefer no OAuth? Level-2 fallback opens GitHub’s file editor pre-filled with your JSON.
03
Merge
CI runs the Zod validator + auto-renders your preview.png via satori/Playwright. A maintainer reviews (usually within a day) and merges. Your card appears in the gallery on the next redeploy — credited to your GitHub profile, MIT-licensed, free forever.

The deal

Community is free. Curated is Pro.

Everything the community submits stays free forever. The only paywall is the small curated set Vineeth hand-designs and iterates on — those land as Pro-only. If your submission is exceptional and the maintainer wants to promote it into the curated library, you’re credited on the pricing page and get a Pro comp indefinitely (see the pricing FAQ).

MIT-licensed
Your template stays open for anyone to remix, fork, or build on.
Credited
Gallery card + detail page link to your GitHub profile.
No lock-in
Delete the PR any time before merge; the template is entirely yours.
Same schema as first-party
Community and premium templates go through the same validator and render pipeline. No second-class citizen shape.

What tends to get merged fast

A clear archetype

"Recruiter-friendly one-page" is a pitch. "Another modern-ish resume" isn't. Say what your template is for and what it's not.

Typography that reads

One or two fonts, deliberate weights, actual line-height tuning. If your first version looks like the Google Docs default, iterate before opening the PR.

Graceful empty state

Use visibleIf so sections without data (empty summary, no education) collapse cleanly instead of leaving a stray heading.

ATS-scannable

Most people PDF this and upload to a job portal. Templates that survive a plain-text extraction pass do materially better in the real world.

Schema in one glance

The author tool writes this JSON for you — but if you’d rather hand-author, this is the shape.

{
  "version": 1,
  "domain": "resume",
  "slug": "my-template",
  "name": "My Template",
  "description": "One-sentence hook that shows up on the card.",
  "author": {
    "name": "You",
    "url": "https://your-site.com",
    "githubUsername": "your-github"
  },
  "license": "MIT",
  "page": { "width": 816, "height": 1056 },
  "fonts": [
    { "family": "Inter", "weights": [400, 700], "source": "google" }
  ],
  "root": {
    "type": "section",
    "layout": "flow-vertical",
    "padding": [64, 72, 64, 72],
    "gap": 28,
    "children": [ /* nodes */ ]
  }
}

Full type definitions: src/types.ts ↗ · Zod validator: src/zod.ts ↗ · Full guide: CONTRIBUTING.md ↗

Ready?