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

https://github.com/Papi84/frontened-parctice-13.09.2024/blob/main/styl

accessibility
Papi•280
@Papi84
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’m most proud of how I effectively utilized HTML and CSS to create a visually appealing and responsive design. The project demonstrated my ability to implement modern web design principles and achieve a clean, user-friendly interface.

Next time, I would focus on enhancing cross-browser compatibility and optimizing performance. Additionally, I’d explore incorporating more advanced CSS features and JavaScript to add interactive elements, which could further improve the user experience.

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

One of the main challenges was achieving consistent styling across different browsers and devices. I tackled this by using CSS resets to standardize default styles and thoroughly testing the design on various platforms to ensure compatibility. Additionally, I faced difficulties with responsive design, particularly with complex layouts. To address this, I utilized media queries and flexible grid systems to adapt the layout effectively. These steps ensured a cohesive and accessible user experience across different environments.

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

I would appreciate feedback on optimizing my CSS for better performance and scalability, particularly in handling complex layouts. Additionally, guidance on improving cross-browser compatibility and suggestions for integrating more advanced interactive features with JavaScript would be valuable. Any advice on refining my design for enhanced user experience and accessibility would also be greatly appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Wendy•2,130
    @wendyhamel
    Posted 8 months ago

    Hi there!

    This is a very nice solution to this challenge.

    Normalising your css is a very good idea. It lets you focus on the design, without the hastle of working out bugs in the different browsers.

    Your css code looks neat and your class names are discriptive. This makes your code easy to maintain. I would change a few names to make it more accurate: for example

    • the card-overlay name => it's not really an overlay of the card
    • and the double class name for card-day (with the addition :first-child) => this first one is not really the day

    But this is me looking really hard to find things to improve for you.

    You could work on the semantic HTML by using more discriptive HTML tags like <section> or <article> for the card.

    You asked for help with optimizing the CSS and cross-browser compatibility, or more interactive features with JavaScript. In the case of this challenge I would discurrage that. It is a simple card, and adding to much transitions and animations can distract or even irritate users. But in other projects it may be usefull. If I have the time to look for improvements on some of your other solutions, I will keep this in mind.

    Over all, a neat solution for this challenge. I like the responsiveness without the need for or use of media queries. This card does not need them and you used nice other solutions.

    Happy coding!

  • Papi•280
    @Papi84
    Posted 8 months ago

    Thanks a lot @poissonfou

  • Emerson Lima•200
    @poissonfou
    Posted 8 months ago

    Great work. Very smart to use the ::before pseudo-element to create the overlay!

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.

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