Links
Why? What?
This portfolio exists as a living space to document the projects and ideas we do together as LyT. It’s for the people that want to see what we’re up to, what we built, some things we care about, or want to know more about how a project was conceived. -> Talking as Luk, kind of how https://mitxela.com/ does it, he and his site were great inspirations for me, he does great stuff.
Most of the stuff is written by both of us and in behalf of both of us, but occasionally we may slip some comment or note like I (or him 👀) just did.
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. And to do it in a transparent way and sharing the process, not just the results. That’s why across this site you may find roadmaps or to-dos or things we are discussing if to do in some way or another.
About the site
Projects and plain text
The site is built upon markdown files and yaml headers that are rendered by our site as project entries. It’s done in that way so that everyting is versionable with git, easily editable and may be rendered by standard tools if we wish. Also the future-proofing plain text gives you is unrivaled, so we really like it as a medium for a lot of stuff, including this content. The idea is to use the same plain-text project catalogue for our internal management of projects and for publishing here in the Portfolio, so that each tool reads the data it needs, as a diferent view for the same elements.
If we add custom kinds of markup (for example for roadmap entries or adding comments/anotations), we intend to make them human-readable, easily parseable and well documented, and try to lean towards existing practices when we can. All data relevant to a file should be there, plain and simple, and databases should be indexing and retrieval systems, making it possible to do complex computations and querys, but not being the source of truth. That as a general philosophy is a topic to talk in a blog maybe, and also it’s limitations #todo
Design
We wanted that standarized way of writing about our projects, but also we wanted a custom personality and feel for each project, so we decided adding options in the metadata for defining a custom color pallete for each project, that would be used for highlighting and visual elements, and a custom poster/banner that can have whatever aesthetic the project has. That’s because we have kind of a tradition of giving our projects weird visual identities that we like to respect and play with (Like PinkOS for instance). Also the color details in the project list and ctrl+k look really cool and help identify each project.
About the choice of typography, the main font used here is [Montserrat](https://en.wikipedia.org/wiki/Montserrat_(typeface), it’s a really popular sans-serif font, but mainly, it’s from our motherland Argentina, from designer Julieta Ulanovsky and inspired by the Montserrat neighbourhood (another coronación de gloria 😎).
Inspiration and contents
We want to talk about whatever we care about, kind of like a blog, but also like the deeply linked non-hyerarchical network of connected notes people do in Obsidian or OG Andy Matuschak in his notes.
#todo Should this go here or in some kind of “about” page? like, it’s more about we and what we want than about the Portfolio as a project. Maybe there’s some overlap, not sure what to do in those cases.
Roadmap
- Launch the portfolio in production (if you’re reading this from the site, then yes — it’s already live lol).
- 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).
- Add a way of adding “editor comments” to parts of the text so one of us can personally add something or comment on what was said