../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