Obviously all the beginner articles are first, but then you have different language articles, serverless articles, intermediate articles etc. You could take any of those paths.
Does that make sense?
As the other response said, it's about not knowing where to begin. The nephew I had in mind is a complete newb, if he hit this site he'd be lost immediately because all the articles assume prior knowledge - except, presumably, the earliest articles in the beginner tag.
It may be that some specific navigation is needed for these beginners; but at the current scale it may not need even code, but simply an article that is 'New reader? Start here!', which goes on to describe places readers at various levels might start reading the site. "If you know a little programming in another language but want to learn Javascript, try here!..." etc.
However, as you scale up, readers will be thrown by articles in other topics appearing 'next' in their reading material, simply because that's when it was written. Having chosen a tag, that should be sticky for navigation. It turns out that all the 'Beginner' articles were written in sequence so they're fine; but you can see the issue starting from https://www.codetips.co.uk/javascript-introduction/ and clicking 'next' from the perspective of someone who clicked into the 'Javascript' tags? Or if you add more Beginner articles later, they would no longer be in sequence.
Anyway, I hope my criticism has been constructive and wish you all the best in helping new programmers...I've a big family-there's an almost inexhaustible supply of nephews&nieces getting to the age I'd like them to read this ;)
Simple change but it would make huge payoffs UX-wise.
Edit: I wasn't very clear. I realize you have those top level tags already, but I was referring to further group articles that "flow" into each other. That way you can have a "journey" without actually having one :)
