Design comparison
Solution retrospective
Hello everybody! I finished the results summary component project.
I had some problems with styling in css because it takes me too much time to build the style and layout of the elements on the page.
Also, I would like to know how I could make the css code more efficient, without too many repetitions or complications.
Thank you in advance.
Community feedback
- @itushPosted over 1 year ago
Congratulations on completing the challenge! π
Welcome to the platform! π We're thrilled to have you here and excited to see your progress πͺas you continue your front-end development journey.
Your solution looks nice to me :)
Also great work with the JS, where the div elements created by the map function are added as children of the summary-items container in the DOM.
In my projects, I try to use at least one main element for a page, and avoid divs as much as possible and use section and article element wherever I can.
Now, to avoid styling issues one must clearly understand at least few basics of CSS.
I remember when I started out, I made countless mistakes and spent long hours searching for solutions. But hey, you don't need to go through the same struggles! π To help you shorten the learning curve, I recommend going through the following articles. They contain valuable insights that can make your journey smoother:
ππ 12 important CSS topics
ππ 11 important HTML topics
I hope you find these resources helpful in your coding adventures! π€
I'm eagerly looking forward to seeing the amazing projects you'll create in the future! ππ»
Keep up the fantastic work and happy hacking! πͺβ¨
Marked as helpful1 - @Thewatcher13Posted over 1 year ago
Hi,
-
You should have a main landmark element for semantics
-
use a ul for the right column, not p tags.
Are you completly new to webdev? Did you have already the qr code challenge?
Marked as helpful1@danyela2000Posted over 1 year agoHello, @Thewatcher13. No, I'm not new to webdev, but I am at the beginning of the road. I took some courses on front-end development. And I decided to practice with some projects. I don't understand why I need landmarks, I didn't use them so far. Thanks
0@Thewatcher13Posted over 1 year ago@danyela2000
Here is a guide on semantic elements.
https://web.dev/learn/html/semantic-html/
Also your font-size should not be in px (absolute value) but in relative values (rem) https://fedmentor.dev/posts/font-size-px/
I recommended to do the qr code challenge on frontendmentor
1 -
- @Thewatcher13Posted over 1 year ago
-
why did you choose a p tag on those? "Your result" "Great" "Summary"
-
Your button should have a type(type:button)
0@danyela2000Posted over 1 year ago@Thewatcher13, I used to write and use p tags very often, instead of headings, but I corrected them here, now.
About the type="button". If I don't use a button inside a form element, I don't think is necessary to use this attribute. This is important if you want to differentiate it from other types of buttons such as reset or submit buttons. But I think the reason for using it is just for accessibility or clarity.
0@Thewatcher13Posted over 1 year agoGood to see the changes! Different browsers may use different default types for the <button> element, for this reason it is always usefull to do it.
0 -
Please log in to post a comment
Log in with GitHubJoin 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