It depends what your goals are. All of my side projects were started because I wanted to learn something. Using a "skip to the end" button wouldn't really make sense for me.
Then chances are it’ll be subpar either way. Every type of cheese, in six hours? The CSS isn’t the bottleneck there, it’s information hierarchy and the information itself. You can’t possibly learn about the history of cheeses and summarise it and organise it for a website in that amount of time. Writing the website code isn’t the lengthy part.
> That people choose to not to learn about topics they don't find interesting because they'd rather learn about topics they do find interesting, doesn't automatically make them dumber than you.
Why so rough? I don’t see any judgement of character or intelligence in the comment you’re replying to.
Going off of the two screenshots in the OP, neither of those were about frontend.
So if the choice is spending time designing a more human frontend or spending more time on the core product, I don’t fault people for choosing the latter.
Now if the core product also stinks, that’s a different issue.