I've been learning Python for the second month now. I want to dive into web development. I've heard about frontend and backend, but I'm not sure which part to start with. What basic skills should I learn first? What tools are relevant right now? Are there any commonly accepted roadmaps? Has anyone tried learning from documentation—does it actually work?
Web development from scratch: where to start the approach?
👁️ 8 views💬 3 replies❤️ 0 likes
3 Replies
Start with frontend—it's simpler and you'll see results faster. Get a solid grasp of HTML/CSS basics in a month, then move on to JavaScript, and after that, React or Vue.
Many beginners have the same question, especially after a short period of learning a language like Python. I also started with some confusion when I entered the web field. Anyway, the basic principle should be that you've had the chance to work with simple static pages using HTML/CSS or even a little front-end with JavaScript, but on the other hand, if you come to the backend first, you might get lost in the complexities without knowing the basics of how the web works well. I strongly recommend that you start with **Front-end** for 3 reasons: first, the visual benefits are faster, meaning the transparency you achieve will make you more motivated. Second, basic concepts like DOM and different environments (browser vs. server) will make it easier for you to understand the backend later. Third, most people when they start with the backend, prefer to get lost in technical requirements without knowing why the server is asking for this.
As for the number of basic skills you need now, put them in a small list: **HTML5** + **CSS3** (with Flexbox/Grid of course) so you can build the structure and shape of the page without problems. **JavaScript ES6+** to deal with interactivity. Then you can jump to **React** or **Vue** (I personally used Vue but React is more popular right now). On the backend side, after you finish the front-end, you can get into it, but wait: every daemon and every server starts in a very simple way - for example, at first you need to know how HTTP, REST/SOAP, Cookies, Headers, etc. work. The best starting point for the backend is **Node.js** with **Express**, especially since Python and Java web development use a similar async/await system.
As for the tools, now in 2024, **VS Code** is the constitution for all developers, **Git/GitHub** is also a must in your daily operations (if you're still a beginner in it, make your first task to study its CLI). As for the random roadmaps that beginners resort to, what I recommend is relying on the **Front-end roadmap** from [roadmap.sh](https://roadmap.sh) in general. Also, MDN Web Docs (developer.mozilla.org) is a very reliable source, especially for theoretical concepts - honestly, the Eastern guy who tried to learn from the Docs didn't get anywhere without getting lost in the sea, but when you ask about specific things, it becomes a very trustworthy reference. Personally, I love the Office Hours military-style follow-up for small starting projects - meaning, for example, make 3 simple pages: the first Contact page, the second Blog but with a dummy API - just like that, develop 5 small projects before you decide to go deeper into a specialty.
Alright, I'll compare it to learning how to drive a car: first, you need to understand the basics, and then move on to practice.
If you've been using Python for two months, starting with frontend is easier—HTML/CSS/JavaScript cover 80% of simple tasks, and the result is visible immediately, like when the browser's "headlights" light up. On the other hand, backend gives you an understanding of how the server side works, and Python is great for that (e.g., Django or FastAPI). Think of it like comparing a sports car and a tractor: a sports car will get you from point A to point B faster, but a tractor can haul more cargo and handle rough terrain. So if you want to build a simple lightshow website from start to finish, go with frontend. If you want to understand how the backend works, go with Python + a framework.
The documentation is real, but like a roadmap: if you don't know where you're going, even Google Maps won't help. First, read the basics (HTML, CSS, JS), then dive into the specifics of your chosen framework. A roadmap, by the way, is like a recipe: there's a general list of ingredients, but every chef has their own tricks. Try, for example, [roadmap.sh](https://roadmap.sh)—it shows you what to learn next after the basics in infographic form. The main thing is, don't try to learn everything at once.