You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there! In the lesson it's clearly stated that when it comes to the implementation of our component styles throughout the course we should stick to Vanilla CSS or CSS-in-JS. However, when you scroll up a little bit, you see Tailwind CSS categorized as Vanilla CSS option. So I asked guys in the chat back then and got the response in the spirit of "people doing this course should stick to writing their own CSS and stay away from frameworks as regular CSS is something that all of those frameworks are built upon" (1), which I completely agree with.
So we've got the general consensus that students should avoid using CSS frameworks (and to "implement your own component's styling from scratch" (2)) at least until the end of the TOP and the lesson telling people to stick to Vanilla CSS and listing Tailwind CSS as a valid Vanilla CSS option.
Which basically contradicts the general advice because:
Tailwind isn't regular CSS and is a framework which violates (1)
Tailwind provides a whole system which dictates the overall style of the app which violates (2)
The solution
I would like to use more specific wording instead of "Vanila CSS" since it's rather vague (and Tailwind could be considered as Vanilla CSS in that context) and remove Tailwind CSS documentation reference from "Additional resources" section but leave it as "Vanilla CSS" option in the list to avoid confusion and funnel people into writing regular CSS.
Checks
Describe your suggestion
The problem
Hi there! In the lesson it's clearly stated that when it comes to the implementation of our component styles throughout the course we should stick to Vanilla CSS or CSS-in-JS. However, when you scroll up a little bit, you see Tailwind CSS categorized as Vanilla CSS option. So I asked guys in the chat back then and got the response in the spirit of "people doing this course should stick to writing their own CSS and stay away from frameworks as regular CSS is something that all of those frameworks are built upon" (1), which I completely agree with.
So we've got the general consensus that students should avoid using CSS frameworks (and to "implement your own component's styling from scratch" (2)) at least until the end of the TOP and the lesson telling people to stick to Vanilla CSS and listing Tailwind CSS as a valid Vanilla CSS option.
Which basically contradicts the general advice because:
The solution
I would like to use more specific wording instead of "Vanila CSS" since it's rather vague (and Tailwind could be considered as Vanilla CSS in that context) and remove Tailwind CSS documentation reference from "Additional resources" section but leave it as "Vanilla CSS" option in the list to avoid confusion and funnel people into writing regular CSS.
Path
Node / JS
Lesson Url
https://www.theodinproject.com/lessons/node-path-react-new-styling-react-applications
Discord Name
SiriusMain#6886
Additional information
The text was updated successfully, but these errors were encountered: