We all know the CSS blinds meme, right? Or the CSS is Awesome text that exceeds the box? These seem to appeal to many developers these days, perhaps even more than in the past. We've started leveraging JavaScript or TypeScript-oriented frameworks and features, while relying on Tailwind to help us style our interfaces.

We've drifted away from one of the main pillars of the web: CSS is not a main focus anymore but an afterthought—something to slap onto a bit of interactive code. Leaning on these frameworks can lead to lower maintenance and more up-to-date knowledge of CSS.

Vue adopted a Single File Component philosophy, which has some benefits over splitting concerns, which you can read up on in the official Vue Docs. From a SFC philosophy, you’d want everything that relates to your component in a Single File. So let’s explore this take with our component tests as well, because why would your tests be any different than your scripts, template or styles?

We’re going to leverage a feature that Vitest offers, out of the box, to a Vue example code base. Bear in mind that this approach would be applicable to other implementations that leverage Vitest just as easy. Also, this is a thought experiment.

Software development is a craft and we can follow many routes to achieving a specific goal. Having this freedom allows us to create simple solutions for very complex problems. That same freedom has a flip side, where very complex solutions can be applied to very simple problems!

To be clear: I don't think anybody purposefully sets out to create complex solutions to simple problems (unless part of an artistic discovery). I think it is a sign of lack of understanding of a certain domain or technology. I also think there are several strategies you can apply to reduce complexity!

As the year draws to a close, it is an opportune time to contemplate the accomplishments of past years in order to gain a better perspective. Looking back on my achievements, I feel a sense of pride and gratitude for all that I have accomplished, with the help and support of those around me.

This year, many things that were previously in progress seemed to fall into place, leading me to pursue a new career direction that focuses more on engaging people rather than code. This is a path that is better suited for me at this stage in my career.

If you've followed the series in setting up a Contentful powered Nuxt blog, you have a decent amount of routes in place. To wrap up everything related to routing, let's add a formatted error page, for a 404 status code.

Now that we have some content exposed, it might have occurred that it's not really anything useful for a visitor. We're getting a JSON shape from the Contentful API, so let's make turn that into HTML markup using the tools that Contentful provides.

In previous parts we've already established a connection to Contentful, but it's a static setup. In this step we'll be mapping a route to a page, which allows for more creativity and less manual maintenance.

So far we have two unconnected systems. So in this post, we're going to connect them to read from the Pages, Articles and Tags. We're first just going to add all of the utilities and helpers that we'll need. We're going to create a Nuxt plugin and some composables.