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

fem landing page html css and js

Sagor Mohammed Yousuf•230
@sagormohammedyousuf
A solution to the Manage landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Pranjali Sargar•520
    @Psargar616
    Posted over 1 year ago

    Hi @sagormohammedyousuf, you have done excellent job on the challenge.

    I hope you're doing well! I wanted to drop you a quick message regarding your Frontend Mentor solution. First off, great job on completing the challenge! I can see the effort you put into it.

    Here's what I liked about your work:

    Design Implementation: Your implementation of the design is commendable. The overall layout and visual aesthetics align well with the provided design.

    Responsiveness: Your solution is responsive, which is fantastic. It ensures a seamless experience across different devices.

    Code Structure: Your code is well-organized, making it easy to follow the logic and understand the flow of your project. This is essential for collaboration and future maintenance.

    However, I also have a few suggestions for improvement:

    Code Efficiency: Consider optimizing your code for efficiency. Look for opportunities to streamline your CSS and JavaScript for faster load times.

    Comments and Documentation: Adding comments to explain your code decisions can be helpful, especially for someone reviewing your work. It provides context and aids understanding.

    I hope you find this feedback constructive. Keep up the good work, and feel free to ask if you have any questions or need further guidance.

    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