Web Development
Learn Web Development From Scratch 0️⃣ HTML / CSS 1️⃣ JavaScript 2️⃣ React / Vue / Angular 3️⃣ Node.js / Express 4️⃣ REST API 5️⃣ SQL / NoSQL Databases 6️⃣ UI / UX Design 7️⃣ Git / GitHub Admin: @love_data
إظهار المزيد📈 نظرة تحليلية على قناة تيليجرام Web Development
تُعد قناة Web Development (@webdevcoursefree) في القطاع اللغوي الإنكليزية لاعباً نشطاً. يضم المجتمع حالياً 79 530 مشتركاً، محتلاً المرتبة 1 601 في فئة التكنولوجيات والتطبيقات والمرتبة 3 791 في منطقة الهند.
📊 مؤشرات الجمهور والحراك
منذ تأسيسه في невідомо، حقق المشروع نمواً سريعاً وجمع 79 530 مشتركاً.
بحسب آخر البيانات بتاريخ 25 أكتوبر, 2026، تحافظ القناة على نشاط مستقر. خلال آخر 30 يوماً تغيّر عدد الأعضاء بمقدار -37، وفي آخر 24 ساعة بمقدار -17، مع بقاء الوصول العام مرتفعاً.
- حالة التحقق: غير موثّقة
- معدل التفاعل (ER): يبلغ متوسط تفاعل الجمهور 2.93%. وخلال أول 24 ساعة من النشر يحصد المحتوى عادةً 1.09% من ردود الفعل نسبةً إلى إجمالي المشتركين.
- وصول المنشورات: يحصل كل منشور على متوسط 2 327 مشاهدة. وخلال اليوم الأول يجمع عادةً 866 مشاهدة.
- التفاعلات والاستجابة: يتفاعل الجمهور بانتظام؛ متوسط التفاعلات لكل منشور يبلغ 7.
- الاهتمامات الموضوعية: يركز المحتوى على مواضيع رئيسية مثل html, css, javascript, github, git.
📝 الوصف وسياسة المحتوى
يصف المؤلف القناة بأنها مساحة للتعبير عن الآراء الذاتية:
“Learn Web Development From Scratch
0️⃣ HTML / CSS
1️⃣ JavaScript
2️⃣ React / Vue / Angular
3️⃣ Node.js / Express
4️⃣ REST API
5️⃣ SQL / NoSQL Databases
6️⃣ UI / UX Design
7️⃣ Git / GitHub
Admin: @love_data”
بفضل وتيرة التحديث المرتفعة (أحدث البيانات بتاريخ 26 أكتوبر, 2026) تحافظ القناة على حداثتها ومستوى وصول مرتفع. وتُظهر التحليلات تفاعلاً نشطاً من الجمهور، ما يجعلها نقطة تأثير مهمة ضمن فئة التكنولوجيات والتطبيقات.
../
means:
Go up one directory.This concept becomes very important as projects become larger. 9️⃣ Common Project Folders As applications become more complex, you'll encounter folders such as: src/ components/ pages/ assets/ images/ styles/ utils/ services/ Their exact purpose depends on the project and framework. For example:
src/
├── components/
├── pages/
├── services/
├── assets/
└── styles/
We'll learn these structures when we start working with React and larger applications.
🔟 A Real-World Project
A simple website might look like:
portfolio/
│
├── index.html
├── about.html
├── contact.html
│
├── css/
│ └── style.css
│
├── js/
│ └── script.js
│
└── images/
├── profile.jpg
└── project1.png
A larger modern application might eventually look more like:
my-app/
│
├── src/
│ ├── components/
│ ├── pages/
│ ├── services/
│ ├── assets/
│ └── styles/
│
├── public/
├── package.json
├── README.md
└── .gitignore
Don't worry about understanding all of these folders yet.
We'll introduce them when we actually need them.
🧠 Key Things to Remember
File → Stores information or code.
Folder → Organizes files.
index.html → Common default/main HTML document.
images/ → Can organize image files.
css/ → Can organize CSS files.
js/ → Can organize JavaScript files.
../ → Moves up one directory in a relative path.
A good project structure keeps code organized and makes applications easier to understand and maintain.Double Tap ❤️ For Part 12 ----- 1.29 ₽ · /balance_help
my-website/
│
├── index.html
├── style.css
├── script.js
│
├── images/
│ ├── logo.png
│ └── profile.jpg
│
└── pages/
├── about.html
└── contact.html
Here:
my-website/
is the main project folder.
Inside it are files and additional folders.
3️⃣ Why Do We Need Project Structure?
Imagine putting every file for a large application into one folder without organization.
You might eventually have:
100+ files
Finding the correct file would become difficult.
A good structure makes it easier to:
Find files
Understand the project
Maintain code
Work with other developers
Scale the application
4️⃣ The Basic Website Structure
For a beginner website, you can start with:
my-website/
│
├── index.html
├── style.css
└── script.js
Each file has a different job.
index.html
Contains the webpage structure.
<h1>My Website</h1>
<p>Welcome to my website.</p>
style.css
Controls the appearance.
h1 {
color: blue;
}
script.js
Adds behaviour.
console.log("Website loaded");
The browser can connect these files together.
5️⃣ The index.html File
You'll see index.html very often.
It is commonly used as the main or default HTML page of a website.
For example:
my-website/
│
└── index.html
When someone visits the main page of a simple website, the server may serve the index.html document.
It's a convention rather than a universal rule for every web application.
6️⃣ Organizing Images
Instead of putting every image directly in the project root, we can create an images folder.
my-website/
│
├── index.html
├── style.css
├── script.js
│
└── images/
├── logo.png
├── laptop.jpg
└── phone.jpg
Then HTML can reference an image inside that folder.
<img src="images/logo.png" alt="Logo">
The path:
images/logo.png
tells the browser where the image is located relative to the HTML file.
7️⃣ Multiple Pages
A website can contain multiple HTML pages.
For example:
my-website/
│
├── index.html
├── about.html
├── contact.html
│
├── css/
│ └── style.css
│
└── images/
└── logo.png
You could have:
index.html → Home
about.html → About
contact.html → Contact
This is a simple way to understand how multi-page websites are structured.
8️⃣ Relative Paths
Understanding file paths is extremely important.
Suppose you have:
project/
│
├── index.html
│
└── images/
└── logo.png
From index.html, you can reference the image using:
<img src="images/logo.png">
Now suppose you have:
project/
│
├── pages/
│ └── about.html
│
└── images/
└── logo.png
From about.html, you need to go up one folder first:
<img src="../images/logo.png">npm install express
This can install Express into a project.
We'll learn npm properly when we reach Node.js.
6️⃣ Git
Git is a version control system.
It tracks changes to your code.
Imagine you modify your application today and accidentally break something tomorrow.
With Git, you can keep a history of changes and potentially return to an earlier version.
A simplified workflow:
Write code → Save changes → Git commit → Continue working → More changes → Another commit
Git becomes essential when working professionally.
7️⃣ GitHub
GitHub is a platform for hosting Git repositories and collaborating on software projects.
You can use it to:
• Store your code
• Share projects
• Collaborate with developers
• Review changes
• Create pull requests
• Track issues
• Build a public developer portfolio
A typical workflow is: Your Computer → Git → GitHub → Remote Repository
We'll learn Git and GitHub in detail later.
8️⃣ API Testing Tools
When working with backend APIs, developers often need to send requests without using a frontend.
Tools such as Postman can help with this.
For example, you might send: GET /users and inspect the server's response.
This is useful when developing and debugging APIs.
We'll introduce API testing once we reach backend development.
9️⃣ Database Tools
When we start working with databases, we'll also use database clients and tools to:
• Create databases
• Create tables
• Run SQL queries
• Inspect data
• Debug database problems
For PostgreSQL, tools such as pgAdmin can provide a graphical interface.
We'll learn database tools when we reach the database section.
🔟 How These Tools Work Together
A typical beginner web development workflow might look like:
VS Code → Write Code → Web Browser → Developer Tools → Debug & Test → Git → GitHub
Later, when we become full-stack developers:
VS Code → Frontend + Backend → Browser → Developer Tools → API Testing → Database → Git → GitHub → Deployment
🧠 The Most Important Tools to Remember
At this stage, focus on these:
• VS Code → Write code
• Browser → Run and view websites
• Developer Tools → Inspect and debug websites
• Terminal → Run commands and development tools
• Git → Track code changes
• GitHub → Store and collaborate on code
• npm → Manage JavaScript packages
Double Tap ❤️ For Part 11
-----
1.36 ₽ · /balance_help<button>Buy Now</button>
You can inspect the button and see which CSS rules are affecting it.
You can even temporarily modify the CSS in Developer Tools and immediately see the result.
This is extremely useful when debugging layouts.
Console
The Console is mainly used for:
• JavaScript output
• Errors
• Warnings
• Debugging
For example: console.log("Hello Web Developer");
The message appears in the browser console.
Later, you'll use the Console frequently while learning JavaScript.
Network
The Network panel shows communication between the browser and servers.
You can see:
• Request
• Response
• URL
• Status code
• Request method
• Response data
• Loading time
For example: GET /products - 200 OK
This becomes particularly useful when working with APIs.
Application
The Application panel can help inspect browser-side storage and other resources, including:
• Cookies
• Local storage
• Session storage
• Cache-related information
We'll use this later when learning authentication and browser storage.
Sources
The Sources panel helps you inspect loaded source files and debug JavaScript.
4️⃣ Terminal
The terminal allows you to interact with your computer using commands rather than a graphical interface.
For example: mkdir my-project creates a folder.
You might also run commands such as:
• npm install
• npm run dev
Later, you'll use the terminal to:
• Create projects
• Install packages
• Run development servers
• Execute scripts
• Work with Git
• Build applications
• Deploy applications
You don't need to memorize commands now. We'll learn them gradually.
5️⃣ Package Manager
Modern web applications often use external libraries and packages.