KEY DECISION
Model public content, membership, events and support as one permission-aware ecosystem, not a collection of disconnected screens.
2025—NOW
SOFTWARE
SYSTEM / BLUE
01 / CONTEXT
IDTES is not a single institutional website. It is a connected ecosystem spanning public content, membership, events, documents, support and the administrative work required to keep every part reliable.
02 / CHALLENGE
Unify journeys for visitors, associates, secretariat, support and administrators while preserving distinct permissions, payment states, event lifecycles and recovery paths.
03 / APPROACH
A modular Next.js and Node.js architecture connects public information, authentication, member services, plans, events and tickets, declarations, certificates, helpdesk, kanban and chat. PostgreSQL, Docker and role-aware rules keep the product language consistent across interfaces.
BEHIND THE WORK / THREE DECISIONS
WHAT SHAPED THE PROJECT.
WHAT CAME TOGETHER
Information architecture, authentication, operational workflows and administrative tooling share consistent rules and language.
NEXT EVOLUTION
Keep validating critical personas and real production actions, especially access control, payment-dependent flows and administrative recovery.
04 / ROLE
PRODUCT · SOFTWARE · SYSTEMS
05 / STACK
NEXT.JS · NODE.JS · POSTGRESQL · DOCKER
06 / OUTCOME
The resulting platform connects the public site, member portal and operational tooling in one system. The case documents real product areas — including publications, membership plans, event registration, QR validation, certificates and support — without exposing private data or production internals.
