Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Responsive Clipboard landing page using CSS Grid and Flexbox

stautuan•160
@stautuan
A solution to the Clipboard 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?

This is my first landing page. What I would do differently next time is I would start with a plan and set up as this took longer to complete than I expected. For instance, implementing the footer section was particularly challenging as there were many ways to tackle it, and especially deciding on breakpoints and adjustments.

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

Figuring out how to implement the hover color effect on the social links took some creative problem solving. Through this process, I learned about the filter property and used a filter generator to achieve the desired effect.

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

Structure and layout of the sections. Feedback is welcome 😄

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Bernardo Poggioni•6,770
    @R3ygoski
    Posted about 1 year ago

    Hello again @stautuan, and congratulations on the project, it turned out wonderfully perfect, truly, my sincere congratulations.

    A small observation: between 595px and 1120px, the titles in the "snippets" section end up aligning to the left, which is slightly awkward, but this is just a minor detail.

    Regarding your code organization, it is very good, I would say almost impeccable. If you want to improve it even further, you could use Sass and distribute its sections into partial Sass files, so you can organize it better. The idea of using "utils" was very good, and a tip about "utils", in sass you can use mixins for this. Sass - Mixins

    Your HTML organization is very good, the comments help to understand where we are in each section, which is great for maintenance, congratulations.

    I just wanted to give you a tip related to your semantic HTML, it is very good, but there are some parts that can be improved, they are here:

    • In the Hero section, your <section class="hero-section text-center"> can be changed to <header>, because it serves as an introductory section.
    • Below the Download section, your <section class="footer"> can be changed to <footer>, because it is the end of your content, so it is more appropriate to use it.

    Again, congratulations on your project, it turned out very well, really, I really liked it as you could tell 😅. If you have any questions, you know where to ask.

    Marked as helpful

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