btw, i haven’t looked into it yet, but from what you have said, i can think of just one thing: “Practice”
let me elaborate, as you’ve said, it’s way later in course, and as it’s a build up for a complete project, then i would say it’s not a bad idea, to recap what you’ve gone through and apply it as you go forward!!
hey, thats just me, perhaps others can weigh in here about this!
That’s step 1, if I remember correctly it does it to 4, and it’s still weird that sometimes a lesson will fail you for doing <html lang="en"> instead of <html> when we were told that we should be declaring the language in the HTML tags like way early on
Skyline spreads out the previous Step 1s into like, 4 steps which is just strange given how deep into the cert it is
also, that’s fair, but it still shouldn’t fail the lesson when you enter <html lang="en"> because that’s an html tag, and it has been told to us before that it’s fine, plus the error message with it fails is something to the effect of “you have to have an <html> tag” which is unhelpful if you’re going to require the language to be undeclared
well this seems like an opportunity to “contribute”, write up an issue about this then!! seems quite valid to me, error message should give enough relevant information to user so that they can correct this!!
i havent done this personally, so i cant really say for sure how “misplaced or redundant” this is!!
but filling issue for requesting a “better error message in console” sounds like a “good thing” to do!!
I think the main reason is that lesson was the 2nd or 3rd project built. There is some inconsistency between the projects because they were done at different times, by different people, and in different orders.
We might want to think about removing some of the lessons that do not have to do with CSS variables.