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

js,css and html

Faisal Omar•50
@faom002
A solution to the Newsletter sign-up form with success message challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Although the project is not fully completed, all the functionalities have been properly set up. However, I acknowledge that there are areas for improvement, such as the lack of mobile design implementation using media queries. Additionally, the desktop design could be enhanced further.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Grace•32,130
    @grace-snow
    Posted about 2 years ago

    You need to be working mobile first really. And not submitting at all if the mobile styling is not done.

    This still needs quite a lot of work. Have you had feedback on earlier challenges?

    Here are some fundamentals to focus your learning on

    • all content should be within landmarks (main, footer etc)
    • don't use large margins to try and create a layout. To center a component on the screen use flex or grid properties along with min-height 100vh
    • instead of setting a % width on a component, use max width only (in rem)
    • always use a modern css reset at the start of the styles. Andy Bell has a good one you can look up and use
    • border radius should never be in %. Use a fixed value for that
    • font size must never ever be in px
    • use small padding values for the button. This could be a good candidate for the em unit
    • you are using a very unusual approach for class names. Consider changing to hyphen-separated strings instead of pascal/camel case
    • alt on images is important content - if the images are meaningful they must have proper descriptions of what they look like
    • consider using the picture element for responsive images
    • this is missing a form and label for the input
    • error message containing elements should be present in the DOM at all times, have a unique ID, and be linked to the input with aria-desciribedby
    • Try to Indent your code consistently so it's easier to read and easier to spot bugs
    • follow me on LinkedIn is not a heading for other content. It's also skipping a heading level but headings must always be in the right order in html. I recommend you move this to a paragraph in the footer (attribution)
    • once you've fixed the html, this needs to be listening for a form submit on the first panel, not a button click

    Good luck

    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

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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub