Skip to content
OverviewSolutions
7
Comments
7

GiorgiOsha95

@GiorgiOsha95100 points

I’m a mysterious individual who has yet to fill out my bio. One thing’s for certain: I love writing front-end code!

Latest solutions

View more solutions

Latest comments

  • P
    Scott•310
    @ldg
    What are you most proud of, and what would you do differently next time?

    I'm happy that I was able to use grid CSS get the layout to work between the different screen sizes.

    What challenges did you encounter, and how did you overcome them?

    One of the challenges for me was being able to target the individual cards so I could style each of them according to the design specs. I chose to use a utility class to set individual styles on each of the cards. Since I used Sass on this project I ended up adding my media queries to the utility classes for any changes that needed to happen between the different screen sizes.

    What specific areas of your project would you like help with?

    I feel like my code isn't very well organized, any suggestions in this area would be appreciated

    Sass, Grid CSS Testimonial cards section

    #sass/scss
    1
    GiorgiOsha95•100
    @GiorgiOsha95

    Great job with recreating the design without figma files

  • GiorgiOsha95•100
    @GiorgiOsha95

    Good documentation and the end result looks similar, You need to be more attentive to details ( Too much spacing between the card and title, Shadows for cards are hard to see compared to design ), Everything else looks great, Good job

  • Gustavo S. Dos Santos•840
    @GustavoSDS
    What are you most proud of, and what would you do differently next time?

    Quedó muy bien la página, como lo muestra el diseño.

    What challenges did you encounter, and how did you overcome them?

    Ningun desafío encontrado.

    What specific areas of your project would you like help with?

    En ninguna.

    Product preview card component

    1
    GiorgiOsha95•100
    @GiorgiOsha95

    Good job, the end result looks fantastic the same as the design

  • GiorgiOsha95•100
    @GiorgiOsha95

    Great job with the Tailwind CSS implementation! I noticed that the solution works well for both desktop and mobile versions. However, it breaks between screen resolutions of 640px and 1024px due to the max-w property. To improve responsiveness, you can either remove the max-w property in the container class for the 640px and 768px breakpoints or overwrite it using Tailwind utilities, for example: !max-w-full for smaller screens and lg:!max-w-[640px] for larger screens. This adjustment should ensure the design looks great across all resolutions.

  • GiorgiOsha95•100
    @GiorgiOsha95

    Semantic HTML: The code effectively uses semantic HTML elements, which enhances clarity and accessibility.

    File Categorization: The file organization is good and understandable, though it may be slightly complicated for a small project. Simplifying the structure could improve maintainability without sacrificing clarity.

    Mixins Usage: The use of mixins is well-executed and demonstrates good practice, especially for larger projects. They help in maintaining consistent styling and managing complexity.

    Marked as helpful
  • Rodri•160
    @rcsilva211
    What are you most proud of, and what would you do differently next time?

    I believe I did a good job in replicating the page and I'm happy with the result. I'm very open to constructive feedback!

    What challenges did you encounter, and how did you overcome them?

    Making the semantic seem right and organizing the code. Basically I did double check while trying to be unbiased about

    What specific areas of your project would you like help with?

    Help and feedback with best practices and what can I improve with.

    Blog preview card

    1
    GiorgiOsha95•100
    @GiorgiOsha95

    Good job, Really close to the design , for cleaner code wriiting i would say to write classes and tags on 1 line
    html, body {} like this instead of html,body {}

View more comments