// contribute
Add a model or a post
The site is file-based on purpose. Every model, FAQ, news post and guide is a typed file or an MDX file in the repository. No CMS, no database.
Add or update a model
Edit data/models.ts. One typed object per model, with a real Hugging Face URL.
Publish news
Drop a new .mdx file in content/news/. Commit and redeploy.
Write a guide
Add a step-by-step .mdx file in content/guides/ with frontmatter.
Update an FAQ
Edit data/faqs.ts. Keep answers short, practical and neutral.
Models — data/models.ts
Models are a typed array. The UI never hardcodes model cards, so a new object appears in the catalog, search index, sitemap and Markdown output automatically.
- 1. Verify the source. Open the Hugging Face repository. Confirm the base model, method, license, available quants and approximate VRAM at Q4. Do not invent download numbers or VRAM figures.
- 2. Add one object. Use the existing entries as a template. Required fields are
id,name,baseModel,family,size,method,quants,approxVRAM,license,hfUrl,downloads30d,tags,descriptionandlastUpdated. - 3. Refresh the numbers. Run the helper script, then review the diff before committing:
pnpm refresh:modelsAdd --write to update downloads30d, likes and lastUpdated from the Hugging Face API. Entries that 404 are reported and left untouched. Review every change; the API is a source, not an oracle.
abliteration, heretic, heretic-ara, fine-tune, other. Family values: Qwen, Gemma, DeepSeek, GLM, Llama, Other.News — content/news/
Create one .mdx file per post. The filename becomes the URL slug. Use a date prefix for readability: 2026-11-22-some-release.mdx → /news/some-release.
You can scaffold the file and frontmatter with the script:
pnpm new:post --type news --slug "some-release" --title "Some release"Or create it manually. Frontmatter:
--- title: "Your title" date: "2026-11-22" description: "One or two sentences for cards, search and SEO." tags: ["qwen", "abliterated"] cover: "/covers/abliteration.svg" # optional draft: false ---
cover is optional. Use one of the SVGs in public/covers/ or add your own. draft: true hides a post in production builds; drafts remain visible in local development.
Guides — content/guides/
Same frontmatter and script, different folder:
pnpm new:post --type guides --slug "ollama-on-mac" --title "Ollama on macOS"Prefer step-by-step instructions. Mention Ollama and LM Studio or llama.cpp when relevant. Include a hardware note and a short troubleshooting section. Keep responsibility notes high-level and neutral.
FAQs — data/faqs.ts
Each entry has id, question, answer (Markdown), tags, optional source and lastUpdated. The id is the deep-link anchor: /faq#your-id.
Cover practical questions only. If an answer depends on hardware, give a range and explain the variables instead of a single number.
Before you open a pull request
pnpm installpnpm lint && pnpm typecheck && pnpm buildThe build validates frontmatter, generates every static page, and will fail on a missing title, an invalid date, or a broken type. If the build passes locally, it will pass in CI.