Skip to content
OverviewSolutions
8
Comments
2
Thomas Percival
@tpercival01

All comments

  • Thomas Percival•240
    @tpercival01Posted over 1 year ago

    Really great job.

    Only advice I would give is to potentially use more detailed IDs. Even for small projects like this, it is good practice for the future.

    1
  • ilyemm•140
    @ilyemmSubmitted over 1 year ago

    I decided to focus on vanilla HTML/CSS since I'm a complete beginner and wanted to practice in understanding the fundamentals before introducing things like Sass into my workflow.

    When making the projects, I had a hard time understanding how to break the components into different parts, resulting in me needing to restart the project. Initially, I was trying to tackle different parts of the design all at once which ended up making things really messy. Eventually, I came up with a result by taking it by the outer layer of the design before going into the details, but I definitely feel like I could have made this more efficiently.

    My main question is about best practices: how does someone start off their HTML/CSS before building on top of that foundation to create the rest of it?

    Thanks!

    Using Vanilla HTML/CSS for Results Summary Component

    2
    Thomas Percival•240
    @tpercival01Posted over 1 year ago

    I believe you have the idea down quite well.

    Personally I like to start how the Readme suggests: build your html first. Just look at the design and decide what components you need, perhaps even researching typical HTML elements used for certain aspects, i.e. flexbox or grid for positioning elements within an element. Then when you're happy with the structure, start adding your CSS in segments; top-to-bottom, right-to-left. I prefer to work on getting the general styling down for everything before going back over with all the colours, shadows, etc.

    Marked as helpful
    0