Case StudyPrivate source2026

FATEC Digital Platform

A production Django education web platform that unifies institutional content, admissions, public-service registration, candidate administration, and direct boleto access.

Role:Freelance product engineering — discovery, design, full-stack implementation, and operations

  • Python
  • Django
  • HTMX
  • Alpine.js
  • Tailwind CSS
  • PostgreSQL
  • Banco do Brasil

Problem

Institutional publishing, admissions, public-service applications, candidate support, and payments were split across manual processes and disconnected pages.

Constraint

The system handles personal and payment data, multiple institutions, deadline-driven public notices, and non-technical administrators while its source remains client-confidential.

Decision

Built a server-rendered Django platform with focused HTMX and Alpine.js interactions, a tailored Unfold administration workspace, private media controls, and Banco do Brasil Cobranças integration.

Outcome

Candidates can register and access their boleto directly in the product, while staff manage notices, applications, documents, status changes, and reconciliation from one operational system.

Registration → boleto in product

Candidate journey

Public site · candidate area · admin

Operational surfaces

Banco do Brasil Cobranças

Payment path

Overview

The FATEC platform is more than an institutional website. It combines public content and course information with operational workflows for admissions, public-service registrations, candidate documents, administration, and payments.

Product decisions

Server-rendered Django keeps sensitive workflows cohesive and auditable. HTMX and Alpine.js add interaction without turning every screen into a separate client application, while the Unfold-based administration area gives staff task-oriented views instead of exposing raw database records.

The payment flow treats email as cadastral data rather than a delivery dependency: after a valid registration, the candidate can access the generated boleto directly in the interface. Banco do Brasil integration, reconciliation, private document storage, and controlled status transitions stay behind the server boundary.

What I built

  • Institutional publishing, courses, news, units, and public contact journeys.
  • Candidate registration, document submission, status tracking, and protected self-service.
  • Administration for notices, roles, applications, exemptions, special-service requests, and payments.
  • Banco do Brasil Cobranças boleto issuance and reconciliation.
  • Deployment and operational safeguards for PostgreSQL, Redis, Nginx, Gunicorn, and scheduled reconciliation.

Source availability

This is client work in production. The source repository is private; the public case study focuses on product scope, architecture, and non-sensitive operational decisions.

Next step

Have a system to build or a process to fix?

Tell us about the problem. You get a first technical read, a suggested path, and next steps.