Hello everyone!
I'm Gio, and welcome to my very first newsletter/post. I've spent a significant amount of time in the tech world, and while I have a ton of enthusiasm for coding & sharing knowledge, writing isn't necessarily my strongest suit. So, take it easy on me!
Given that you've either followed my journey or are just stumbling upon this newsletter (if you haven't subscribed, please do đ), you might already be aware that I am working on a course platform. This platform is designed to be the home for my past work, like âLearn PHP The Right Wayâ, and a foundation for what's to come, such as âLearn Laravel The Right Wayâ. Now, if you're curious about my decision to build the platform from scratch instead of using an existing one, here's whyâŚ
Great Learning Experience: There are some new things that Iâm learning while building this. I'm diving into areas previously unfamiliar to meâlike building in public, getting into Inertia.js, Framer Motion, and sharpening my UI/UX skills, to name a few.
A Unique Experience: While I don't want to spill all the beans just yet, I envision my platform as more than just a space for tutorial videos. Learning is a journey, an adventure, so taking a course should feel that way.
Building in Public: I'm embracing the "build in public" philosophy. It's an exciting journey, and I'd love for you to be a part of it.
So, as part of this post, letâs dive into the tech stack Iâm using to build the platform and why I chose it.
The Tech Stack:
Laravel PHP: I love PHP & I love Laravel. Plus the first course Iâll be hosting on this platform is about Laravel, so makes sense to build the platform with it.
Inertia.js: It integrates React seamlessly into the Laravel app.
React: My go-to choice for building UIs.
Tailwind: I donât have strong UI or design skills; this is where Tailwind & Tailwind UI come to the rescue.
Figma: For some graphic design needs.
Why Inertia.js and not the usual Laravel API + React combo? You might wonder why I opted for Inertia.js instead of the Laravel API and a React front-end like Next.js. There are a few reasons:
Familiarity with React: Having a history with React, it has always been my tool of choice for building user interfaces.
Desire to Learn Inertia.js: I've been eyeing Inertia for a while now. The way it bridges the gap between Laravel and client-side frameworks (like React) is pretty cool. This project presented the perfect opportunity to dive in and learn.
Seamless Integration: The blend of Laravel and React using Inertia has been surprisingly smooth. While there have been nuances (more on that in future updates), the overall experience has been pleasant.
React over Vue or Livewire? The debate between React vs. Vue is eternal, and I donât really want to get into that. While Vue has its merits, my decision was based on familiarity. Iâm just more productive when coding in React. Iâm learning enough new things while working on this project, so I donât want to overwhelm myself. The same reason applies to the decision of not using Livewire. That said, I'm always open to trying new things and might explore Vue or Livewire for other projects in the future.
I'm really excited about this project & will keep you updated as the platform takes shape. Expect more weekly updates right here in this newsletter. In the spirit of building in public, I've been sharing sneak peeks on X (aka Twitter), particularly showcasing the quiz portion of the platform. If you're curious to see it in action, check out this post.
Feel free to share your thoughts, feedback, or even just a word of encouragement. Building this platform is a journey, and having you alongside makes it even more rewarding. Until the next update, happy coding & learning!
im so excited ! ,is it free ?
I will be looking out for the course. I like your videos and how throughly you explain concepts in a compact way.