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

Audiophile solution using Svelte(Kit), DaisyUI, Superforms, & Valibot

svelte, tailwind-css, typescript
Barry•170
@bonclairvoyante
A solution to the Audiophile e-commerce website 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 most proud of my ability to complete this challenge. I also think that my skills have improved as I started with the newbie challenge and proceeded through the ranks to a guru-level challenge.

I am also proud of the fact that while doing it, I got an idea to start an online audiophile shop as I consider myself an audiophile. It is one of the things that drew me to this challenge.

Next time, I would probably not try not to use tailwind css. Svelte scopes CSS styles to the component, thereby reducing the need for scoped styles that Tailwind offers. I would also plan my time and strictly adhere to it.

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

The main challenge I faced was in styling. But Daisy UI helped with that.

Handling form data was also a challenge but Sveltekit's Form Action simplified it.

Sveltekit Superforms and Valibot (A TypeScript validation schema library) helped me validate formData on the client and server.

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

None specifically. Any help with accessibility would be appreciated as I realised that I struggle a lot with it.

Note: I made some tweaks to the designs as I plan to build it out as a fullstack eCommerce website for my use in real life.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Barry's solution.

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.