Skip to content
OverviewSolutions
4
Comments
4

Nathan Perkins

@nathan-perkins80 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

  • Recipe Page

    #bem
    Nathan Perkins•80
    Submitted 11 months ago
    0 comments

  • Social Links Profile Challenge

    #bem
    Nathan Perkins•80
    Submitted 11 months ago

    For this project I intended to only use HTML and CSS. While I was able to make the links navigable via the tab key, I could not figure out how to make them navigable via the arrow keys without incorporating JS. I would like to know if there is a way to make this happen only using HTML/CSS or if JS is required to incorporate this feature.

    0 comments

  • Blog preview card using CSS

    Nathan Perkins•80
    Submitted 12 months ago

    I would like to know if there are other things I should consider when it comes to organizing my CSS or just improving my CSS in general. I know that this smaller project doesn't necessarily require as much organization, but I wanted to aim for organization as if this were a much larger project.

    1 comment

  • QR code component using CSS

    Nathan Perkins•80
    Submitted about 1 year ago

    I would like to know if there is a better way to organize my CSS. I decided to use variables to practice for bigger projects, but I am curious if my methods for positioning and spacing can be improved.

    0 comments

Latest comments

  • Gurbala Laurent•110
    @laurentGurbala
    What are you most proud of, and what would you do differently next time?

    I am particularly proud of having managed to efficiently implement a responsive design with CSS Grid and Flexbox, while integrating variable fonts. The layout adapts perfectly to different screen formats and the use of CSS Counter for the recipe steps was a real plus to make the content dynamic and easy to maintain.

    If I had to do this project again, I would spend more time on accessibility.

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

    One of the biggest challenges was managing the CSS grid for the nutritional information. I wanted each row to be well aligned with the labels on the left and the values ​​on the right, while keeping a consistent underline. By using CSS Grid and adjusting the alignment with grid-template-columns and nth-last-child, I managed to achieve the desired rendering while keeping a flexible and maintainable structure.

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

    I would like to get more specific feedback on using CSS Grid in my project, especially for the layout of the nutritional information. While the current layout works well, I am wondering if there are more optimized techniques or best practices I could apply to make the grid even more efficient, flexible and maintainable. Also, I would like some advice on managing bullet points in lists.

    Recipe page

    #bem
    1
    Nathan Perkins•80
    @nathan-perkins

    Hello @laurentGurbala, congratulations on completing this project! I really enjoyed seeing the way that you organized your CSS into various files; I may play around with that in future projects.

    I wish that I could give you feedback on using grid for the nutritional information, but I do not feel that I know enough about CSS grid at this point to give confident advice in that area.

    One thing I did notice as I was reviewing your HTML was that you employed section elements without using an aria-labelledby or aria-label attribute. I learned as I was working on this project that the section element does not automatically include the role of "region", you must add an aria-labelledby, aria-label, or title attribute to incorporate it as a semantic element. The way you currently have it set up, it essentially acts just as a div.

    I hope this helps, good luck on future projects!

  • Nathan Perkins•80
    @nathan-perkins

    Hello @KP1976, fantastic job on completing this project! I looked through your project and am impressed by the amount of thought and attention to detail that you put behind this project. I appreciate your attention to different browsers and mediums by which people may be viewing your project. I also appreciate the comments you included within your CSS file which were helpful for reading and understanding your code. Your project mimics the original design very well, and you made sure to incorporate semantic HTML to keep your project accessible.

    I think you are more than ready to tackle the challenge of making your links navigable via the keyboard. While I do not believe that was a requirement for this project, I think it would be a fun challenge that would help make your project even more accessible. I also noticed that you included only two sizes for your component across different screen sizes. There are some mid-range screen sizes where this looks a little awkward. You could consider adding a third size that would better suit mid-range screen sizes such as ipads, tablets, etc.

    Overall, great job on this project! I look forward to seeing your future projects!

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

    I feel proud of knowing what I'm doing in the code but I hope to find more challenges so I can learn from them.

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

    I didn't find any problems in this challenge, it's similar to the previous QR code challenge.

    Blog preview card solution with flex

    2
    Nathan Perkins•80
    @nathan-perkins

    Hello and congratulations on completing this challenge! It looks like you did a nice job with the layout of the card and getting your solution to look similar to the given design. I also enjoyed seeing you employ CSS variables. If you want to hone it in even more, reference the Figma file to get more of those details locked in!

    One thing you may want to consider as you are completing these first projects is to go ahead and incorporate semantic html. A <main> or <article> tag in place of some of your <div> tags could help improve the accessibility of your solution. Even though this project is small, these are important concepts to practice now in preparation for those bigger projects.

    I enjoyed looking at your solution, and I hope to see you post more soon!

  • Carlos Marte•160
    @carlosmarte23
    What are you most proud of, and what would you do differently next time?

    I’m proud of completing this first challenge because, after watching countless tutorial videos, I was able to do it without much external help. Even though it’s really simple, it gives me more confidence in my ability. I was proud of implementing CSS variables which, while not very practical in this example, are probably a must in a full project, so it’s better to get used to them now.

    If I have to do the challenge again, instead of using Flexbox, I’d use Grid for the layout to practice it more.

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

    The most difficult part was getting the spaces exactly like the design and making the text on the card centered with the exact spacing. I redid the HTML layout that I had in the beginning and used a simpler one. Using only Flexbox, I managed to do it. Next time, I’d try not to overcomplicate things and keep it simple from the beginning.

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

    I’d like to get feedback on how to set up the dimensions and font sizes without using pixels directly. I still don’t know much about how to calculate it and which dimensions to use, e.g., em, rem, etc.

    Simple QR Component Card with Flexbox

    1
    Nathan Perkins•80
    @nathan-perkins

    Hi Carlos, great job on completing this first challenge! Similar to you, I found that completing this challenge boosted my confidence in my ability to apply my knowledge to practical situations.

    Concerning avoiding using pixels explicitly, ems and rems are probably your best bet. Ems are based on the font size of their parent element. If the parent element does not have a specified font size, then the size will be determined by going up the tree until a font size is found. If no font size is found, then the em will generally default to 16px. Therefore, 2em would translate to 32px. If you explicitly set the parent element's font size to 12px instead, then 2em would automatically adjust to be 24px. A problem can arise when using ems, however. You use ems where the parent element also uses ems, you get a compounding effect and things can get out of control quickly. For example, lets say you set an element's font size to 2em. Based on the default size (16px), this would calculate to 32px. But if you then introduce a child element and set the size to 2em, it would be based on the 32px size of the parent element and would calculate to 64px. Because ems can get out of control quickly, rems (or "root ems") were introduced that work very similarly to ems, but they instead base their size on the root element (the html element), and will not compound the way ems do. To learn more, I found this video (https://www.youtube.com/watch?v=_-aDOAMmDHI) and this article (https://www.digitalocean.com/community/tutorials/css-rem-vs-em-units) very helpful!

    Other than that, use the screenshot and accessibility reports that FM gives you to continue refining your solution. One thing I learned as I was completing the challenge was that img elements have a display of inline by default, which adds a little extra space between the image and the text underneath it in addition to the margin/padding that you specify. This may help you align your elements more closely to the original.

    Marked as helpful