
Omlaty
Gallery
Select a screen to enlarge
Summary
Backend for a coin marketplace and numismatics platform: catalog, store, academy, exams, forum, and blog on one NestJS API.
Overview
Omlaty is a backend for a coin marketplace and numismatics platform. Clients browse and buy coins, study a catalog, take courses and exams, and use a forum and blog. Admins run the catalog, store, academy, community, and site content. All routes sit under api/v1. The API is NestJS with PostgreSQL through Prisma and Redis caching. Clients and admins log in separately, both with JWT access tokens and refresh tokens. Email handles account activation and password reset. Firebase Cloud Messaging sends push notifications. A background queue imports catalog rows from Excel, and uploaded files are served from a files endpoint. Admin routes use a permission guard: READ, WRITE, and DELETE map to HTTP methods, and the SUPERADMIN role skips that check. A client signs up, activates, then browses the catalog or store, saves favourites, buys a coin or a course, studies lessons, takes exams, posts in the forum or blog, and collects points and badges. An admin keeps the catalog accurate, including client submissions and Excel import, manages stock and orders, builds courses and exams, moderates the community, and updates the public pages.
Technologies
Features
Clients and admins
Clients sign up, activate by email, and can log in with email or Google. A profile holds an avatar, bio, and addresses, plus a public profile and a status of active or blocked. Client roles are CUSTOMER and SELLER. Admins log in separately. Roles and permissions are configurable as READ, WRITE, and DELETE. The app seeds one SUPERADMIN from environment variables on startup, and that account is hidden from the admin account list. Admins can create, update, block, and delete client accounts, and manage other admin accounts and role assignments.
Catalog
The catalog is a reference library of coins, not the shop inventory. Admins create coins with images for the cover, face, and edges, plus categories, minting houses, versions, conditions, inscriptions, metal, shape, edge, a Gregorian or Hijri calendar, and minting details. Coins can be pending review, published, or unpublished. Clients browse, filter, and open coin details, and can submit their own entries. Admins approve, reject, or edit those submissions. Admins can also import many coins from Excel and check the import job status.
Store and orders
The store is the sellable inventory, separate from the catalog. Admins list, update, and delete store coins, and manage condition grades from G through UNC and stock. Clients filter and view coin details, write reviews, add items to a cart or a favourites list, and check out. Orders cover coins, a single course, or a course plan. Each order tracks payment as pending, success, or failed, plus order status and shipping from pending through delivered, cancelled, or returned. Clients see their own orders. Admins list and open any order.
Collection and academy
A logged-in client can keep a private collection of catalog coins: add items, update notes or details, and remove them. A public profile can show that collection. Admins create course categories, courses with language, level, price, discount, and a publish toggle, plus units, lessons, and lesson sections, and can reorder them. Course plans are monthly, yearly, or forever. Clients browse courses, open units and lessons, leave reviews, and mark a unit or a whole course complete. Completing content awards points. Clients can buy a course or a plan, and purchased courses show on their profile. Admins also publish free learning items that clients can list and open without buying a course.
Exams
Admins create exams, questions, and answer options, publish or unpublish them, and review all attempts. Clients list exams, start one, submit answers, and see their attempts and results.
Forum and articles
Admins manage a forum category tree, moderate posts, handle comment reports as pending, reviewed, or rejected, and see forum statistics. Clients create and edit posts, comment with images, like posts and comments, share, subscribe to topic notifications, and record views. Articles are blog or news, each with its own categories and tags, and are built from text or note sections. Clients and admins can create and edit articles. Admins can publish or unpublish them. Readers comment, like comments, and report comments, and admins review those reports. Reading, commenting, and creating a blog post can award points. A client can mark an article as read.
Points, profiles, and site content
Points come from configurable sources: reading, commenting on, or creating a blog; posting or commenting in the forum; completing a unit or a course. Admins set how many points each action gives and define badges with a name, image, and point threshold. Clients see the badges they have earned, and badges also appear on the public profile. The private profile covers details, password, addresses, avatar or account deletion, activity, and owned courses. The public profile shows posts, blogs, badges, the coin collection, and basic info. In-app notifications support mark-as-read, and push uses device tokens when Firebase is configured. Admins can notify one user, a list, or everyone. Admins edit, and clients read, about us, the team, partner logos, FAQ, contact info and messages, privacy and legal pages, and homepage-style sections for home, academy, forum, blog, store, catalog, and similar pages.