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

HTML, CSS, capture and sketch to measure cards and div's

materialize-css
José Isaias Lourenço•20
@IsaiasLourenco
A solution to the NFT preview card 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 spent a lot of time on creating and measuring the cards and div's, but I think I managed to do better than last time, I was also able to separate all the CSS files, leaving everything more organized and better to maintain later, I believe I'm on the right track but I still need a lot of training in CSS and Front End

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

Once again, I found it difficult to find a way to measure, leaving everything as close as possible to the original, I will continue looking, and I accept suggestions, for tools to measure in pixels the components to be built and styled, this would make the work much easier.

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

I think I can help with planning and analysis before the code itself, as I said above, the concern with a tool that gives us a quick and efficient way to find all the measurements in pixels of the components would be great help in planning. I like to plan before I start coding

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on José Isaias Lourenço's solution.

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 1st-party linked stylesheets, and styles within <style> tags.

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.