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

[NextJS, Tailwind CSS] - Order Summary Component

next, react, tailwind-css
Loretta•50
@lucky-lore
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


-------- All Frontend Mentor Challenges --------

Hello there! 👋

I'm a professional React developer working through the challenges from Frontend Mentor. 3 years ago doing the Guru projects landed me a job and I am coming back to finish all the challenges as a hobby. I'm methodically progressing through these challenges, starting with the free versions, and gradually working up to the premium ones.

-------- My Journey 🚀 --------

  • Current Phase: Completing all Newbie Free projects.
  • End of Current Phase: Code revision and optimization (E.g. Componentization/modularization)
  • Next Steps: Moving onto Junior, Intermediate, Advanced, and finally the Guru levels.
  • Premium Challenges: After completing the free versions, I'll tackle the premium challenges.
  • End Phase: Code revision and optimization (E.g. Adding service workers, web workers, optimizing accessibility, refactoring projects to support PWAs)

-------- Repository Overview 📚 --------

The repository is a Lenra Monorepo. Each project in /packages is hosted on Vercel. The live versions you can find in the README.md

  • Project Status: In Progress 🚧
  • Number of Challenges Completed: 5

🔗 Repository Link

-------- Project Structure --------

Each project is housed in its own folder in the packages directory and contains all the necessary files. Feel free to explore.

-------- Stack That I will be using for the projects --------

  • NextJS
  • Zustand
  • React Query
  • Tailwind CSS

-------- Future Plans 🌟--------

  • Code Optimization: Once all Newbie Free challenges are completed, I plan to revisit each project. I'll focus on optimizing the code, implementing Progressive Web Apps (PWA), enhancing accessibility, and general code clean-up.
  • Timeframe: Due to my busy schedule, I'm aiming to complete these challenges ASAP. Your understanding and support are much appreciated!

-------- Connect with Me and Support My Journey! 🤝--------

  • Star the Repo: If you find my work valuable or interesting, please give it a star! ⭐
  • Follow Me on GitHub: Stay updated with my progress and latest projects by following me here.

Your support and feedback are crucial to my growth as a developer. Let's connect and embark on this coding journey together!

Thank you for stopping by! 🙏

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Jax Teller•670
    @piushbhandari
    Posted over 1 year ago
    • for that wavy pattern, i would suggest that instead of having background-repeat: no-repeat, change it to background-repeat: repeat-x;. this is because the pattern looks awkward when you scale your component to screen widths larger than 1440px

    • the proceed to payment and cancel order need to be converted to more semantic elements i.e <button> or <a> because presumably, depending on the need of this on a web page, these are going to be doing something

    • for all interactive elements, make sure to have hover/focus states to indicate that these can be interacted with

    • i would suggest adding side paddings on your main/body element so that your component isn't hugging the edges.

    • add an alt attribute to your image

    Marked as helpful
  • Serah Nderi•450
    @MundiaNderi
    Posted over 1 year ago

    Happy to learn that the Guru projects landed you a job in the past. Really inspiring to newbies like me. I just started learning React and I hope to start practicing with Frontend Mentor.

    Cheers!

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub