Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
7
Comments
7
Stash443
@Stash443

All comments

  • Giuseppe Giannotta•260
    @giuseppe-giannotta
    Submitted 5 months ago

    Testimonials grid section - Giuseppe Giannotta

    1
    Stash443•120
    @Stash443
    Posted 4 months ago

    Hi there, the code doesn't look finished. It didn't include semantic HTML. I'm not sure if naming a css file an index is fine but i think its better if you name your css files as styles.css instead of index.css and try using Grid to center your parent container. but overall nice try though.

    Marked as helpful
  • isaiahp04•180
    @isaiahp04
    Submitted 4 months ago

    Four Card Feature Section Using Mobile-First Workflow

    1
    Stash443•120
    @Stash443
    Posted 4 months ago

    Your code has semantic HTML which is good. The code is well structured and readable. You also added comments on the code so that the next person can understand. Although I do recommend you use rem units for font size's of text, it helps a lot with responsive layouts. Well done.

  • Mustafizali•80
    @Mustafizali
    Submitted 5 months ago

    Product Review card

    1
    Stash443•120
    @Stash443
    Posted 5 months ago

    The code is readable but you didn't include semantic HTML. The layout looks the same as the design. Well done.

  • zardrick•260
    @zardrick
    Submitted 5 months ago
    What are you most proud of, and what would you do differently next time?

    I’m proud of how well the layout and typography turned out, especially the clean and structured design. The use of CSS custom properties and responsive styling made the page look great on different screen sizes.

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

    Handling the list styling for the ingredients and preparation steps required tweaking the default styles. I used CSS pseudo-elements to customize bullet points and markers, achieving a cleaner, more polished look.

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

    I’d love feedback on: Code Structure: Are my CSS and HTML well-organized? Best Practices: Any unnecessary code or areas for improvement?

    Simple Omelette Recipe Page - HTML, CSS & Responsive Design

    1
    Stash443•120
    @Stash443
    Posted 5 months ago

    Your solution does not contain semantic HTML, try implementing it in future projects it helps with SEO and readability. Also normalize adding comments in your CSS so that you don't get confused next time you view your code after a while. Your code is well structured and readable as well as your media query. Overall you have coded well. Well done.

  • doganayurgupluoglu•40
    @doganayurgupluoglu
    Submitted 5 months ago
    What challenges did you encounter, and how did you overcome them?

    It could probably have been coded in a more optimized way, but I wanted everything to be contained within a single container. If there are any mistakes you would like to correct or improvements you would like to suggest, please feel free to provide feedback.

    Used Flexbox

    1
    Stash443•120
    @Stash443
    Posted 5 months ago

    The code is well structured and readable. Although I've noticed that your solution code didn't include responsive code for mobile screens but all in all it's similar to the design, there's just a slight width difference. Well done.

    Marked as helpful
  • sj•100
    @subjectiverealityy
    Submitted 5 months ago
    What challenges did you encounter, and how did you overcome them?

    When I was pushing to Git, I kept making mistakes on the README.md file and had to keep repeating the process of git add, git commit and git push. I have now gotten it to read the way I want it to. The problems originated from using the wrong file paths for the README.md file and my project's screenshot initially.

    Responsive Blog Preview Card

    2
    Stash443•120
    @Stash443
    Posted 5 months ago

    The solution was well built, as well as the responsive(media query) part was well structured and understandable. I don't see any improvements that need to be implemented here. Well done.

  • kr0ma-git•40
    @kr0ma-git
    Submitted 5 months ago
    What are you most proud of, and what would you do differently next time?

    Although the replica itself is not perfect, I'm kind of proud that I was able to pull it off having barely any actual experience on HTML and CSS without relying too much on external sources. What I think I'd probably do differently next time is to organize my time by finishing other aspects first that are way simpler to implement as opposed to those that will take me more time.

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

    I felt I didn't have to struggle with the image resizing bit, but I did. It was really annoying at first since it kind of destroyed the other parts of the layout. Managed to know what the problem was though and pulled through with it (realizing that transform: scale() does resize the image but just changes how it is supposed to look /fp).

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

    I would most definitely need help in formatting the page in a way that accustoms the entire page accordingly based on the window's size and dimensions. Still need to learn that part of styling I guess.

    Challenge #1 - First Submission to Frontend Mentor | QR Code Component

    3
    Stash443•120
    @Stash443
    Posted 5 months ago

    I find the code well structured and the design is close the solution. Nice use of the position property.

Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub