Files
LeviM-0323 9e58bb20db new file: INFO-1252 (Front End Dev)/Labs/Lab-5/Lab 5 - Desktop Version - Screenshot.png
new file:   INFO-1252 (Front End Dev)/Labs/Lab-5/Lab 5 - Mobile Version - Screenshot.png
	new file:   INFO-1252 (Front End Dev)/Labs/Lab-5/Lab 5 - Tablet Version - Screenshot.png
	new file:   INFO-1252 (Front End Dev)/Labs/Lab-5/images/dinner.jpg
	new file:   INFO-1252 (Front End Dev)/Labs/Lab-5/images/dinnerparty.jpg
	new file:   INFO-1252 (Front End Dev)/Labs/Lab-5/images/nachos.jpg
	new file:   INFO-1252 (Front End Dev)/Labs/Lab-5/images/smileyface.png
	new file:   INFO-1252 (Front End Dev)/Labs/Lab-5/images/squares_bg.png
	new file:   INFO-1252 (Front End Dev)/Labs/Lab-5/index.html
	new file:   INFO-1252 (Front End Dev)/Labs/Lab-5/notes.txt
	new file:   INFO-1252 (Front End Dev)/Labs/Lab-5/styles/main.css
2025-11-02 12:30:09 -05:00

22 lines
980 B
Plaintext

This project has all the css code in one giant file and there are
pros and cons of doing this.
pros:
slightly faster webpage load times and less network traffic.
cons:
you have one big giant css file which can be hard to maintain if the
project is just a little bit larger than this.
In the industry, we separate the css codes into multiple files.
The css code can easily be thousands of lines in a small real-world projects
and we have no choice but to separate the codes.
By doing this we get the benefit of maintainability.
When the code is actually sent to the clients/users there are tools
to combine the css(and JavaScript) code into less css file.
By doing this we get the benefit of less network traffic and slightly
faster load times.
Do not worry about it for now if this does not make sense.
Try different approaches and see how you like it.
You will learn/experience more about this throughout the journey of IWD.