Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 2 years ago

Next.js 13 with API, Typescript, SCSS, Fluid design (all rem, clamp)

next, react, typescript, zustand, sass/scss
Vlad•240
@vladmee
A solution to the Space tourism multi-page website challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


My first Next.js project. I tried its Server-Side Rendering (SSR) features, exploring how Server and Client components interact. I used Next.js's built-in router for easy page creation and serverless functions to serve data via an API.

I also gave Zustand a go. It's a lightweight state management tool, and I was pretty impressed by how efficiently it worked and how little setup it needed to keep the data consistent across pages.

When it came to styling, I used SCSS for its file structure, but found that CSS custom properties could do the job too. I'm still on the lookout for the perfect fit.

The most interesting part of this project was definitely the styling. I learned a lot about modern CSS concepts. I even ended up rewriting most of my CSS halfway through, switching from pixels to rem and using clamp for a fluid design approach. Check this commit if you're interested to see my process.

This project was a real game-changer for me. I'd spent the last 3 years in a management role, shaping the architecture of big projects rather than doing the coding myself. Now, I'm keen to brush up my skills to meet current web development standards, making the most of the latest tech like Next.js, Zustand, and modern CSS.

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 Vlad'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.