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

Article component (broken version)

P
shpokas-io•150
@shpokas-io
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?

Proud that i tried to use as semantic as possible in HTML section , but I think that way is much harder and I don't understand fully why things don't work as they should

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

dekstop version not working properly, instead of two column horizontal it is mobile one column, in mobile aspect of it doesn't pop up share section

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

THere is alot of problem with this one but i`ll just raw dog it and leave it for later fixing

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Austin•430
    @astnio
    Posted 11 months ago

    Seems as though you are already aware, but this does need quite a bit more work done in getting the layout configured.

    I do like what I think you were going for, however. In particular the animation you setup when clicking the share button. It isn't working fully now, but I can see what you were going for and I really like it!

    Your HTML also looks really good, just some more work on your CSS and I'm sure it will all come together.

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