Original Summary

Every workshop and hackathon has the same final boss: “Can we get the certificates by tonight?” 😅 Then begins the traditional ritual: duplicate a design, change one name, export, repeat… and quietly wonder whether anyone will notice the typo in certificate #47. I started building a small fix for that problem. After lots of JOMFS — Just One More Feature Syndrome — it became something more. 🔧 A name field became a visual certificate editor. A CSV upload became bulk generation. A download button became issuance to each student’s own account. And, naturally, certificates needed QR codes, public verification, and revocation status. That project is now open source: Certifier — a tool for designing, issuing, and verifying certificates. What it can do Upload a certificate design or import one from Canva Place text, logos, signatures, and QR codes in a visual editor Generate certificates in bulk from a CSV Deliver certificates to the right student via email or roll number Let anyone verify a certificate through a QR code or public code Show whether a certificate is valid or revoked Tech stack Backend: Django Task processing: Celery Frontend: Next.js License: AGPL-3.0 Run docker compose up and you can have a working setup with demo data in a few minutes. Explore the code Backend: https://github.com/Shantanu700/certifier_reloaded_backend Frontend: https://github.com/Shantanu700/certifier_reloaded_frontend I'd love contributions: bug reports, fixes, documentation, feature ideas, and feedback from anyone who has had to survive certificate season. 💬 I'm especially interested in feedback on the architecture, verification workflow, and features that would make this useful for colleges, workshops, and hackathons. If you've built something similar or dealt with certificate generation at scale, I'd love to hear how you approached it!   submitted by   /u/Unknown_4nonymous [link]   [comments]

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/20 13:05:21