Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 21 days ago

Audiophile website using Headless Wordpress

pinia, vite, vue, wordpress, sass/scss
P
Andrey•4,480
@dar-ju
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 saw this task, where it is proposed to use a headless CMS, especially since I had already worked with Wordpress before, but I learned about headless for the first time. I decided to give it a try. In my opinion, the main disadvantage of Wordpress is that it is very difficult to make a rocket out of it, it is unrealistic to bring Page Speed ​​Insights close to 100. So it turns out that if you take the backend and admin panel of Wordpress, and write your own front, then this is really cool. The site flies fast! At the same time, it is possible to change / add content and products without any problems.

If you are interested, you can see a demo of what the admin panel looks like from the inside

https://audiophile.darju.ru/wp-login.php

login: demoUser

password: 123

I can provide full access upon request.

At the same time, the load on the hosting and the database during the development process is minimal. In short, I recommend this approach.

Orders are actually sent and displayed in the admin panel, you can send them to email quite quickly. For full operation, this store only lacks payment acceptance and protection from bots. I specifically reduced the number of required fields so that it would be easier to check.

P.S. Only during my work I learned about Strapi, I want to try it next.

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

In terms of layout, the main difficulty was how to synchronize the sizes of the loaded blocks with the skeleton blocks and control their changes when the screen width changes. At the same time, it is necessary to achieve a minimum displacement of these blocks, otherwise Page Speed ​​greatly reduces the indicators. This took a lot of time.

In general, the project is really complex, my code time shows 71 hours and about 10 hours to configure WordPress.

Also, Github pages categorically refused to receive data from a domain without SSL, and on the test domain I could not make HTTPS, I had to register a new domain ((

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

Maybe there are some automatic means of adjusting skeletons? I'm really tired of doing this.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Ivo•170
    @ijerkov
    Posted 21 days ago

    Awesome work Andrey! I never tried headless WordPress before and I was wondering how would you process orders? Using WooCommerce API?

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