Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Interactive pricing component using React

react
Joseph Fola•590
@Fola-Joe
A solution to the Interactive pricing component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I had a little tough time with this project since I am new to React, but it was a nice project to tackle. What could I have done better? 🤔

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Matthias Nilsson•980
    @RalfiSlask
    Posted over 1 year ago

    Hello nice work!

    I have a few suggestions and tips.

    HTML

    Change semantics of your elements so instead of <div className="footer></div> use <footer></footer>. Use only section if it is necessary.

    Javascript

    Maybe use ternary operators for simple if statements, it is easier to read as it only takes up one line.

    instead of:

    if (isDiscounted) {
         newPrice = newPrice * 0.75;
     }
    

    use:

    newPrice = isDiscounted ? newPrice * 0.75 : newPrice

    React

    Make use of react by creating components that can be reused if necessary so you dont have to repeat code. The most obvious example is in the footer, where you have three items that could be used in a single component.

    If you instead create a component like this and make use of the text as a prop:

    const FooterFeatureItem = ( {text} ) => {
      return (
        <section className="check-section">
            <img src="./icon-check.svg" alt="" />
            <h3>{text}</h3>
        </section>
      )
    }
    
    export default FooterFeatureItem
    

    When you then have this component you can either use it by just writing it like this:

    <section className="bottom-section">
           <FooterFeatureItem text="Unlimited websites"/>
           <FooterFeatureItem text="100% data ownership"/>
           <FooterFeatureItem text="Email reports"/>
     </section>
    
    

    But a better and more dynamic way is by first creating an array of objects:

    
    const footerFeaturesList = [
            {id: 1, text: "Unlimited websites"}, 
            {id: 2, text: "100% data ownership"}, 
            {id: 3, text: "Email reports"}
    ]
    
    

    And then use the map method over this list to create the components:

     <section className="bottom-section">
         {footerFeaturesList.map(feature => <FooterFeatureItem key={feature.id} 
         text{feature.text}/>)}
     </section>
    
    Marked as helpful

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