Juleflet Designer

Adding a heart

One SVG in static/hearts/ (with its Danish and English names and descriptions written into it) and one id in hearts.jsonc in the project root, then npm run generate:heart-data — the steps are in docs/ADDING-A-HEART.md.

Similar websites

• Majbrit og Erik Ginnerskov - Anderledes flettede hjerter
• Alt Om Hobby - Skabeloner tilflettede julehjerter
• Gerth Stølting Brodal - Flettede Julehjerter med bogstaver
• Papermatrix - Links til mange andre hjerter
• Johan's Hjerter - wonderfully creative cuts

Testing and release checks

npm test runs application tests and the complete inverse suite, including timed quality benchmarks. To run the inverse release gates separately, use npm run test:inverse:ci; npm run benchmark:inverse:ci runs the advisory cases. The heart generator's regressions that build whole hearts take seconds each and are marked slow; npm run test:slow runs them with the rest of the generator's tests, and the deployment workflow leaves them out.

The deployment workflow requires type checks, lint, application tests, inverse correctness tests and a production build. Fresh image searches with strict wall-clock quality or routing expectations are registered with qualityBenchmark. They run separately with their original budgets and assertions; misses appear in the workflow summary and the inverse-timed-quality-1 / -2 artifacts (kept seven days). They do not block deploying an otherwise valid improvement. A missing or broken benchmark run still fails its reporting job.

Fixed-work geometry, paper connectivity, feature/image-loss and exported-rendering regressions remain blocking, as do the longer functional photo fits. This does not change the application's acceptance thresholds or claim every photo can be solved in ten seconds. The measured old/new comparison and known difficult cases are recorded in the checkpoint study.

License

MIT