Files
templates/blueprints/erpnext/meta.json
Mauricio Siu c3de62fb83 feat: per-template metadata — eliminate meta.json merge conflicts
- move each template's metadata to blueprints/<id>/meta.json (442 files, byte-identical roundtrip with the old root meta.json)
- generate the served meta.json at build time into app/public/meta.json (gitignored); pnpm dev/build run the generator first
- CI validates every blueprints/<id>/meta.json via generate-meta.js --check (required fields, id/folder match, logo exists, folder<->meta bidirectionality) and rejects any committed root meta.json
- remove root meta.json, dedupe-and-sort-meta.js and build-scripts/process-meta.js (obsolete)
- update CONTRIBUTING.md, AGENTS.md and README.md

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-07 23:58:10 -06:00

22 lines
436 B
JSON

{
"id": "erpnext",
"name": "ERPNext",
"version": "version-15",
"description": "100% Open Source and highly customizable ERP software.",
"logo": "erpnext.svg",
"links": {
"github": "https://github.com/frappe/erpnext",
"docs": "https://docs.frappe.io/erpnext",
"website": "https://erpnext.com"
},
"tags": [
"erp",
"accounts",
"manufacturing",
"retail",
"sales",
"pos",
"hrms"
]
}