Repository: sayyedaaman2/faq-accordion-main
Branch: main
Commit: b4b58cf7ade1
Files: 9
Total size: 26.9 KB

Directory structure:
gitextract_r18s7epf/

├── .gitignore
├── README-template.md
├── README.md
├── assets/
│   └── fonts/
│       ├── OFL.txt
│       └── README.txt
├── index.html
├── script.js
├── style-guide.md
└── style.css

================================================
FILE CONTENTS
================================================

================================================
FILE: .gitignore
================================================
# Avoid accidental upload of the Sketch and Figma design files
#####################################################
## Please do not remove lines 5 and 6 - thanks! 🙂 ##
#####################################################
*.sketch
*.fig

# Avoid accidental XD upload if you convert the design file
###############################################
## Please do not remove line 12 - thanks! 🙂 ##
###############################################
*.xd

# Avoid your project being littered with annoying .DS_Store files!
.DS_Store
.prettierignore

================================================
FILE: README-template.md
================================================
# Frontend Mentor - FAQ accordion solution

This is a solution to the [FAQ accordion challenge on Frontend Mentor](https://www.frontendmentor.io/challenges/faq-accordion-wyfFdeBwBz). Frontend Mentor challenges help you improve your coding skills by building realistic projects. 

## Table of contents

- [Overview](#overview)
  - [The challenge](#the-challenge)
  - [Screenshot](#screenshot)
  - [Links](#links)
- [My process](#my-process)
  - [Built with](#built-with)
  - [What I learned](#what-i-learned)
  - [Continued development](#continued-development)
  - [Useful resources](#useful-resources)
- [Author](#author)
- [Acknowledgments](#acknowledgments)

**Note: Delete this note and update the table of contents based on what sections you keep.**

## Overview

### The challenge

Users should be able to:

- Hide/Show the answer to a question when the question is clicked
- Navigate the questions and hide/show answers using keyboard navigation alone
- View the optimal layout for the interface depending on their device's screen size
- See hover and focus states for all interactive elements on the page

### Screenshot

![](./screenshot.jpg)

Add a screenshot of your solution. The easiest way to do this is to use Firefox to view your project, right-click the page and select "Take a Screenshot". You can choose either a full-height screenshot or a cropped one based on how long the page is. If it's very long, it might be best to crop it.

Alternatively, you can use a tool like [FireShot](https://getfireshot.com/) to take the screenshot. FireShot has a free option, so you don't need to purchase it. 

Then crop/optimize/edit your image however you like, add it to your project, and update the file path in the image above.

**Note: Delete this note and the paragraphs above when you add your screenshot. If you prefer not to add a screenshot, feel free to remove this entire section.**

### Links

- Solution URL: [Add solution URL here](https://your-solution-url.com)
- Live Site URL: [Add live site URL here](https://your-live-site-url.com)

## My process

### Built with

- Semantic HTML5 markup
- CSS custom properties
- Flexbox
- CSS Grid
- Mobile-first workflow
- [React](https://reactjs.org/) - JS library
- [Next.js](https://nextjs.org/) - React framework
- [Styled Components](https://styled-components.com/) - For styles

**Note: These are just examples. Delete this note and replace the list above with your own choices**

### What I learned

Use this section to recap over some of your major learnings while working through this project. Writing these out and providing code samples of areas you want to highlight is a great way to reinforce your own knowledge.

To see how you can add code snippets, see below:

```html
<h1>Some HTML code I'm proud of</h1>
```
```css
.proud-of-this-css {
  color: papayawhip;
}
```
```js
const proudOfThisFunc = () => {
  console.log('🎉')
}
```

If you want more help with writing markdown, we'd recommend checking out [The Markdown Guide](https://www.markdownguide.org/) to learn more.

**Note: Delete this note and the content within this section and replace with your own learnings.**

### Continued development

Use this section to outline areas that you want to continue focusing on in future projects. These could be concepts you're still not completely comfortable with or techniques you found useful that you want to refine and perfect.

**Note: Delete this note and the content within this section and replace with your own plans for continued development.**

### Useful resources

- [Example resource 1](https://www.example.com) - This helped me for XYZ reason. I really liked this pattern and will use it going forward.
- [Example resource 2](https://www.example.com) - This is an amazing article which helped me finally understand XYZ. I'd recommend it to anyone still learning this concept.

**Note: Delete this note and replace the list above with resources that helped you during the challenge. These could come in handy for anyone viewing your solution or for yourself when you look back on this project in the future.**

## Author

- Website - [Add your name here](https://www.your-site.com)
- Frontend Mentor - [@yourusername](https://www.frontendmentor.io/profile/yourusername)
- Twitter - [@yourusername](https://www.twitter.com/yourusername)

**Note: Delete this note and add/remove/edit lines above based on what links you'd like to share.**

## Acknowledgments

This is where you can give a hat tip to anyone who helped you out on this project. Perhaps you worked in a team or got some inspiration from someone else's solution. This is the perfect place to give them some credit.

**Note: Delete this note and edit this section's content as necessary. If you completed this challenge by yourself, feel free to delete this section entirely.**


================================================
FILE: README.md
================================================
# Frontend Mentor - FAQ accordion

![Design preview for the FAQ accordion coding challenge](./design/desktop-preview.jpg)

## Welcome! 👋

Thanks for checking out this front-end coding challenge.

[Frontend Mentor](https://www.frontendmentor.io) challenges help you improve your coding skills by building realistic projects.

**To do this challenge, you need a basic understanding of HTML, CSS and JavaScript.**

## The challenge

Your challenge is to build out this FAQ accordion and get it looking as close to the design as possible.

You can use any tools you like to help you complete the challenge. So if you've got something you'd like to practice, feel free to give it a go.

Your users should be able to: 

- Hide/Show the answer to a question when the question is clicked
- Navigate the questions and hide/show answers using keyboard navigation alone
- View the optimal layout for the interface depending on their device's screen size
- See hover and focus states for all interactive elements on the page

Want some support on the challenge? [Join our community](https://www.frontendmentor.io/community) and ask questions in the **#help** channel.

## Where to find everything

Your task is to build out the project to the designs inside the `/design` folder. You will find both a mobile and a desktop version of the design. 

The designs are in JPG static format. Using JPGs will mean that you'll need to use your best judgment for styles such as `font-size`, `padding` and `margin`. 

If you would like the design files (we provide Sketch & Figma versions) to inspect the design in more detail, you can [subscribe as a PRO member](https://www.frontendmentor.io/pro).

All the required assets for this project are in the `/assets` folder. The images are already exported for the correct screen size and optimized.

We also include variable and static font files for the required fonts for this project. You can choose to either link to Google Fonts or use the local font files to host the fonts yourself. Note that we've removed the static font files for the font weights that aren't needed for this project.

There is also a `style-guide.md` file containing the information you'll need, such as color palette and fonts.

## Building your project

Feel free to use any workflow that you feel comfortable with. Below is a suggested process, but do not feel like you need to follow these steps:

1. Initialize your project as a public repository on [GitHub](https://github.com/). Creating a repo will make it easier to share your code with the community if you need help. If you're not sure how to do this, [have a read-through of this Try Git resource](https://try.github.io/).
2. Configure your repository to publish your code to a web address. This will also be useful if you need some help during a challenge as you can share the URL for your project with your repo URL. There are a number of ways to do this, and we provide some recommendations below.
3. Look through the designs to start planning out how you'll tackle the project. This step is crucial to help you think ahead for CSS classes to create reusable styles.
4. Before adding any styles, structure your content with HTML. Writing your HTML first can help focus your attention on creating well-structured content.
5. Write out the base styles for your project, including general content styles, such as `font-family` and `font-size`.
6. Start adding styles to the top of the page and work down. Only move on to the next section once you're happy you've completed the area you're working on.

## Deploying your project

As mentioned above, there are many ways to host your project for free. Our recommend hosts are:

- [GitHub Pages](https://pages.github.com/)
- [Vercel](https://vercel.com/)
- [Netlify](https://www.netlify.com/)

You can host your site using one of these solutions or any of our other trusted providers. [Read more about our recommended and trusted hosts](https://medium.com/frontend-mentor/frontend-mentor-trusted-hosting-providers-bf000dfebe).

## Create a custom `README.md`

We strongly recommend overwriting this `README.md` with a custom one. We've provided a template inside the [`README-template.md`](./README-template.md) file in this starter code.

The template provides a guide for what to add. A custom `README` will help you explain your project and reflect on your learnings. Please feel free to edit our template as much as you like.

Once you've added your information to the template, delete this file and rename the `README-template.md` file to `README.md`. That will make it show up as your repository's README file.

## Submitting your solution

Submit your solution on the platform for the rest of the community to see. Follow our ["Complete guide to submitting solutions"](https://medium.com/frontend-mentor/a-complete-guide-to-submitting-solutions-on-frontend-mentor-ac6384162248) for tips on how to do this.

Remember, if you're looking for feedback on your solution, be sure to ask questions when submitting it. The more specific and detailed you are with your questions, the higher the chance you'll get valuable feedback from the community.

## Sharing your solution

There are multiple places you can share your solution:

1. Share your solution page in the **#finished-projects** channel of our [community](https://www.frontendmentor.io/community). 
2. Tweet [@frontendmentor](https://twitter.com/frontendmentor) and mention **@frontendmentor**, including the repo and live URLs in the tweet. We'd love to take a look at what you've built and help share it around.
3. Share your solution on other social channels like LinkedIn.
4. Blog about your experience building your project. Writing about your workflow, technical choices, and talking through your code is a brilliant way to reinforce what you've learned. Great platforms to write on are [dev.to](https://dev.to/), [Hashnode](https://hashnode.com/), and [CodeNewbie](https://community.codenewbie.org/).

We provide templates to help you share your solution once you've submitted it on the platform. Please do edit them and include specific questions when you're looking for feedback. 

The more specific you are with your questions the more likely it is that another member of the community will give you feedback.

## Got feedback for us?

We love receiving feedback! We're always looking to improve our challenges and our platform. So if you have anything you'd like to mention, please email hi[at]frontendmentor[dot]io.

This challenge is completely free. Please share it with anyone who will find it useful for practice.

**Have fun building!** 🚀


================================================
FILE: assets/fonts/OFL.txt
================================================
Copyright 2019 The Work Sans Project Authors (https://github.com/weiweihuanghuang/Work-Sans)

This Font Software is licensed under the SIL Open Font License, Version 1.1.
This license is copied below, and is also available with a FAQ at:
http://scripts.sil.org/OFL


-----------------------------------------------------------
SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
-----------------------------------------------------------

PREAMBLE
The goals of the Open Font License (OFL) are to stimulate worldwide
development of collaborative font projects, to support the font creation
efforts of academic and linguistic communities, and to provide a free and
open framework in which fonts may be shared and improved in partnership
with others.

The OFL allows the licensed fonts to be used, studied, modified and
redistributed freely as long as they are not sold by themselves. The
fonts, including any derivative works, can be bundled, embedded, 
redistributed and/or sold with any software provided that any reserved
names are not used by derivative works. The fonts and derivatives,
however, cannot be released under any other type of license. The
requirement for fonts to remain under this license does not apply
to any document created using the fonts or their derivatives.

DEFINITIONS
"Font Software" refers to the set of files released by the Copyright
Holder(s) under this license and clearly marked as such. This may
include source files, build scripts and documentation.

"Reserved Font Name" refers to any names specified as such after the
copyright statement(s).

"Original Version" refers to the collection of Font Software components as
distributed by the Copyright Holder(s).

"Modified Version" refers to any derivative made by adding to, deleting,
or substituting -- in part or in whole -- any of the components of the
Original Version, by changing formats or by porting the Font Software to a
new environment.

"Author" refers to any designer, engineer, programmer, technical
writer or other person who contributed to the Font Software.

PERMISSION & CONDITIONS
Permission is hereby granted, free of charge, to any person obtaining
a copy of the Font Software, to use, study, copy, merge, embed, modify,
redistribute, and sell modified and unmodified copies of the Font
Software, subject to the following conditions:

1) Neither the Font Software nor any of its individual components,
in Original or Modified Versions, may be sold by itself.

2) Original or Modified Versions of the Font Software may be bundled,
redistributed and/or sold with any software, provided that each copy
contains the above copyright notice and this license. These can be
included either as stand-alone text files, human-readable headers or
in the appropriate machine-readable metadata fields within text or
binary files as long as those fields can be easily viewed by the user.

3) No Modified Version of the Font Software may use the Reserved Font
Name(s) unless explicit written permission is granted by the corresponding
Copyright Holder. This restriction only applies to the primary font name as
presented to the users.

4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
Software shall not be used to promote, endorse or advertise any
Modified Version, except to acknowledge the contribution(s) of the
Copyright Holder(s) and the Author(s) or with their explicit written
permission.

5) The Font Software, modified or unmodified, in part or in whole,
must be distributed entirely under this license, and must not be
distributed under any other license. The requirement for fonts to
remain under this license does not apply to any document created
using the Font Software.

TERMINATION
This license becomes null and void if any of the above conditions are
not met.

DISCLAIMER
THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
OTHER DEALINGS IN THE FONT SOFTWARE.


================================================
FILE: assets/fonts/README.txt
================================================
Work Sans Variable Font
=======================

This download contains Work Sans as both variable fonts and static fonts.

Work Sans is a variable font with this axis:
  wght

This means all the styles are contained in these files:
  WorkSans-VariableFont_wght.ttf
  WorkSans-Italic-VariableFont_wght.ttf

If your app fully supports variable fonts, you can now pick intermediate styles
that aren’t available as static fonts. Not all apps support variable fonts, and
in those cases you can use the static font files for Work Sans:
  static/WorkSans-Thin.ttf
  static/WorkSans-ExtraLight.ttf
  static/WorkSans-Light.ttf
  static/WorkSans-Regular.ttf
  static/WorkSans-Medium.ttf
  static/WorkSans-SemiBold.ttf
  static/WorkSans-Bold.ttf
  static/WorkSans-ExtraBold.ttf
  static/WorkSans-Black.ttf
  static/WorkSans-ThinItalic.ttf
  static/WorkSans-ExtraLightItalic.ttf
  static/WorkSans-LightItalic.ttf
  static/WorkSans-Italic.ttf
  static/WorkSans-MediumItalic.ttf
  static/WorkSans-SemiBoldItalic.ttf
  static/WorkSans-BoldItalic.ttf
  static/WorkSans-ExtraBoldItalic.ttf
  static/WorkSans-BlackItalic.ttf

Get started
-----------

1. Install the font files you want to use

2. Use your app's font picker to view the font family and all the
available styles

Learn more about variable fonts
-------------------------------

  https://developers.google.com/web/fundamentals/design-and-ux/typography/variable-fonts
  https://variablefonts.typenetwork.com
  https://medium.com/variable-fonts

In desktop apps

  https://theblog.adobe.com/can-variable-fonts-illustrator-cc
  https://helpx.adobe.com/nz/photoshop/using/fonts.html#variable_fonts

Online

  https://developers.google.com/fonts/docs/getting_started
  https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Fonts/Variable_Fonts_Guide
  https://developer.microsoft.com/en-us/microsoft-edge/testdrive/demos/variable-fonts

Installing fonts

  MacOS: https://support.apple.com/en-us/HT201749
  Linux: https://www.google.com/search?q=how+to+install+a+font+on+gnu%2Blinux
  Windows: https://support.microsoft.com/en-us/help/314960/how-to-install-or-remove-a-font-in-windows

Android Apps

  https://developers.google.com/fonts/docs/android
  https://developer.android.com/guide/topics/ui/look-and-feel/downloadable-fonts

License
-------
Please read the full license text (OFL.txt) to understand the permissions,
restrictions and requirements for usage, redistribution, and modification.

You can use them in your products & projects – print or digital,
commercial or otherwise.

This isn't legal advice, please consider consulting a lawyer and see the full
license for all details.


================================================
FILE: index.html
================================================
<!DOCTYPE html>
<html lang="en">

<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <!-- displays site properly based on user's device -->

  <link rel="icon" type="image/png" sizes="32x32" href="./assets/images/favicon-32x32.png">
  <link rel="preconnect" href="https://fonts.googleapis.com">
  <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
  <link href="https://fonts.googleapis.com/css2?family=Work+Sans:ital,wght@0,100..900;1,100..900&display=swap"
    rel="stylesheet">
  <link rel="stylesheet" href="style.css">
  <title>Frontend Mentor | FAQ accordion</title>

  <!-- Feel free to remove these styles or customise in your own stylesheet 👍 -->
  <style>
    .attribution {
      font-size: 11px;
      text-align: center;
    }

    .attribution a {
      color: hsl(228, 45%, 44%);
    }
  </style>
</head>

<body>
  <main class="wrapper">

    <div class="faq-card bg-white">

      <div class="heading flex ">
        <img src="./assets/images/icon-star.svg" alt="" />
        <h1 class="text-dark-purple fs-700 fw-extra-bold">

          FAQs
        </h1>
      </div>

      <div class="question">


        <h4 class="text-dark-purple  fw-bold ">
          What is Frontend Mentor, and how will it help me?
        </h4>
        <img src="./assets/images/icon-plus.svg" class="plus" alt="plus" />
        <img src="./assets/images/icon-minus.svg" class="minus hidden" alt="minu" />
      </div>
      <p class="para hidden ">
        Frontend Mentor offers realistic coding challenges to help developers improve their
        frontend coding skills with projects in HTML, CSS, and JavaScript. It's suitable for
        all levels and ideal for portfolio building.



      </p>
      <hr>
      <div class="question">

        <h4 class="text-dark-purple  fw-bold">
          Is Frontend Mentor free?
        </h4>
        <img src="./assets/images/icon-plus.svg" class="plus" alt="plus" />
        <img src="./assets/images/icon-minus.svg" class="minus hidden" alt="minu" />

      </div>

      <p class="para hidden">
        Yes, Frontend Mentor offers both free and premium coding challenges, with the free
        option providing access to a range of projects suitable for all skill levels.

      </p>
      <hr>
      <div class="question">

        <h4 class="text-dark-purple  fw-bold">
          Can I use Frontend Mentor projects in my portfolio?

        </h4>
        <img src="./assets/images/icon-plus.svg" class="plus" alt="plus" />
        <img src="./assets/images/icon-minus.svg" class="minus hidden" alt="minu" />
      </div>

      <p class="para hidden">
        Yes, you can use projects completed on Frontend Mentor in your portfolio. It's an excellent
        way to showcase your skills to potential employers!

      </p>
      <hr>

      <div class="question">

        <h4 class="text-dark-purple  fw-bold">
          How can I get help if I'm stuck on a Frontend Mentor challenge?

        </h4>
        <img src="./assets/images/icon-plus.svg" class="plus" alt="plus" />
        <img src="./assets/images/icon-minus.svg" class="minus hidden" alt="minu" />
      </div>

      <p class="para hidden">
        The best place to get help is inside Frontend Mentor's Discord community. There's a help
        channel where you can ask questions and seek support from other community members.


      </p>
      <hr>

    </div>
  </main>
  <script src="./script.js"></script>
  <footer class="attribution">
    Challenge by <a href="https://www.frontendmentor.io?ref=challenge" target="_blank">Frontend Mentor</a>.
    Coded by <a href="#">Sayyed Aaman</a>.
  </footer>
</body>

</html>

================================================
FILE: script.js
================================================
const plus = document.querySelectorAll('.plus');
const minus = document.querySelectorAll('.minus');
const hidden = document.querySelectorAll('.hidden');
const para = document.querySelectorAll('.para');


for(let i=0; i< plus.length; i++){
    plus[i].addEventListener('click',function(){
        plus[i].classList.toggle('hidden');
        minus[i].classList.toggle('hidden');
        para[i].classList.toggle('hidden');

    })
}

for(let i=0; i< minus.length; i++){
    minus[i].addEventListener('click',function(){
        minus[i].classList.toggle('hidden');
        plus[i].classList.toggle('hidden');
        para[i].classList.toggle('hidden');
        
    })
}

================================================
FILE: style-guide.md
================================================
# Front-end Style Guide

## Layout

The designs were created to the following widths:

- Mobile: 375px
- Desktop: 1440px

> 💡 These are just the design sizes. Ensure content is responsive and meets WCAG requirements by testing the full range of screen sizes from 320px to large screens.

## Colors

- White: hsl(0, 0%, 100%)
- Light pink: hsl(275, 100%, 97%)
- Grayish purple: hsl(292, 16%, 49%)
- Dark purple: hsl(292, 42%, 14%)

## Typography

### Body Copy

- Font size (paragraphs): 16px

### Font

- Family: [Work Sans](https://fonts.google.com/specimen/Work+Sans)
- Weights: 400, 600, 700

> 💎 [Upgrade to Pro](https://www.frontendmentor.io/pro?ref=style-guide) for design file access to see all design details and get hands-on experience using a professional workflow with tools like Figma.


================================================
FILE: style.css
================================================

:root{

    /* Colors  */

    --clr-white : hsl(0,0%,100%);
    --clr-light-pink : hsl(275,100%,97%);
    --clr-grayish-purple : hsl(292,16%,49%);
    --clr-dark-purple : hsl(292,42%,14%);

    /* Font-Families  */
    --ff-serif : "Work Sans", sans-serif;

    /* font Weight  */
    --fw-normal : 400;
    --fw-bold : 600 ;
    --fw-extra-bold : 700;

    /* Typography  */

    --fs-400 : 1rem;
    --fs-500 : 1.25rem;
    --fs-600 : 1.50rem;
    --fs-700 : clamp(1.75rem, 4vw, 2rem);


}

*,*::before,*::after {
    box-sizing: border-box;
    padding : 0;
    margin : 0;
}

h1,h2,h3,h4{
    padding : 0;
    margin : 0;
    line-height: 1.1;
    font-weight: var(--fw-normal);
}

html{
    font-family: var(--ff-serif);
  
}

body{
    min-height: 100vh;
    font-size : var(--fs-400);
    font-weight : var(--fw-normal);
    color : var(--clr-grayish-purple);

    background-color: var(--clr-light-pink);
    background-image: url('./assets/images/background-pattern-mobile.svg');
    background-repeat: no-repeat;
    background-position: center top;
    background-size: contain;

    display: flex;
    flex-direction: column;
    justify-content: center;
}


/* -------------------- */
/* Utility Classes */
/* -------------------- */




.bg-white {
    background-color : var(--clr-white);
}

.bg-light-pink {
    background-color : var(--clr-light-pink);
}
.bg-grayish-purple {
    background-color : var(--clr-grayish-purple);
}
.bg-dark-purple {
    background-color : var(--clr-dark-purple);
}



.text-white {
    color : var(--clr-white);
}

.text-light-pink {
    color : var(--clr-light-pink);
}
.text-grayish-purple {
    color : var(--clr-grayish-purple);
}
.text-dark-purple {
    color : var(--clr-dark-purple);
}


.ff-serif{
    font-family: var(--ff-serif);
}


.fw-normal{
    font-weight : var(--fw-normal);
}

.fw-bold{
    font-weight : var(--fw-bold);
}
.fw-extra-bold{
    font-weight : var(--fw-extra-bold);
}


.fs-400{
    font-size : var(--fs-400);
}

.fs-500{
    font-size : var(--fs-500);
}

.fs-600{
    font-size : var(--fs-600);
}

.fs-700{
    font-size : var(--fs-700);
}





.flex{
    display: flex;
    --gap : 1rem;
    gap : var(--gap);

}
.grid{
    display: grid;
}

.d-block{
    display: block;
}


.hidden{
    display: none;
}

/* -------------------- */
/* General Classes      */
/* -------------------- */
.wrapper{
    height: 100vh;
    display: grid;
    place-content: center;
    margin-inline: 2rem;
}

/* -------------------- */
/* Components            */
/* -------------------- */

.faq-card{
    --br : .9375rem;
    padding : 1.5rem;
    border-radius: var(--br);
    max-width: 37.5rem;
}
.faq-card p {
    margin-bottom: 1rem;
}
.heading{
    margin-bottom: 1rem;
    align-items: center;
}

.heading >  img{
    display: block;
    width: 40px;
    
}
.question{
    display: flex;
    gap : var(--gap, 2rem);
    justify-content: space-between;
    padding-block : 1rem;
}

.plus,.minus{
    cursor: pointer;
}

.question:hover > h4, .question:focus > h4{
    color : rgb(237, 0, 237) !important;
    cursor: pointer;
   
}


/* -------------------- */
/* Responsive           */
/* -------------------- */
@media only screen and (min-width:35rem){

    body{
        background-image: url('./assets/images/background-pattern-desktop.svg');
    }
}