Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 11 months ago

Html, CSS native Blog Preview

Adam Bethlehem•90
@adambeth
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I have decided not to use any frameworks such as Bootstrap or Tailwinds

Instead of trying to design it from scratch, I used the Figma designs this time, which made the experience a whole lot better.

Just from the past two challenges I feel like by doing rather than tutorial hell, I have learned actual concepts and techniques rather than just following along

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

I found it difficult to know if all my need to be displayed: flex. It looks like the Figma designs, but I'm not sure if that's correct.

I'm still finding it hard to figure out the units for sizing. Should the view be 100vh or set a px value? When and how to set width/height for elements... I'm sure I just need some more practice

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

I would like to know how you decide what divs need to be flexboxes and how you decide and what units you use to create the widths and heights or do you just add margins and let the parent decide the size of the child?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    JackEG•90
    @Yakub357
    Posted 11 months ago

    Dear Adam Bethlehem, You may add some padding inside div container which cover-up the texts or add some margin to your text. both for titles (h1)and for P-text. Also there is small discrepancy between the design color of secondary text, p-text and the solution, you may change the color property

    Marked as helpful

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
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

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

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

Log in with GitHub