Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found

All solutions

  • Submitted


    Challenge #02 complete! ^.^

    It's refreshing having to build something with a clear finish line. I'm happy I watched Kevin Powell's YT channel and the recommendation to this site. Hope everyone is having a nice day.

    I'm avoiding using frameworks for the first three challenges mostly to help myself learn better habits. I can appreciate how much easier react makes things.

    Somethings I had problems with were planning for the mobile implementation, CSS development, and CSS testing.

    The questions I'm asking are such:

    • What is a good approach to plan for mobile views? I personally built for desktop without planning for mobile. This lead to adding more classes and lots of media queries.

    • What is a good rule of thumb for committing CSS work? When I work with JS I feel confident in committing after creating new functions, updating a feature, or debugging something. When it comes to CSS I don't have that instinct yet.

    • Somewhat related to the previous. Are there better ways to test CSS than observing their behavior via chrome tools? This one might be worded a bit weirdly. I find it a bit awkward having to observe the changes and then mouse the element to confirm changes. In JS I can use jest to test functions or HTML, but I'm not sure where to look for CSS testing.

    Thanks to everyone reading this :]

  • Submitted


    Two things I found difficult:

    • Breaking down the reference material into semantic HTML when planning.
    • Organizing CSS in a way that is easier to read and flows logically for updating.

    My question then is: What is some general best practices when breaking down reference images and organizing CSS code?

    Still, it was a fun little project. Thanks for stopping by!