Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
8
Comments
9
P
Will Cooley
@CooleyWC

All comments

  • P
    joeabrahamian•100
    @joeabrahamian
    Submitted about 11 hours ago
    What are you most proud of, and what would you do differently next time?

    Yes

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

    Forgot to add media queries for mobile screen

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

    media queries

    Meet Landing Page

    1
    P
    Will Cooley•190
    @CooleyWC
    Posted about 8 hours ago

    Nice work!

    It's difficult to check the code as your code link goes to a 404. However, I do notice that the content doesn't scale down when the width shrinks - so I imagine you might have some hard-coded widths that are currently being inflexible. You might start with a mobile-first approach by getting everything to look as close as possible to the figma file at 374px, then build out the other sizes/media queries from there.
    Hope that helps!

  • P
    nmoon8019•50
    @nmoon8019
    Submitted 4 months ago
    What specific areas of your project would you like help with?

    HTML-- Is my use of div's acceptable? CSS-- am I using too much code to accomplish this?

    Blog preview card

    1
    P
    Will Cooley•190
    @CooleyWC
    Posted 4 months ago

    You could use an article tag (https://developer.mozilla.org/en-US/docs/Web/HTML/Element/article) instead of a div for the card. I would also use section tags instead of divs for the 'info' and 'authorbox'.

    CSS: I would avoid using pixels for font-sizes - convert to rems or use clamps for better responsiveness. I usually copy clamps from this site https://utopia.fyi/type/calculator?c=320,18,1.2,1240,20,1.25,5,2,&s=0.75%7C0.5%7C0.25,1.5%7C2%7C3%7C4%7C6,s-l&g=s,l,xl,12

    Also avoid setting hard widths and heights (on the container) - usually its better to use min-widths or min-widths to control the sizing.

    Hope that helps!

    Marked as helpful
  • P
    Jair•680
    @JairRaid
    Submitted 4 months ago
    What are you most proud of, and what would you do differently next time?

    I learned to make this quote mark position absolute to his parent.

    testimonials grid section

    1
    P
    Will Cooley•190
    @CooleyWC
    Posted 4 months ago

    Looks Great!

    Marked as helpful
  • AceThunder546•100
    @AceThunder546
    Submitted 4 months ago

    Four Card Feature Section with HTML and CSS

    1
    P
    Will Cooley•190
    @CooleyWC
    Posted 4 months ago

    Looks Great! One thing to consider is using a different unit type for font-sizes instead of pixels(rems are what I use most). This helps both with responsiveness and accessibility. And I also often use the typography clamps that I get from this site: https://utopia.fyi/ - they smoothly scale your font size and they make sure the size doesn't get too big or too small. Also consider updating your README (you can use the template they give you in the project files)

    Marked as helpful
  • adetoadeto•220
    @adetoadeto
    Submitted 4 months ago

    Responsive card component

    1
    P
    Will Cooley•190
    @CooleyWC
    Posted 4 months ago

    Looks great! Perhaps adjust the breakpoint so it doesn't get quite as wide before switching to your desktop layout (when the image is next to the description). Maybe somewhere in the 350-500px range.

    Marked as helpful
  • Masaud Ahmod•30
    @masaudahmod
    Submitted 5 months ago

    Frontend Mentor - Recipe page

    1
    P
    Will Cooley•190
    @CooleyWC
    Posted 5 months ago

    Looks great!! Perhaps consider using a separate css file for styling. A few items to compare with the original design:

    Mobile:

    • image should have no margin/padding.
    • container should extend to full width and height.
    • check colors of main heading text and the preparation time card.
    • spacing between li and their respective markers should be larger.
    • no bottom border after the last nutrition table row. can try not(:last-child) selector for this.

    Desktop: -larger top/bottom margin

    Marked as helpful
  • arachoxs•110
    @arachoxs
    Submitted 5 months ago

    Responsive Solution using flex

    1
    P
    Will Cooley•190
    @CooleyWC
    Posted 5 months ago

    Looks great! Check responsiveness on small screens

  • knurik•30
    @knurik
    Submitted 6 months ago
    What are you most proud of, and what would you do differently next time?

    I would start with writing down full HTML page, and only after write CSS for it

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

    Main challenge was center div on the middle of the page. I overcome it using display: grid

    Blog preview card HTML CSS

    1
    P
    Will Cooley•190
    @CooleyWC
    Posted 5 months ago

    Looks great!

    It appears your solution has some box shadow on the top and left, whereas it should just be right and bottom. (your repo link is down so I can't look into the CSS).

  • Amiolemen Best•10
    @BestOlumese
    Submitted 5 months ago

    QR Code Component

    2
    P
    Will Cooley•190
    @CooleyWC
    Posted 5 months ago

    Looks great! Perhaps check the padding (increase) for the text to make it look like the source example.

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

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