Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Article preview component using Angular

angular
Roraima Lugo González•510
@roraima1986
A solution to the Article preview 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?

sin comentarios

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

sin comentarios

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

sin comentarios

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Muhammad Amoo•220
    @DruxAMB
    Posted over 1 year ago

    Hi Rorsima, Congratulations you finished the challenge!!! Just one recommendation that might help you with your projects.

    You can use a utility class to center you content in the middle and prevent that stretch all away the viewport width. In your css file

    .container { widht: 90%; // in small screens it will take the 90% of the viewport width max-width: 1100px; // in big screens won't grow more than 1100px viewport width margin-inline: auto; //margin left and right will center you content } In you html

       <main class="main-section">
          content
      </main>
    </div>```
    
    Hope this help you!
    
    ***DruxAMB***
    
    Marked as helpful
  • Petrit Nuredini•2,860
    @petritnuredini
    Posted over 1 year ago

    Congratulations on completing your Frontend Mentor challenge! Here are some quick best practices recommendations:

    • HTML Semantics: Good use of semantic HTML elements. Consider using <article> for your card and <section> for distinct sections within the card.
    • CSS Structure: Make sure your CSS is organized and commented for better readability and maintainability.
    • Responsive Design: Test your design on various devices to ensure it's fully responsive.
    • Angular Practices: Great job using Angular for logic handling! Ensure to follow Angular's best practices, like modular code and using services for data handling.
    • Accessibility: Make sure all interactive elements are accessible. Use aria-labels for icons and buttons where necessary.

    Keep exploring and refining your skills. Here are some resources for further learning:

    • HTML Semantic Elements
    • CSS Guidelines
    • Angular Best Practices
    • Web Accessibility Guidelines

    Keep up the great work, and happy coding! 🚀

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