diff --git a/frontend/src/components/ProjectsText.js b/frontend/src/components/ProjectsText.js index 0e8156a..c65cac8 100644 --- a/frontend/src/components/ProjectsText.js +++ b/frontend/src/components/ProjectsText.js @@ -48,47 +48,59 @@ const statuspage = { sourceURL: 'https://github.com/TwiN/gatus', }; +const lily58pro = { + text: 'Lily58 Pro Keyboard', + url: 'https://wiki.carlossousa.tech/doku.php?id=engineering:computer_science:projects:lily58_pro_diy_custom_keyboard', + sourceName: 'QMK and ZMK Firmware', + sourceURL: 'https://github.com/zebrajr/lily58_keyboard', +}; + function ProjectsText() { - return ( -
-
+ return ( +
+
- {titleText} + {titleText} - {subTitleText} + {subTitleText} - Let's start by the quickest, simplest (and one of the most useful for multiple reasons) - A {statuspage.text}. A {statuspage.sourceName} instance so I know if everything is running at a quick glance and to inform others (and myself) of all the services that I host and run, or at least the ones that are meant to be easy to find. + Let's begin with one of the most useful projects - a {statuspage.text}. This {statuspage.sourceName} allows me to quickly check the status of my hosted services and provide transparency to others. - So, one of the many things I enjoy having (mostly for me, to be fair) is my {wikipediaData.text}. Nothing fancy, just hosting {wikipediaData.sourceName} so I can keep some notes, references (maybe some guides?), and just random thoughts. + As a hardware and software enthusiast, I've built two {lily58pro.text} - a wired version for home use and a wireless one for work. The {lily58pro.sourceName} is available for those interested in creating their own Lily 58 Pro Keyboard variant. + + + I maintain a personal {wikipediaData.text}, primarily for my own use. This {wikipediaData.sourceName} serves as a repository for notes, references, guides, and random thoughts. - I also host this {traveltracer.text}, source code in {traveltracer.sourceName}. A one-page application that shows Markers on a rendered GeoJSON file with Leaflet, to display a few of the places I either visited or want to visit. + I've also developed a {traveltracer.text} - a single-page application using Leaflet to display markers on a GeoJSON file, showcasing places I've visited or wish to explore. The source code is available on {traveltracer.sourceName}. - I also run an {archiveData.text} where I keep articles that I either reference or enjoy re-reading, and don't want them to be lost due to the natural state of the internet. In case you want to have your own, it's called {archiveData.sourceName}. I have my issues with it, don't get me started on the topic. + My {archiveData.text} preserves articles I want to reference or revisit, preventing them from being lost to the transient nature of the internet. Powered by {archiveData.sourceName} (though I have my reservations about it). - I'm also hosting a calculator, {reactoCalcData.text}. Source code also available in {reactoCalcData.sourceName}. It's a simple calculator that is useful for specific situations, mainly financial ones. Nothing fancy, just something that was put together (semi-)quickly. + I host a specialized {reactoCalcData.text}, a calculator designed for specific financial scenarios. The source code is available on {reactoCalcData.sourceName}. - I'm still hosting a {tornIndexerData.text} for {tornIndexerData.sourceName}. I honestly stopped using it, like, 1 month after I finished the Proof of Concept (PoC), but some players still use it, so, guess it stays up. If for whatever reason you are interested in it ( don't code shame me :( ), you will find the Source Code on my GitHub. + I'm still maintaining a {tornIndexerData.text} for {tornIndexerData.sourceName}. Though I stopped using it shortly after the Proof of Concept (PoC), some players continue to find it useful. - I also host a few more services, but either I don't want or can't share publicly. + Several additional services remain undisclosed due to privacy or confidentiality reasons. - Among other services that I either prefer not to disclose or cannot share publicly, I also manage a HomeLab. -
It includes a Proxmox setup with VMs and containers, 3-2-1 backups, and more, mostly for the purpose of experimenting with "Linux ISOs," learning, and testing. + My HomeLab is a comprehensive setup that includes: +
• Proxmox with VMs and containers +
• 3-2-1 backup strategy +
Primarily used for experimentation, learning, and testing.
- These projects represent a blend of both personal enjoyment and practical utility in my tech pursuits. + These projects reflect my passion for technology, balancing personal curiosity with practical innovation. -
-
- ); +
+
+ ); } export default ProjectsText;