Glad it was helpful! I'm the same way; I prefer grid over flex in most scenarios even if it's just 1 row, but for any kind of complexity of counting and placing based on grid lines... it becomes rocket science in my brain; so glad to have Penpot for those situations. I hear you on the class names. I think if you name the layers Penpot will use the layer name in the classes / selectors, but still, I think getting immediately usable paste'able code from the export feature is hard because like you mentioned how it renders to the canvas. And I'm not sure there's a way to get that perfect because the software still lets designers drag and drop and position things "absolutely" instead of doing things exclusively with flex and grid like I did in the video. Maybe it's good that it's almost an unsolvable issue; it's extra bonus job security lol.

I've been enjoying it. I did run into some performance issues in Safari, but in Chrome it's silky smooth.

Yes! Next is my "next" new course, but I've been focusing on updating all of my existing courses first. When I get caught up, Next.js is the next new course I wan to release on Udemy & Teachable.

I do have a tip because I've been there myself. I'd stop trying to learn the basics or "make sure you have the technical fundamentals" down because that could be a never ending never "good enough" task. I'd focus on building a usable web app for the next month or so. But here's the important part; it can't be one from a tutorial or course, but one that is your own idea that's different from any tutorial you've seen. This way, you'll feel ownership over the project, and you'll be problem-solving solutions to your app instead of "troubleshooting tutorials" - instead of frustration you'll be building confidence. I've taken some amazing courses over the years, and they're like a road map, which is necessary, but all of my actual confidence building comes when I finish the course and go build something by myself. Keep a notes / text file where you keep track of which features you still need to build, which experiments you need to try, which bugs you need to fix, and just keep working on the project as you get time. Eventually you'll finish it, and seeing the working finished project is like physical evidence that tells imposter syndrome to be quiet; that what you know is "enough" and that you built something worthwhile with your code knowledge.

@@LearnWebCode thanks a lot for the info 😊