Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 11 months ago

pagina con ayuda de display grid css

sankiss55•200
@sankiss55
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


What are you most proud of, and what would you do differently next time?

saber muy bien como manejar el estilo de display: grid en css y me gusto como lo diseñe sin dificultad

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

creo que ninguno

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

en todo un poco estaria bien me ayudaria mucho

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • matt2282•310
    @matt2282
    Posted 11 months ago

    You did the email validation and switching of the pages correctly and the general layout of the page is good, but it does have a lot of issues.

    The email input has a cursor pointer when it should be a text selection pointer(this is default I believe). Desktop: -background color should be hsl(235, 18%, 26%)

    • The padding on the right of the image gets messed up when you switch from mobile back to desktop.
    • Missing a space on "Stay updated!"
    • I'd recommend setting a fixed height/width for the outside container because things get weird when the container gets resized.
    • Also recommend keep the image at a fixed size. -Could use a bit more padding especially on the left.

    Mobile:

    • The original design has the image at the very top of the page while your solution has it centered and the desktop background visible.

    Success Page:

    • Misspelled "subscribing!"
    • The email should be the same as the email you entered in the box on the first page not ash@loremcompany.com every time.
    • You forgot to make a mobile friendly version. It looks not right on mobile.

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