Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

I used javascript for my first time

samandavari•20
@samandavari
A solution to the FAQ accordion card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I did my first javascript but there are some problems i couldnt solved so i really like to give me some solutions for better UI and coding, first i couldnt place the box on top of the women pic how shoud i do that ? second if i toggle all accs together it will pop out the wrapper how should i fix that? third how should i hide parts of my picture ?it is not hidden well. i `ll be glad to see your tips

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • samandavari•20
    @samandavari
    Posted over 3 years ago

    tnx for your help

  • Marcus Hugo•365
    @marcus-hugo
    Posted over 3 years ago

    Looks good!

    For the box svg , add it to the html before the div .image, then in the css set it to position: relative and position it with top: and left: like this

    display: inline;
    position: relative;
    left: -177px;
    top: 282px;
    

    Try removing the heights from the .wrapper and .accwrapper, that should keep it from popping out of the wrapper.

    For hiding the images, it looks like you could add the bg-pattern to the .image div and then set it to position: relative and z-index: -1, and overflow: hidden, though I'm not sure it will work?

    I ended up using background-image: with url().

    background-image: url(../images/illustration-woman-online-desktop.svg), url(../images/bg-pattern-desktop.svg);
            background-position:  -76px, -571px -248px;
            background-size: 472px, 966px;
            background-repeat: no-repeat;
    

    Hope this helps! 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