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

responsive site using Vue.js and Tailwind

vue, tailwind-css
Nelly•30
@NellyBise
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


What are you most proud of, and what would you do differently next time?

I'm proud of the responsive header. Next time, I think I will define fonts in the CSS index at the beginning of the project. I started using Tailwind config, but it's not the best way for responsive text.

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

My biggest difficulty was using Vue, as this is my first complete project with it. On the other hand, this project allowed me to improve my CSS knowledge. I discovered some properties that I had never had the occasion to use before.

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

I'm not sure if my management of the "selected destination" is the best ; perhaps it would have been better to handle it through the URL. What do you think ?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Varun Tyagi•150
    @vitviki
    Posted 11 months ago

    The website looks great, but the moon image under the destination tab is not showing up.

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