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

Clipboard Landing page

Neel Mishra•240
@Neel-07
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?

I'm most proud of the clean and visually appealing design of the Clipboard landing page. The layout and styling came together seamlessly, effectively highlighting the features and functionality of the page.

Moving forward, I would concentrate more on ensuring the landing page is fully responsive. Although it currently looks impressive on larger screens, I acknowledge the need for improvement to optimize its display on smaller devices. Furthermore, I aim to incorporate additional interactive elements to enhance user engagement with the page.

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

The main challenge I faced was changing the fill color of the SVG of the social icons. Through this, I learned a great deal about SVGs.

One of the main challenges I encountered was making the Clipboard landing page fully responsive to cater to different screen sizes. It required experimentation and adjustments to strike a balance between responsiveness and maintaining the page's aesthetic appeal.

To tackle this challenge, I employed media queries and flexible layout techniques in CSS to ensure the landing page adapts seamlessly to varying screen dimensions. Rigorous testing on diverse devices was also crucial to verify the page's consistent display across different platforms.

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

I would greatly appreciate feedback on the responsiveness of the Clipboard landing page, particularly on smaller screens. Additionally, suggestions on enhancing user interaction and engagement within the landing page would be highly valuable. Thank you for your insightful input!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Neel Mishra'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 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.