Not really an answer, but where do you draw the line?
Bootstrap -> CSS -> Web Server -> HTTP Protocol -> TCP/IP -> Networking -> OS Kernels -> Chip Design.
Obviously the above is a silly example, but at each stage of those you could argue the next level up is "the basics." The trick is to determine just how much of the basics do you really need to know to do what you need to do? Is it important that people know all the CSS tags and which ones work in what browsers? Or is it enough to have a general idea of "how" CSS works and understand that Bootstrap builds on top of it?
The problem of course is if they have no understanding of CSS and they get stuck in Bootstrap they are well and truly stuck.
Perhaps in this case you could encourage them to pick a Bootstrap component and dissect it to it's core to see how it's put together and what makes it tick. Maybe.
It's an interesting problem for sure.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Not really an answer, but where do you draw the line?
Bootstrap -> CSS -> Web Server -> HTTP Protocol -> TCP/IP -> Networking -> OS Kernels -> Chip Design.
Obviously the above is a silly example, but at each stage of those you could argue the next level up is "the basics." The trick is to determine just how much of the basics do you really need to know to do what you need to do? Is it important that people know all the CSS tags and which ones work in what browsers? Or is it enough to have a general idea of "how" CSS works and understand that Bootstrap builds on top of it?
The problem of course is if they have no understanding of CSS and they get stuck in Bootstrap they are well and truly stuck.
Perhaps in this case you could encourage them to pick a Bootstrap component and dissect it to it's core to see how it's put together and what makes it tick. Maybe.
It's an interesting problem for sure.