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

article component slution

Taiwo Sumayyah•150
@Sumta4real
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?

Finally getting hang o responsive design

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

I was not able to style the bottom component as required. And I also had chellenge with uing javascript to change the compnents of the bottom div

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

I would appreciate help with my getting better on Javascript, any recommendations on practical hands on tutorial or useful books. I woul also appreciate corrections on best way to style the bottom div

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Michał•290
    @miedzygalaktycznygit
    Posted 9 months ago

    Hello, I’m not sure if my way is the best because I’m also just starting to learn, but I just made another div for socials, and with JS, I made it pop up on the screen when a button is clicked and disappear when clicked again. On the mobile design, I made the div with the photo disappear and replaced it with socials.

    
    button.addEventListener('click', () => {
        if (mediaQuery.matches && !landscapeQuery.matches) {
            divPersonalInfo.style.display = 'none';
            divSocials.style.display = 'flex';
        } else {
            if (isToggled) {
                divSocials.style.display = 'none';
            } else {
                divSocials.style.display = 'flex';
            }
            isToggled = !isToggled;
        }
    });
    
    button2.addEventListener('click', () => {
        if (mediaQuery.matches && !landscapeQuery.matches) {
            divSocials.style.display = 'none';
            divPersonalInfo.style.display = 'flex';
        }
    });
    
    • You can look on my code and feel free to use it to try to improve Your website.
    • And I think that You have small mistake that's making this bottom div looks weird
    background: linear-gradient(to bottom, white 90%, hsl(217, 19%, 35%) 100%);
    

    You simply write "background-color" and You should udes "background" instead

    • I hope that You can find my message helpful and I wish You best in Your future projects.

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