PWA journey, Tagline afternoon and dependency disaster

So in these 5 hours you see, some things happened and I’m excited to share the story with you.📖

First, the PWA

So I wanted to make a PWA out of my website and searched around. After a while, I find a plugin that seems just right for me. Little did I know what I had just unleashed here…
I’ve spent a whole day just figuring out what was wrong before ultimately realizing the service worker setup was causing issues, so I decided to revisit this later. I cleaned up, added a normal webmanifest and the logos/icons I had already created and got a non-offline PWA out of it for now (definitely will add offline functionality once I figure out how to write a service worker).🤔

Next, the Tagline Afternoon

So I wanted to change this little text under that big bold “Hey there! Yeah you!” (as seen in the pictures I was successful in the end).
But I had misread one critical piece of information which would devour my whole afternoon. I thought the description option was the place for configuring this little text! (Spoiler: It was the option called tagline)
So I spent hours searching if my OS had trouble updating sites, reinstalling dependencies etc. and gave myself a proper facepalm when you finally see what was right in front of you.😑🤣

Last but not least, Dependency Disaster

So this problem basically followed me through every attempt and changing or troubleshooting something. It thankfully was easy to resolve the remains of this problem though (reinstalling some dependencies and cussing a little at AI for suggesting a deprecated option when I asked about the build error).😌

Conclusion

These were really productive 5 hours I spent here - more or less successful - expanding this project even further. I hope you enjoyed this devlog and I can’t wait for you to join in again. 😉Have a nice day, I’ll see myself out for now!😁

Why I am doing this, manifest update, minor changes

• Added “Why another free course” section to README.md
• Added project banner to README.md
• Added Stardance note in “Achievements” section to README.md
• Removed giscus comments from start page for visual clarity

This is the last post before the first ship. 🥳 I’m so excited! 😬 I’m so glad I got to share the current development process of this project so far in this (and previous) HackClub event(s).☺️

But this project is far from over. I’m looking forward to extending this even further with more content, different styling, functionality, translations etc.🫡

This change focused on theme and comment/suggestion functionality

I added the starlight-giscus plugin to add giscus support, added an edit page to my config file and followed the steps in the docs for applying a custom theme on a starlight page.

Annoying Bug

When configuring the styling for the giscus plugin in the config, the browser wouldn’t switch neatly when switching from light to dark mode when using themes other than plain light and dark –> using default themes for correct switching logic now.

After another 30min of router logic battle I got the images working!🥳 Something with how the routing logic subtracts base subtracted the necessary / too so just added an extra one to make it work. #workaround

Astro 7 transition, markdown rendering hell and a functional result

After some growing pains 😖 with the tools I was using (Starlight + Astro), I finally got this project ready and shipped.
Stay tuned for more devlogs!😉

Quick overview of the changes I made✍️:

• Added social links
• Astro 7 transition
• Removed duplicate titles

I worked on the existing project (was already part of flavortown).😄

• Added an update to the manifest regarding a migraton to another static site generator.
• Added a lesson in section 2-language-specific-lessons where I detail my new project - a Java course which is based on the same principles as this course - and describe what it’s for.

Short version

Migrating from Material for MkDocs to Astro Starlight.

Look forward to:

Migration post where I detail the experience with the migration going on in the background!😘