I’m onto my second set of video lectures on using NextJS 13+ (again, I’ll plug Frontend Masters, which I love, and Scott Moss’s well laid-out teaching style). Recently the concept of route grouping clicked in my brain, so I thougt I’d share it here. As I mentioned in my initial post on NextJS, routing is handled via directory structure (very cool, easy to understand, big fan). Additionally, your project also requires a root layout file that indicates the…well, layout of all child pages.

So NextJS is essentially opinionated React…plus? Okay, I’m listening. I’m running through a great Frontend Masters class to learn the basics of the latest version of NextJS (that’d be 13, with the introduction of the new app directory and removal of the pages directory). It’s been awesome (Scott Moss is not only a great instructor but is a really smart dude in general - check out his LinkedIn someime), but some of the latest changes in the 13+ version of NextJS have made even the latest class already be a touch out of date (example: the head file discussed in the class no longer exists in 13.

I’m blowing the dust off of an old project idea, and I’m finding the many development options avaialable pretty overwhelming. I’m so used to writing code in a preexisting codebase that having the option to choose anything I want and the options themselves feel like a lot for me to sift thorough right now. It’s like trying to pick a brand of toothpaste at the grocery store.

About 10 years ago I used to blog a lot - not about technology or programming, but about baking, actually. I still bake, though I haven’t written about it in years. During that time I learned a lot about baking (obviously), writing, and bit of general photography (gotta have those hot hot baking pics), but I eventually ran out of time to bake as frequently, and thus, writing as much about baking.