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

Responsive Landing page built with Vue

typescript, vue
Sebastian Heitmann•150
@DonHeidi
A solution to the Meet landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I really enjoyed this challenge but it took me longer than expexted due to Vue. I wanted to try out Vue and it was a nice experience. Vue really encouraged me to structure my code in a cleaner way than with Vanilla HTML/CSS but it took some time to bring up a structure.

I also tried to use counter-increment for the but was not able to get it up :/ Is counter-increment only working on siblings?

I am also not sure about the background on the footer. I used pseudo elements to create the effect but I am not sure if this is the way to go.

Besides, feel free to give me some feedback

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Elaine•11,360
    @elaineleung
    Posted almost 3 years ago

    Hi Don, this looks really good! 🙂 I've been looking to get into Vue and Svelte too, so it's nice to see people trying out new frameworks in their projects.

    About the footer background, I wonder whether you had tried using the image as a background first, and if you did, what kind of issues did you run into that made you use a pseudo element instead? I would think using it as the footer background would give you more control in positioning, and plus this is on a container element that spans across the page. I had similar issues when working on a recent challenge, and I went back and forth between using the SVGs as a background and as a pseudo element; in the end I had almost all of them as pseudo elements because resizing of the SVGs was needed.

    In any case, this was great work, and looking forward to more Vue projects 😊

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

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