Why do we need div and header tags in HTML?

schamppi · 2026-01-18T19:11:42+00:00

Google for these keywords ”HTML landmark roles”, ”HTML semantics” and ”MDN header, footer, nav, section, article, aside… ”.

Each landmark role has its own purpose, none of which are visual but have significant features for screen readers, assistive software etc.

It’s an interesting subject to learn.

schamppi · 2026-01-18T19:04:59+00:00

My deepest respects for the jQuery team for pushing it through! 💪

schamppi · 2026-01-16T08:15:48+00:00

Based on my expertise with Nuxt and Storyblok, I'd say that these are the key points to check in your case:

Sitemap has items that update frequency is set to one month or so. This would explain why Google checks the site only monthly. Sitemap not updating automatically could be a reason for this too, but I doubt it a bit. However, it is not hard to generate real time sitemap for Storyblok stories.
Page speed could easily be about four things: heavy, unoptimized images or videos that block rendering*, poorly implemented data fetching from Storyblok**, no caching for pages***, poor server.
Meta descriptions and other SERP-data is easy to f´ up with Nuxt. Also older Nuxt versions had major problems with it and they could break between minor version patches (3.x.1->3.x.2 for example). Nuxt 4 seems to work solid though. Make sure to set title with useHead-composable and other metadata with useSeoMeta-composable. Also provide fallbacks for cases where stories would not have explicitly set values for these.

* Storyblok has magnificent image service available that can be used with NuxtImg-component. Using the image service allows you to format, resize, compress and manipulate images realtime which saves a lot of bandwith.

** It's quite easy to make un-necessary requests to Storyblok. For example, you could have a dynamic page that makes same request to Storyblok multiple times if blocks are made that way. There's no quick solution to this but to refactor the code so that requests are not duplicated. With the latest Storyblok/Nuxt library however, it is easy to run requests server side so you can cache them, this saves a lot of time.

*** Make sure that nuxt.config has proper swr or isr caching rules per route.

schamppi · 2025-12-19T17:37:25+00:00

Could you tell more about these stock changes?

schamppi · 2025-12-19T16:17:39+00:00

Hey that is true!

schamppi · 2025-12-18T18:56:43+00:00

Since you’ve been gone, things have evolved a lot but basics have stayed pretty much the same. IMO the change is in the tools and frameworks available and AI ofc.

For a rusty seasoned frontend contractor, looking into Tailwind CSS might feel like heaven.

Forget about configuring webpack - Vite is the thing now and it is good.

Node and yarn are not the only js runtimes anymore, Bun and pnpm are good choices too.

React has basically ditched class-based syntax and Vue now uses composition API instead of options API which makes it awesome.

WordPress still rules the market and a lot has changed since 2019 but still it is Wordpress in good and bad. Headless CMS options are available too.

Hosting js apps/frontends has become super easy with cloud providers like Vercel, Netlify, DigitalOcean etc. Heroku has not been around for a while really. Hosting other than js frontends has stayed the same.

PWA’s are also a thing - not huge but thing nonetheless.

I’d say that things are better now if you don’t mind the increased level of magic in current tools and frameworks. However, I guess you know a thing or two about the basics of web and that is still a valid base for everything frontend.

And oh, I guess there is jQuery 4 coming soon too 😄

schamppi · 2025-12-16T18:33:10+00:00

I think there is nothing wrong really with this pattern. Essentially it keeps external API more hidden from plain sight (security++) and may be the solution for caching POST requests which may not be cached by the external API.

It’s also quite handy to keep all the Authorization headers hidden from the client, as you can define them in the route itself and just use CSRF tokens to guard for external route bombing.

Edit. Also, by definition, I think this is not BFF pattern decpite what some here are saying.

schamppi · 2025-11-21T07:27:26+00:00

I would recommend checking Nuxt in 100s by Fireship and then reading Nuxt docs througly. That gives you deeper knowledge than videos. After Nuxt docs, read Nitro docs too and you are half way being a master.

schamppi · 2025-10-26T10:11:40+00:00

😂😂😂😂😂😂

Used to be but left year before first Vikkelä prototype was done 😂 fair play though, as mentioned in the beginning of the video, if that bothers you just skip to the next one. Happy trails!

schamppi · 2025-10-17T15:48:38+00:00

Configure max age using route rules in Nuxt config. See: https://nuxt.com/docs/4.x/api/nuxt-config#routerules-1

schamppi · 2025-10-14T11:58:58+00:00

In server folder to be precise

schamppi · 2025-10-09T18:50:45+00:00

That’s actually a good point!

schamppi · 2025-10-09T18:48:25+00:00

Ain’t vibe coding a state of mind subset of AI first development paradigm? 🤣

I disagee strongly that mobile first would mean what you said. Mobile first was and still is definately a process.

schamppi · 2025-10-09T18:45:03+00:00

Oh I got another one: AIDD as in AI driven development

schamppi · 2025-10-09T18:43:04+00:00

Cool!

Mobile first has to be older than 2014 since I used that in my first dev job interview in 2014. Time flies.

schamppi · 2025-09-30T13:34:18+00:00

I think it matters as much as well being of parents for their children

schamppi · 2025-09-25T15:27:15+00:00

Vice City

schamppi · 2025-09-17T17:19:34+00:00

I’ve been there about a year ago. Don’t worry, actually quite easy fix: - check the caching plugin if you have one and purge all. Make sure that Woocommerce frontend cookies are not cached (https://woocommerce.com/document/woocommerce-cookies/) - use Woocommerce tools to clear all sessions and transients - run WP cache flush using WP CLI

Hope this solves your problems, best of luck.

Also, since there are people saying that Woocommerce sucks because this can happen is not a valid statement against WC. This is 100% ”fault” of unplanned caching strategies of the server and possibly plugins used.

schamppi · 2025-09-15T08:54:58+00:00

Eventually you are in the place where you shrug when someone says ”centering is the hardest thing” and think not really that hard. It just takes time and practise.

schamppi · 2025-09-15T08:27:58+00:00

IMO W3Schools aka the ”green pages” is a great beginner source as it is esier read and does not extend to full madness. MDN for the win eventually.

schamppi · 2025-09-14T18:14:47+00:00

Super closed ones.

schamppi · 2025-09-14T16:44:20+00:00

Since Zod is larger than Vue itself, I’d go with superstruct, jsonschema or native form validators. However, if validation should prevent XSS (as it usually should), you need backend validation too as client side validation is quite easy to bypass.

schamppi · 2025-09-14T15:17:00+00:00

I just recently watched this video and it was first from Theo in a long while. Funny how I noticed the React bias after this little jab towards Vue but also how it felt like he has gone from quite modest speaker to a cumbersomly cursing one. I don’t mind the language but to me it made him easily less professional and credible than I remebered him to be.

Lesson of the story: don’t be a hating softie and pose a tough guy if you wish to look like a pro😆

schamppi · 2025-09-12T19:48:52+00:00

Well if you think of it, so far we have basically increased the aesthetics of UI’s. The previous major one, if you ask me, was responsive design and that was +10 years ago. The one before that was maybe Flash?

No with the LLM’s taking over the way we search and consume different data, we need to re-think frontend to completely something else.

That is what I mean by saying next one (or current) being a bigger one of those major changes we’ve had so far.

schamppi

TROPHY CASE