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

NX, Next.js, Typescript, GraphCMS, Nest.js, and Styled Components

graphql, next, styled-components, typescript, react
Simon Davis•505
@Skidragon
A solution to the Audiophile e-commerce website challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This is a fullstack site which all the content comes from a CMS which there is a reverse proxy server talking between the client and CMS to add extra security for example DOS attack. I used react-hook-form to build the checkout and the payment endpoint is not connected to stripe or paypal but it does double check prices between the database product prices and what the client sent by checking item ids. I call this MVP since its a usable site but its not styled perfectly or has all the content because its busy work and plan to work on a more challenging project. Will work on it more little by little.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Riha Shehzadi•80
    @codingwithriha
    Posted about 3 years ago

    Hello SIMON DAVIS! I took some time to look at your solution. there are some tips for better your code 1.add a link element with an attribute must have a rel attribute that contains the value preload. 2.all img are broken maybe the url is incorrect. overall you have done great.

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