- Portfólio
- Open Source
- Projetos Pessoais
- React
- TypeScript
- Vite
- Tailwind
- JavaScript
- Comunidade Dev
- IA no desenvolvimento
- Inteligência Artificial
- Automação
- Mercado de Trabalho
- Vercel
- qualidade de software
- Desenvolvimento Pessoal
- workflow de desenvolvimento
- Privacidade de Dados
- testes unitários
- clean code
- Free Software
- Convex
- Presença Digital
- Freelancer
- Arquitetura de Software
Rubrica
The open-source portfolio that became infrastructure
Every developer reaches a point where LinkedIn isn't enough. You want a space that's yours, that showcases your technical skills, that tells your story. Most people create a simple portfolio, leave it up for a few months, and abandon it when maintenance feels like too much work. I did things differently: I built it three times. And on the third try, the project became something else.
This post tells the story of Rubrica, the open-source portfolio system that I started as a personal portfolio and that ended up becoming, 211 commits later, a complete infrastructure that any developer can fork, customize, and publish.
Why the Third Version of a Portfolio Changes Everything
My portfolio has always been a technical reflection. Each version documented where I was as a developer at that moment: the technologies I mastered, the patterns I preferred, the problems I could solve. The first version was simple, honest in its limitations. The second, more robust. The third, different in essence.
It wasn't planned to become what it did. I started with a simple question: I want a portfolio that has a blog, projects, and a resume, and that I can manage without touching code every time. The obvious answer was an admin panel. And when the admin panel was ready, something changed in the perception of the project.
The turning point wasn't when I added payments. It wasn't when I integrated AI. It was when I created the file management system. At that moment, I looked at the code and thought: any developer could use this. Not as a template, but as a foundation. A solid technical structure that frees you to focus on what really matters: your identity.
That's the philosophy of Rubrica. The foundation is ours, the identity is yours.
This has a name: a living portfolio. It's not a portfolio frozen in time. It's a project that grows with you, that actively demonstrates the technical decisions you make today. When someone visits Rubrica and sees React 19, Convex, Tailwind 4, 472 tests with Vitest, and GDPR compliance, they're not looking at a resume. They're seeing code in production.
What Rubrica Delivers: From Landing Page to Admin Panel
Before diving into the technical decisions, it's important to understand the scope of what the project has built. Rubrica isn't a one-page template. It's a system with complete public and administrative areas.
In the public area, you have:
- Home with hero section, about section, services, testimonials, and availability badge
- Portfolio with project grid, technology filters, detail modals, and image carousel
- Blog with posts, tags, search, and featured content system
- Resume with structured sections and export to ATS-optimized PDF
- Commercial proposals with handwritten digital signature and PDF contract generation
In the admin area, you manage everything without touching code:
- Dashboard with usage statistics
- Complete CRUD for projects, posts, resume, and proposals
- User management with roles
- Audit logs of all actions
- Plugin system with granular control
- GDPR compliance panel with data export and anonymization
- Payment Links via Stripe
- AI Resumes: AI-powered resume rewriting pipeline
There are 11 admin routes protected by authentication. The database has more than 20 tables in the schema. The README has been rewritten as a complete deployment guide: from fork to custom domain in 10 steps.
This answers the question that developers usually ask: "Why so much complexity for a portfolio?" Because Rubrica isn't just a portfolio. It's a work tool.
Technical Decisions: React 19, Convex, and Why I Migrated from Supabase
Rubrica's stack wasn't chosen to impress. It was chosen to work.
React 19 and Vite as a base don't need a long justification: React leads with 41.6% of professional developers in the Stack Overflow Developer Survey 2024. Vite surpassed Webpack in npm downloads in July 2025 and had the highest satisfaction rate in the State of JS 2024. Create React App was officially deprecated in February 2025, recommending Vite as an alternative. The choice is in the mainstream for good reasons.
The backend story is more interesting.
Rubrica started with Supabase. It was the logical choice: structured SQL, ready-made auth, integrated storage, huge community (99k stars on GitHub). It worked. The problem wasn't technical, it was philosophical.
In the middle of development, I started using Convex in other projects. And I realized something: Convex fit exactly into Rubrica's intention. To be simple. To be easy. To be a system that even a beginner can deploy.
The migration was long and arduous. It required dozens of tests and checks. But the result was worth it: a complete deployment became as simple as an npm run build. Convex takes care of the reactive backend, real-time, storage, and server-side Actions. You don't need to configure a database, you don't need to manage connections, you don't need to think about initial scalability.
In terms of performance, Convex sustains latency below 50ms in reading and writing. Supabase, under similar load, reaches 100-200ms. But the decision wasn't based on benchmarks: it was based on alignment with the project's mission. Convex open-sourced in February 2025. With 10,000 stars today, it's an early adopter bet. Rubrica is exactly that kind of bet.
The rest of the stack follows the same pragmatic logic:
- Tailwind CSS 4 for styling, with CSS variables and controlled theme
- Wouter for lightweight routing, without the overhead of React Router for the project's scope
- TanStack Query for caching and data fetching
- TipTap for the blog's rich text editor with complete extensions
- React Hook Form + Zod for forms with typed validation
- jsPDF + signature_pad for PDF generation and handwritten signature
AI with Purpose: Automatic Translation and ATS Resume Pipeline
Rubrica has AI. But not in the way you're used to seeing it.
It's not a chatbot. It's not "content generation." It's not AI for the sake of it. It's AI where it makes sense for the professional.
The first case is automatic translation via OpenRouter. The problem: maintaining a portfolio in two languages manually is double the work. Each text field, each blog post, each project description would need a version in pt-BR and en-US. Rubrica's solution is to automate this pipeline: you write once in Portuguese and the system automatically translates it into English. Internationalization without the maintenance cost.
This matters more than it seems. Retrofitting i18n into an existing codebase is significantly more expensive than planned from the start. For a solo developer, the entire pipeline, code, design, translation, and review, falls on a single person. AI specifically solves this bottleneck.
The second case is more impactful: the ATS-optimized resume pipeline.
Here's the real problem: almost all large companies use Applicant Tracking Systems to process applications. 97.8% of the Fortune 500. 90% of companies with more than a thousand employees. And 66% of these systems can't interpret synonyms: the keywords need to be exact. Candidates are 6 times more likely to get an interview if they personalize their resume for the job.
Rubrica has a three-step pipeline to solve this:
- Gemini analyzes the job description and extracts keywords and ATS requirements
- GPT scores the current resume against these requirements
- Claude Sonnet rewrites the resume incorporating the keywords without losing authenticity
It's not to trick recruiters. It's to ensure that the recruiter's AI doesn't discard a qualified application just because a keyword was missing. The irony of our market: AI is being used on both sides.
Quality as a Value: 472 Tests, GDPR, and Enterprise Architecture
At a certain point, Rubrica stopped being just a portfolio and started having the characteristics of a system in real production. This requires another level of technical responsibility.
The project has 472 tests with Vitest, covering both the Convex functions and the application layer. Tests aren't about numerical coverage: they're about the confidence you have when making a change. When you refactor something in Rubrica, the tests tell you if you broke something.
It has soft delete throughout the system: nothing is permanently deleted, only marked. It has audit logs of all administrative actions. It has rate limiting by IP, XSS prevention with DOMPurify, and Content Security Policy headers configured.
It has GDPR compliance: export of personal data, anonymization, and granular control over what is collected. For a personal site, this may seem like overkill. For a tool that processes contact data, commercial proposals, and customer payments, it's the minimum.
The plugin system is where the architecture gets more interesting. There are 14 plugins with hierarchy, each with granular control through the admin panel. Want to disable the payments module? A toggle. Want to enable Telegram notifications for new contacts? Another toggle. The core of the system doesn't change: you activate what you need.
All of this added together: 211 commits, 66 well-structured dependencies, 20 tables in the schema, a technical reference of 880 lines. Rubrica has the scale of a product, but the soul of a personal project.
Portfolio as Infrastructure: How to Use Rubrica as a Starting Point
I'll be direct about the current state of the project: Rubrica still has the front-end with my visual identity. Fonts, colors, texts, photos. To use it as a base today, you still need to replace these layers manually.
This is changing. The next planned feature is an installation CLI that goes beyond a simple fork:
- Different visual templates to choose from before the first deploy
- Configuration of the visual identity in the initial setup
- Guided setup of environment variables and integrations
The goal is for you to arrive at Rubrica, run the CLI, answer a few questions about your visual identity, and start with a portfolio that's already yours, not a copy of mine.
But even today, Rubrica works as a base. The README has 10 detailed steps from fork to custom domain. The stack is modern and well-documented. The code follows clear patterns: Repository Pattern, Context API, Clean Architecture in the use cases.
"Digital commons describe digital systems and solutions that are owned, developed, and maintained by groups rather than by single individuals or entities, coordinating through peer collaboration rather than pricing or subordination."
— Open Future, "Digital Commons as Providers of Public Digital Infrastructures" (2024)
You don't need to start from scratch. 211 commits of technical decisions, corrected errors, covered edge cases: all of this becomes available when you fork Rubrica. Explore, build on top of it, improve it. The foundation is ours, the identity is yours.
Conclusion
The name Rubrica came after a long time thinking. Rubrica: the signature, the sign that you were here, that the work is yours. I didn't need a name to build, but I needed a name to open it up. When the name arrived, the post arrived together.
Rubrica is the project I built with the most care. Seeing a simple portfolio transform into a system with payments, AI, 472 tests, and GDPR compliance over 211 commits taught me more than any tutorial could. It's my pride and joy.
If you're thinking about creating or renovating your portfolio, fork Rubrica. If you want to contribute, open an issue. If you want to build something on top of it, do it. This project was made for that: sign it with your face.
References
- CoverSentry. "ATS Statistics 2026: Why Your Resume Disappears Into the Void". Accessed 2026-05-20.
- ResumeAdapter. "ATS Statistics 2026: The '75% Rejection' Stat Is Fake. Here's Real Data." Accessed 2026-05-20.
- Select Software Reviews. "Applicant Tracking System Statistics (Updated for 2026)". Accessed 2026-05-20.
- Stack Overflow. "Technology | 2024 Stack Overflow Developer Survey". Accessed 2026-05-20.
- State of JS 2024. "Build Tools". Accessed 2026-05-20.
- Open Future. "Digital Commons as Providers of Public Digital Infrastructures". October 2024. Accessed 2026-05-20.
- Phrase.com. "Internationalization beyond code: A developer's guide to real-world language challenges". Accessed 2026-05-20.
- DevTools Academy. "Supabase vs Convex". Accessed 2026-05-20.
- Convex. "Why I picked Convex over Firebase, Supabase, and Neon for my app". Convex Stack Blog. Accessed 2026-05-20.
- CodeAnywhere. "Vite: The JavaScript Build Tool Dominating 2024". Accessed 2026-05-20.
- Tweag. "The Developer Experience Upgrade: From Create React App to Vite". Accessed 2026-05-20.