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

Tech Book Club – Responsive landing page built with Vue

vue, vite
P
marijazlatkova•100
@marijazlatkova
A solution to the Tech book club landing page 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 I built the whole project from scratch and that everything works smoothly. This was my first time using Vue, so I focused on keeping it clean and functional with plain CSS.

If I did it again, I’d definitely go with SCSS instead. I’d set up mixins, variables, and global styles to make things easier to manage and avoid repeating code.

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

Getting comfortable with Vue’s syntax and component logic took some time since it was all new to me.

I overcame it by keeping things simple, reading the docs when needed, and figuring things out step by step. Nothing really blocked me. It was just about getting used to how Vue works.

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

I’d like feedback on the project in general. Since it’s my first time using Vue, I’m open to any suggestions on how to improve the structure, logic, or even the styling.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Harsh Kumar•5,160
    @thisisharsh7
    Posted 16 days ago

    Great work on completing the challenge! It’s impressive that you built everything from scratch and kept the structure clean while learning a new framework. The UI is responsive and visually consistent, and you’ve organized your template and script sections well.

    Some suggestion:

    1. CSS Structure: Extract styles into separate .scss or .css files per component. This improves maintainability and allows features like global styles, mixins, and variables when you scale.
    2. Breakpoints: Currently, breakpoints are at 768px and 1440px. Consider refining them to better support mid-range laptop screens (~1024px) and tablets (~600–800px). Tailoring views for tablet and laptop users ensures a smoother UX.
    3. Semantic Tags: Consider using semantic HTML tags like <footer>, <section>, or <nav> where applicable to improve accessibility.
    4. File Structure: Group assets and components logically. For instance, place related assets near the Vue component to reduce path complexity.

    Overall a fantastic start with Vue - happy coding!

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