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

Pure CSS Flex-box

SemptechVzla•150
@SemptechVzla
A solution to the Product preview card 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?

i am learning yet, no proud about anything. Nex time, i will add variables in mine css to practice them

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

the challenge was to place an image in the button, i did overcome it by watching videos from youtube about how to do it!.

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

i want to learn how to use varibles at css

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Pedro Eustáquio•220
    @PedroEustaq
    Posted 11 months ago

    Hello! You want to know how to change variables in CSS trought JS? if it is, just:

    var page = document.querySelector('.Container');
    page.style.width = '200px';
    page.style.backgroundColor = 'green';
    

    and keep going...

    or if it is, example, 100px...100vh / 100vw.... 100% | I recommend you watch some youtube videos about it, but yet i haven't found one to show you :(

    Basically:

    1. px = is for amount of pixels

    2. % = is relatable as the size of the page (if you make a container with height: 90% it cover 90% relatable to your page, ex: your page is heigth 3000px then the height of the container will be 90% of 3000px.)

    3. vh = is only for height, and its the same thing as % but it will depend on your screen (if you put height: 80vh, it will cover 80% of the screen the user is on.)

    4. vw = is only for width and its the same but with width.

    5. Try making and HTML5 changing de body with these ones, so you can see the diference!

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 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