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

Clipboard Landing Page - SASS, Bootstrap..

accessibility, bootstrap, sass/scss
Lucas Exequiel•200
@arrejoria
A solution to the Clipboard landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi frontend mentor community, lets matear 🧉 😁

This is my solution for the Clipboard Landing Page

Solution Repo

I'm very happy doing this kind of project to improve my performance skills.

  • I used SASS to improve my skills in CSS and minified the file to get better performance. 🚀
  • I got 88% of Performance in PageSpeed Insights.
  • Used Semantic HTML5 markup to get better compatibility and accesibility for users.

This project is responsive for desktop, tablets and mobile using bootstrap and custom media queries.

Comment: First of all thank you! Clipboard landing page is a big challenge where to start

Second, this project was not supposed to be this long. I was working this solution in laravel to practice more with blade and libraries like sass, bootstrap etc. in that environment.

When I finished the solution, I got really frustrated trying to deploy the project with Railway (sad Heroku moment), so I decide to do it statically.

PS.If anyone knows a platform where to implement a project like laravel, please let me know...

For me this was a great challenge where I got a better understanding of CSS. I think the best part of this project was coming up with a better vision for designing each section and how each one works on top of the other.

I learned a lot about how to better structure my HTML to get a head start on CSS and better responsive results.

For now I leave this solution here and I would like to do more projects in Laravel, I also want to do some applications in React or focus on a new technology... but all in due time

Thanks for reading and seeing my solution. Any feedback or advice is welcomed!

Lucas,

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 Lucas Exequiel'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.