Origin

This portfolio exists, first and foremost, as a living space. What you’re reading right now is temporary by design. It’s here to set the tone, but not to say everything. We know this section will evolve, expand, and probably be rewritten more than once — and that’s perfectly fine. The idea is to slowly turn this into a place where we can properly explain what we do, how we think, and why we build things the way we do.

There’s a lot we want to talk about.

For example, the choice of typography. The main font used here is Montserrat, and that’s not accidental. It was designed by an Argentine designer, Julieta Ulanovsky (another coronación de gloria), and it carries a very particular balance between modernity, clarity, and personality. We’d love to go deeper into why typography matters so much to us, how it shapes perception, and how it affects the way content is read and felt.

We also want to dedicate proper space to talk about architecture — not just in terms of code, but in terms of structure, scalability, and long-term intent. The same goes for design decisions and the overall purpose of this portfolio: what it represents, who it’s for, and how it connects with the projects showcased here.

Technically speaking, this portfolio is built with Astro, which gives us the flexibility to keep things fast, content-focused, and clean. Writing content in Markdown lets us move quickly and focus on ideas rather than tooling, while still leaving room to grow into something much more powerful.

This is only the beginning.

Roadmap

• Launch the portfolio in production (if you’re reading this at the bottom of the page, then yes — it’s already live).
• Enable the blog section, where we’ll write more structured and in-depth posts.
• Open the space for rants — shorter, more opinionated, less polished thoughts that still deserve a place.
• Add a CMS for internal use, so we can manage content more comfortably as the project grows (even though everything is currently written in markdown).