P
OlgaBorovik• 120
@OlgaBorovik
Posted
Good job
0
Design comparison
Solution retrospective
What are you most proud of, and what would you do differently next time?
- I am proud that I started, I told my self that I would practice some web skills and I did
What challenges did you encounter, and how did you overcome them?
- I had to set up my environment on a new machine and get familiar with HTML and CSS again
What specific areas of your project would you like help with?
- efficiency, I sometimes feel like I am just slapping CSS together in a way that does work, but could be better
Community feedback
Osei-Bonsu Isaac• 50
@io-oseinana
Posted
Hello @JonKnitt1205, congratulations on completing this project, let's make some changes that may be helpful 😊
Suggestion:
- It's recommended 👍️ to put CSS into its own file which may help in the following:
- Cleaner Code Structure 🧹: Keeping HTML and CSS separate makes each file easier to read and maintain.
- Reusability 👨💻: By separating CSS into its own file, you can easily reuse styles across multiple HTML files.
- Scalability 📈: Separating CSS allows you to manage styles more efficiently. You can easily add, remove, or modify styles without directly affecting the HTML structure.
- Faster Loading Times 🚀: When CSS is externalized into a separate file, the browser can cache it, improving loading times for subsequent page views.
- Also consider using CSS reset in your future projects
0
Yash Babani• 660
@Yashbabani0
Posted
.
0
Please log in to post a comment
Log in with GitHub
Join our Discord community
Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!
Join our Discord