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

Project using HTML,CSS,Javascript

arthurns1•50
@arthurns1
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?

That i could do this project, was difficult but i could do this

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

i encountered some challenges refered to reacreate the design but was a good deal

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

how i can do this to work in any screens? Who is the best way to do this project?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Natali 👻 Grimm•1,190
    @Grimm-N
    Posted 9 months ago

    Great job on your project—it’s looking amazing! The effort and creativity you’ve put into this really shine. 🌟

    A few quick suggestions to take it to the next level:

    1. The inline styles in your HTML are just for demonstration purposes. Move them into your CSS file to keep things tidy and easier to maintain.
    2. Pixels are kinda old-school! Using units like em, rem, or percentages gives your design more flexibility and makes it way more responsive.
    3. To center an element like in the design, try using Flexbox for the container:
      .container {  
          display: flex;  
          justify-content: center;  
          align-items: center;  
          height: 100vh; /* Example height */  
      }  
      
    4. For medium-width screens, consider switching to the mobile layout (like placing the image on top) a bit earlier. And don’t forget, you can use responsive typography by adjusting the text size gradually with media queries or clamp().

    You're absolutely crushing it—keep up the awesome work!

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