Summary:
Organizations can use Quick Certify as a product to issue certificates to their people. For example, when an organization conducts a training session and wants to issue participation certificates to people, it can use Quick Certify to do that. One of the example is here.
https://credsverse.com/credentials/cf187b96-aa06-4aff-af72-16b9de3e8769
Quick Certify can be used not only by companies but also by various other stakeholders. For example, influencers or online tutors teaching online classes can also use this. Additionally, features are not only limited to issuing certificates but can also be expanded to issue badges, appreciation tokens, etc.
It also gives recipients a place to store their certificates for future use. In typical cases, these certificates get lost.
Problem we are solving
- At Crownstack, we want to issue certificates to our employees for the various events we organize. Therefore, we are fulfilling a long-held desire.
- Although we feel this product can be used by other companies as well, we are creating this as a multi-tenant SaaS-based application.
- This product will be built in such a way that it can be integrated with various systems, like third-party applications like LMS, HRMS via APIs.
Technical Architecture
- This will be a multi-tenant application where multiple organizations can register themselves and use the feature independently without exposing their data to other organizations.
- We are using Next.js, Nest.js, Typescript, Tailwind CSS, Postgres Database, Sequelize ORM, and Docker in a monorepo setup.
- The design will be built using Tailwind CSS, mainly Flowbite and Tailwind UI. We are not wasting time to create components on our own and will rely mostly on Flowbite.
- Testing will be done using Playwright; only E2E testing will be the main focus.
Tooling and access
- Code is open source and can be accessed from https://github.com/cs-quicklabs/quick-certify