Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
18
Comments
13
P
Marcus
@marcus-hill

All comments

  • P
    Christian•300
    @christianb3ll
    Submitted 8 months ago
    What specific areas of your project would you like help with?

    Any pointers appreciated!

    A Password Generator App

    1
    P
    Marcus•310
    @marcus-hill
    Posted 8 months ago

    Great job with this, it looks excellent and works perfectly!

  • Rafi Rachmawan•210
    @rafirachmawan
    Submitted 8 months ago
    What are you most proud of, and what would you do differently next time?

    deepen the logic of calculations in javascript

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

    The challenges I experienced here were calculator calculations and to solve them I extracted on chatgpt and read the documentation on javascript

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

    I asked whether the logic in my project calculations was correct or not?

    Html,CSS,JS,TailwindCss Text Editor VSCode

    1
    P
    Marcus•310
    @marcus-hill
    Posted 8 months ago

    Hi @rafirachmawan, good job with this solution. The design looks good and it is impressive that you've done it in react.

    The tip amount seems to only update when I select a new tip % though, rendering the number of people input value useless initially.

    Hopefully you can get the usability fixed and it will be great!

  • P
    Leonardo Almeida•370
    @leonardoalmeida7
    Submitted 8 months ago

    time tracking solution with display grid

    1
    P
    Marcus•310
    @marcus-hill
    Posted 8 months ago

    Hey @leonardoalmeida7, I think you've done a fantastic job. It matches the design and works perfectly. Although you've mentioned you used React, I cannot seem to see this in your code?

    Good luck in the future!

  • newwdeveloper•110
    @newwdeveloper
    Submitted 9 months ago
    What are you most proud of, and what would you do differently next time?

    1ST TIME ATTEMPTED TO SWICH PAGE ON EVENT lISTENER

    HTML,CSS,JAVASCRIPT

    1
    P
    Marcus•310
    @marcus-hill
    Posted 8 months ago

    Hi @newwdeveloper, good use of React to complete this project. This isn't something I have learnt yet so cannot offer any feedback on that.

    However, in order to meet the design your solution needs a number of improvements:

    • Only the success message is in a reasonably sized container for me, the rest of your project spans the full size of my browser.
    • Missing the active effect on the button and also the error message (without using the pop up error message)

    Best review your CSS/HTML as per the design and this can be perfect!

    Marked as helpful
  • Chandan Roy•90
    @roychandu
    Submitted about 1 year ago

    Article Preview Component

    1
    P
    Marcus•310
    @marcus-hill
    Posted 9 months ago

    Hi @roychandu, good job with this - I think you've made a good effort but there is definitely scope for some improvement. I am unable to access your GitHub repository so I am providing this feedback visually & with access to the dev tools:

    • There does not appear to be a max width on your card in rem - instead it is set to 60% which makes the card incredibly large on bigger displays, which isn't good.
    • As this happens, the profile picture and author's name overflows out of the card with the text also scaling incredibly large - given you have a font size set in vm. I do not see why you have the font size set in vm which is a percentage of the viewpoint width. I would recommend using rem for your fontsize, which scales with the user's browser default.
    • On mobile, there appears to be a significant amount of white space at the bottom of the card. I can see you are utilising flexbox with flex-direction: column - however there appears to be no use of justify-content or align-items which could have created the required spacing between these elements, such as the use of space-between.
    • On pressing the share button in mobile view, there is no button visible which allows for it to be toggled away again.
    • There also appears to be no max width on the image, which will continue to scale so large or so small (to the point that little of the image is visible) as I switch to mobile view which is quite a problem for this responsive design.

    With a few improvements, this design will be much better. Remember to allow access to your Github Repository (I am assuming you have forgotten to make it public).

  • Maren Ehlers•230
    @MarenOelixtown
    Submitted 9 months ago
    What are you most proud of, and what would you do differently next time?

    👉I tried to get a smooth transition between the different output sizes. With trial and error I came to the conclusion that if you give an element a max-width and centre it with margin-left and margin-right ‘auto’, you could already achieve a lot. In addition, clamp()-function helped me not only with font-sizes, but also with the scaling of images and spacing.

    🔎 In the future, I would also like to learn more about tricks and tips for smooth transitions between different output devices to achieve a responsive design.

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

    👉 First time that I used the 'background-image' with the linear-gradient and also first time I created a section devider like this.

    • background-image - This helped me for designing the footer-background.

    👉 I liked using the picture-element in this way for the desktop media-query without css. Using the picture-element and the srcset attribute also ensures that only the necessary images are loaded depending on the screen size.

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

    I have spent some time thinking about how to structure the html and also how to use BEM correctly. There is certainly room for improvement. I am looking forward to your suggestions.

    It would be interesting to know whether all images (with the exception of the logo) should be considered decorative. In this case I did it, and provided a null (empty) alt text (alt="") so that they can be ignored by assistive technologies. What do you think?

    Meet landing page / responsive design for different devices

    1
    P
    Marcus•310
    @marcus-hill
    Posted 9 months ago

    Hi @MarenOelixtown, I think you've done a great job with this. It matches the design and looks amazing. The CSS looks pretty clean.

    However, there do appear to be a couple of issues with the responsive nature of the design. At approximately 1200px, the content at the top is very much squashed together and not vertically aligned. Also, the "Smarter Meetings" header looks like it is meant to be hidden for tablets, as per the figma design (but you may not have noticed that).

    Good luck in the future!

  • Megha S Patil•100
    @meghaspatil1
    Submitted 9 months ago
    What are you most proud of, and what would you do differently next time?

    I loved the way to takle testimonial with grid and more knowledge on CSS grid.

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

    Challenges came across arragement , tried most of way like grid area, grid column and row count.

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

    confusion with handling css-grid-area and grid-column or grid-row.

    Responsive landing using CSS grid

    1
    P
    Marcus•310
    @marcus-hill
    Posted 9 months ago

    Hi @meghaspatil1, good job with this, it looks good but here's some feedback for you:

    • Your solution looks much taller than the design. Perhaps you could set a max-height on your testimonials container?
    • Doesn't look like you have loaded the required font, although it is referenced in the CSS
    • There is a lack of responsiveness in this design. On smaller screens (and mobiles), your container with all testimonials is pushed to the right of the screen and half of them are hidden. Might be worth seeing if you can center the cards any better.
  • Djamel1133•910
    @Djamel1133
    Submitted 9 months ago
    What are you most proud of, and what would you do differently next time?

    I did it with flexbox (not with grid) and started using logical units instead of max-width and max-height. I used a mobile-first approach, which saved me a lot of time. I'm happy to follow my learning path and to be with you 🥰.

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

    Responsiveness again

    Four card feature

    1
    P
    Marcus•310
    @marcus-hill
    Posted 9 months ago

    Hi @Djamel1133, good work with this! I like your use of flex box in order to create the finished design, which works as one of the multiple ways of completing this challenge.

    Here's some feedback for you:

    • The coloured line at the top of each card appears to have been done differently for the Supervisor card compared to the other three. I would stick to using border-top: to achieve this (as you have done with the Supervisor card), rather than utilising the <hr> element and then sticking a border-top: on top, which overlaps with the border-radius.
    • The box-shadow doesn't appear to match the design brief, it was specifically looking for one on the bottom of each card.
    • It's great you are using responsive CSS units for the margin and font sizes, which scales well with a user's default browser font size.
    • Did you need to make each card itself a flexbox (which you've done by targeting .cards div)? By taking off display: flex on these, the only element out of place is the icon which could then be aligned to the right in another way? The elements in the card are already block elements and so will already stack like a column, questioning whether flexbox was needed.

    Good luck in the future!

  • nebiyoudawit•50
    @nebiyoudawit
    Submitted 9 months ago

    recipe

    1
    P
    Marcus•310
    @marcus-hill
    Posted 9 months ago

    Looks like the wrong design/file has been submitted

  • kaleb birhanu•60
    @kalebbirhanu
    Submitted 10 months ago

    grid system

    1
    P
    Marcus•310
    @marcus-hill
    Posted 10 months ago

    Hi Kaleb, I'm unable to access your Github Repo (perhaps it isn't public?), however I can provide some feedback based on your live preview link and the dev tools:

    • Good start with the mobile design first, I can see this is where you've put your effort and began with mobile design, which is best practice.
    • Good use of some semantic HTML, however I think you could have used more, such as the <article> tag and also the <section> tag.
    • On a desktop, your solution does not meet the design and is far too wide, extending nearly to the left and right hand side of my screen. Whilst it works on a smaller screen size (of 1000px), it begins to get far too big on anything larger. From looking at the dev tools, there doesn't appear to be a max-width set on the .total class div, which is causing it to grow and grow in size until the content is stretched way beyond necessary.

    Keep up the good work and I am sure this will be much better with a few changes.

  • Khrystyna Horbenko•230
    @KristinaHorbenko
    Submitted 10 months ago

    bam blocks, adaptive layout, flex boxes

    1
    P
    Marcus•310
    @marcus-hill
    Posted 10 months ago

    Great job Kristina, your preview matches the design files perfectly and I think the flexbox use was a great way to do it. However, at 375px (mobile size) the social card is very squashed. Perhaps a media query could solve this? Keep up the good work!!

  • Begli Amanov•80
    @begli-amanov
    Submitted 10 months ago
    What are you most proud of, and what would you do differently next time?

    Everything is outlined in the Updated readme file.

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

    It was really annoying to tweak responsive text without media queries. Need to find a way to make it more effective. The approach was like from 90s. To much manual setup. Or maybe we are just too lazy?!

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

    I am mostly interested in if my html and css semantics are robust enough and is my approach with cal() function good enough for responsive text on the page.

    Fairly responsive Blog Preview Card

    2
    P
    Marcus•310
    @marcus-hill
    Posted 10 months ago

    Hi Begil, great job on the design! I am only starting out but here is some feedback I have:

    • Even with the use of a media query, your card is still too big for a small viewport (below 370px) and leads to the left hand side of the content being hidden.
    • I like your use of CSS variables, I haven't used these before but it prevented a lot of repetition of colours and styles.
    • I think the way you added the hover effect was quick by selecting multiple classes, but I don't believe this was required as per the design brief (only the name should apply)

    Good luck with your learning, you're doing a great job!

  • James Morrissey Jr•100
    @JammiM
    Submitted 10 months ago

    Flexbox

    3
    P
    Marcus•310
    @marcus-hill
    Posted 10 months ago

    Hi James,

    The design looks good and I think you have done well with that. However, the obvious issue is the positioning of the card which is not currently in the middle of the screen. Setting a min-height on the body element should solve this problem I believe.

    Hope that helps!

    Marked as helpful

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

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