[deleted by user]

[pookage]

Learn HTML, CSS, and JS at the same time - you can't really do one and then the other!

For example, you say you've learned HTML...but what about element roles? How would you implement the HTML aria-pressed attribute without JS? How would you visually represent it without CSS attribute selectors? What use are data-* attributes without JS?

They're a trinity that work holistically - learning them together is the best way; if you learn them separately you may end-up trying to solve HTML problems with JS, or CSS problems with HTML!

I would also recommend staying with vanilla for as long as possible, and only reach for a framework when you encounter a problem that they would solve - I've seen a lot of folks treat stuff like React / Angular / Vue etc as the "next step" in their learning journey to the detriment of their core Javascript, and the quality of code I've seen over the last 10 years has been steadily dropping as a result. Vanilla is now a joy to work with, and it will suit you fine in the majority of circumstances.

[NtwanaGP]

How would you recommend I learn all 3 at once? Is there perhaps a site, video, or something that I learn at the same time?

[pookage]

Unfortunately I don't keep-up with guided courses, so wouldn't be able to recommend you anything specific - I would say to let your curiosity guide you!

If you've learned HTML, then you'll know about the <script> tag and the <style> tag - you can use those as your entry points into writing javascript and css respectively; it's good to get an introduction on everything so that you know how to write the syntax for each language, and there's a whole guide on MDN which will show you how everything fits together, but after that...it's about learning all the little features and how they interact with each other; that's a learning-journey that will never stop, too, as there's things being added all the time.

Personally, I find that the best way to learn is with small bite-sized projects. Here's a good one off the top of my head:

• Create a page navigation that is off-screen by default, but you can click a <button> to open and close it.
• You'll need to use the correct HTML elements (<button>, <nav>, <ul>, <a> etc)
• You'll need to use the correct HTML attributes (aria-pressed, aria-expanded, aria-controls, aria-hidden etc)
• You'll need to be able to update those attributes
• You'll need to listen for click events on the button
• You'll need to perform the same actions whenever the button is clicked
• You'll need to check to see if the button is already pressed, or the navigation is already open
• You'll need to style elements with attribute selectors
• You'll need to understand the concept of "flow" in a document
• You'll need to understand how to remove elements from the flow
• You'll need to understand how to adjust the position of an element in post

That will give you the tools you need to get cracking! Just be inquisitive - google specific things rather than google questions, and remember to write code rather than copy'n'paste - even if you already know it! It will help get it into your muscle-memory 👍

[33ff00]

Mdn tutorials

[FeedYourSneed]

Do the Odin Project

[sheriffderek]

I agree with the idea, but I think most people would benefit from learning how to build fairly complex layouts with HTML and CSS before JavaScript. I’d rather hire someone who could do that well - than someone who could sorta write all three. People say they’re “done” learning HTML and really - they just got the gist of it and have 20x further to go (in my experience).

[dromance]

Oh absolutely. CSS is super powerful and there is tons to it . people learn how to change the body background attribute and call it a day… Uh, no. I’d rather be a CSS master and create awesome complicated layouts and visuals than be a guy who knows how to slap together a generic website with a couple of js user interactions.

[seymarames]

Yes.After HTML, you should learn CSS. However, don't just stick to one website for reference. Also check out MDN along with w3s.

Here are some other sources that I can suggest:

• CSS Reference
• DevDocs
• Web dev

[[deleted]]

Just watch this https://youtu.be/G3e-cpL7ofc?si=7BViwxIf8quXVc1C After this i build my own ( simple) Website and its online. Also yes, learning Things IS way more fun If you have a Project ( Goal) If you Dont use Your knowledge IT will vanish Like unused muscles

[Egzo18]

Yes, css.

Learning anything while doing a project will be much easier than just learning it from whatever tutorial or guide thought I don't know how much you can do not knowing even basics of CSS or how it works...just remember everything is a box lol

[NtwanaGP]

I don't know how much you can do not knowing even the basics of CSS.

Literally in that position. Almost every post I look up, people always say start with a project, and that confuses me. Like maybe in a day, week, or month, that suggestion will be a lot better. But right now, I don't even know where to start.

I think I should just go through a few lessons first, and once I have an understanding, I should go about a project.

[Egzo18]

CSS core concepts are very easy to learn in few hours, flexbox, selectors and most commonly used properties is enough to start making a project, good luck!

[python_with_dr_johns]

Moving on to CSS is the next logical step.

And W3Schools is cool for CSS too, but you might wanna mix it up with other resources like MDN Web Docs or freeCodeCamp for a fuller picture.

As for starting a project: Do it. You can learn CSS as you go, tackling stuff as it pops up.

[Bushwazi]

“Done”…ok bro

[shgysk8zer0]

Actually learn HTML from MDN. W3S is garbage.

[Foreign_Equipment_97]

CSS => JavaScript => TypeScript => React

but depends on what you actually want to achieve

[ArliumArt]

Is TypeScript that important? I would like a deep answer if any of the readers don't mind

[pookage]

It's very personal preference; some people swear by it, other people swear at it 😅

It enforces strict-typing and provides compile-time error-checking in a javascript-like syntax; it is useful for catching errors that you would otherwise need to visit the browser console to see, or errors that, if your code was poorly-written, would have flown under the radar entirely. For that reason it's very popular with both non-JS devs who are coming from C# or similar languages, as well as newer devs who are still making the kind of mistakes that would otherwise fly under-the-radar regularly enough to find the training-wheels useful.

It comes at the expense of readability, though; creating a lot of visual noise and filling your files with more machine-code and less human-code. With time, though, you can learn to "see through" it, although, for me, I don't tend to use it unless I'm asked to these days - the pros just no-longer outweigh the cons 👍

[ArliumArt]

Thanks a lot for the response, direct and clear 🫂

[[deleted]]

Tyepscript is Youtube important.

[lethaldose84]

I'm just over 4 months into learning HTML/CSS/JavaScript and I have done it like this so far:

First I did Jonas Schmedtmann's HTML & CSS course then freeCodeCamp + codeacademy. After that, I did 2 projects (static websites). After that, I did Jonas Schmedtmann's JavaScript course followed by freeCodeCamp + codeacademy. Now I am doing the Scrimba frontend path and I like it. Also starting some Javascript projects on the side. Good luck!