Skip to content
Submitted almost 2 years ago

Responsive QR Code

DevMedic11•20
@DevMedic11
A solution to the QR code component challenge
Preview (opens in new tab)Code (opens in new tab)

Solution retrospective

When it comes to best practices, i know the roars of "mobile-first" will be echo'd through the industry...but what does that really mean? Any tips for how to start designing small, then making things "big"?

Code

Please log in to post a comment

Log in

Community feedback

  • Tushar Biswas•4,060
    @itush

    Congratulations on completing the challenge! 🎉

    Welcome to the platform! 🎉 We're thrilled to have you here and excited to see your progress 💪as you continue your front-end development journey.

    Your solution looks nice on larger screens :)

    • On smaller screens you may want to increase the size of the card.

    • The language of the document is missing. Identifying the language of the page or page elements allows screen readers to read the content in the appropriate language. It also facilitates automatic translation of content.

    • Image alternative text is not present. Each image must have an alt attribute. Without alternative text, the content of an image will not be available to screen reader users or when the image is unavailable. These might look very frivolous but these are accessibility issues.

    In my projects:

    • I always start with mobile-first workflow.
    • I use at least one main element for a page (entire content goes into the main, if I'm not using header & footer), and avoid divs as much as possible and use section and article element wherever I can.
    <body>
<main>
All content 
</main>
</body>

    • I Use relative units as much as possible and avoid absolute units whenever possible.

    • If you are someone who is just starting out with front-end development, I strongly suggest starting with the QR code component project(which you did). Also in the challenges page you may filter by (Newbie, HTML&CSS) sort by (easier first) to select projects that will help you solidify your foundation. To avoid any potential knowledge gap⚠️ please first solidify HTML, CSS, JS fundamentals, make few projects only with the trio and then move on to any framework or library.

    • I remember when I started out, I made countless mistakes and spent long hours searching for solutions. But hey, you don't need to go through the same struggles! 🙌 To help you shorten the learning curve, I recommend going through the following articles. They contain valuable insights that can make your journey smoother:

    📚🔍 12 important CSS topics where I discuss about css position, z-index, box-model, flexbox, grid, media queries, mobile-first workflow, best practices etc. in a simple way.

    📚🔍 11 important HTML topics where I discuss about my thought process and approach to convert a design/mock-up to HTML along with important topics like block and inline elements, HTML Semantic Elements, accessibility.

    I hope you find these resources somewhat helpful in your coding adventures and get answers to your questions! 🤞

    I'm eagerly looking forward to seeing the amazing projects you'll create in the future! 🚀💻

    Keep up the fantastic work and happy hacking! 💪✨

    Feel free to ask more questions☺️

  • VictorMtzCodes•350
    @VictorMMartinezJr

    Basically what it means is always start with the mobile device in mind. Create the website for mobile devices first then expand your way up tp desktops. Most people will view the web app on a mobile device nowadays. Another reason is that mobile devices are a lot less powerful than desktops, therefore we should try to not have all the things we have on the desktop devices also included in the code for the mobile devices. It will always be easier to add items for desktop later than to remove items for mobile after developing for a desktop first also.

  • Chris Cablish•310
    @ChrisCablish

    Hey there,

    Most (if not all) of the challenges on this website provide multiple designs for the same challenge. Navigate to the provided mobile design and flesh that one out first. Once you have completed it, move on to the tablet (if applicable), and finally the desktop design. My understanding of the rationale is that it is fundamentally easier to expand a compact design than it is to shrink down a larger (desktop) design. Also, internet connections tend to be less stable on mobile, so having the compiler encounter the mobile design first helps with performance on mobile devices. Be sure to check into media queries for CSS responsive design if you haven't already done so. Hope this helps.

    -Chris

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord