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

Photosnap---WordpressStack

accessibility, php, wordpress, lighthouse
Teodor Jenkler•4,040
@TedJenkler
A solution to the Photosnap multi-page 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'm most proud of creating a fully custom WordPress site optimized for performance, accessibility, and responsiveness—all without relying on plugins. It was rewarding to build something from the ground up, focusing on clean, efficient code.

Next time, I’d explore enhancing the Gutenberg block builder and PHP further, leveraging variables to make it even more user-friendly. This would empower future users to make small edits independently, reducing the need for ongoing maintenance. Despite limited free time, this project was a great learning experience and a lot of fun to create!

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

The biggest challenge was mastering the Gutenberg classes to customize the framework while maintaining a seamless experience for no-code users. It required a lot of trial and error to ensure the customizations didn’t interfere with the block editor’s usability. I overcame this by carefully studying the WordPress documentation, experimenting with various approaches, and testing thoroughly to strike the right balance between flexibility and functionality. This process not only solved the issue but also deepened my understanding of WordPress development.

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

I’d love feedback on the responsive design, particularly how well the layouts transition across mobile, tablet, and desktop. I aimed for pixel-perfect results and used rem units with a root size strategy to ensure smooth scaling. It would be great to hear your thoughts on the different desktop designs—do they feel cohesive and visually balanced?

Additionally, any insights on further improving accessibility or optimization would be helpful. The Lighthouse scores are already strong, but if you spot any missed opportunities for perfection, I’m all ears!

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 Teodor Jenkler'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 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.