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

Article preview component with HTML, sass and js

sass/scss
P
wideirp•280
@wideirp
A solution to the Article preview component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

I would like to add an animation slide in but I don't know much about CSS animations. If you can help me out, I would appreciate it!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Flávio Júnior•180
    @flavin-jr
    Posted 11 months ago

    Assessment of the Solution

    1. Does the solution include semantic HTML?

      • Yes, the solution includes semantic HTML. Elements such as <header>, <main>, <article>, and <footer> are used appropriately, providing clear meaning and improving the document's readability and accessibility.
    2. Is it accessible, and what improvements could be made?

      • Yes, the solution is accessible. The use of semantic elements aids screen readers and other assistive technologies in understanding the content and its structure. To further enhance accessibility, consider adding aria-labels or descriptive alt attributes for images.
    3. Does the layout look good on a range of screen sizes?

      • Yes, the layout is responsive. Media queries are employed to adjust the design for different screen sizes, ensuring that it looks good on both large screens and smaller devices. This approach maintains usability and aesthetics across various devices.
    4. Is the code well-structured, readable, and reusable?

      • Yes, the code is well-structured, readable, and reusable. The use of semantic HTML and organized CSS rules contributes to a clean and maintainable codebase. SCSS mixins and variables enhance reusability and consistency, making the styling easier to update and manage.
    5. Does the solution differ considerably from the design?

      • No, the solution aligns closely with the design. The semantic HTML and responsive layout ensure that the design principles are preserved across different devices and screen sizes, effectively translating the design into a functional and visually appealing web page.

    Assessment of the Solution

    1. Does the solution include semantic HTML?

      • Yes, the solution includes semantic HTML. Elements such as <header>, <main>, <article>, and <footer> are used appropriately, providing clear meaning and improving the document's readability and accessibility.
    2. Is it accessible, and what improvements could be made?

      • Yes, the solution is accessible. The use of semantic elements aids screen readers and other assistive technologies in understanding the content and its structure. To further enhance accessibility, consider adding aria-labels or descriptive alt attributes for images.
    3. Does the layout look good on a range of screen sizes?

      • Yes, the layout is responsive. Media queries are employed to adjust the design for different screen sizes, ensuring that it looks good on both large screens and smaller devices. This approach maintains usability and aesthetics across various devices.
    4. Is the code well-structured, readable, and reusable?

      • Yes, the code is well-structured, readable, and reusable. The use of semantic HTML and organized CSS rules contributes to a clean and maintainable codebase. SCSS mixins and variables enhance reusability and consistency, making the styling easier to update and manage.
    5. Does the solution differ considerably from the design?

      • No, the solution aligns closely with the design. The semantic HTML and responsive layout ensure that the design principles are preserved across different devices and screen sizes, effectively translating the design into a functional and visually appealing web page.

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

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