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

Solution Intro component with sign-up form

tailwind-css
Stefan Bojkovski•720
@xStephx
A solution to the Intro component with sign-up form 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

  • chems eddine bourabia•150
    @chemsodev
    Posted 12 months ago

    Just try to adjust the card width a little bit to get the same result for the text in the footer(text in one line)

    Marked as helpful
  • Mcbattle•40
    @MarioBatalha
    Posted 12 months ago

    Good job, but you should consider remove the unnecessary comments. There no need the add comment for a block of instructions or a line of code if it explain for itself e.g:

    <!-- Form to subscribe--!> <form> <label>Add your email to subscribe</label> <input type="email" placeholder="Your email" /> <button type="submit">Subscribe</button> </form> Write a comment for complex block of code that it isn't auto explanatory, is a good practise and help to leave de code more readble and clean, instead of write a commento of every block of code.
  • KingX•180
    @iwedibah
    Posted 12 months ago

    Woow awesome job.. can i know more about tialwind css?

  • rahimibadov•20
    @rahimibadov
    Posted 12 months ago

    Great effort

  • Yousef Ayman•220
    @Yussif20
    Posted 12 months ago

    keep going 👏. it's already looking great and pixel perfect, you can try adding some hover effect to the button to make it look more interactive.

  • Nitin•80
    @indecisivenitin
    Posted 12 months ago

    your work is really wonderful but the preview option is not showing stylesheets properties on ur website

  • chems eddine bourabia•150
    @chemsodev
    Posted 12 months ago

    Woah good job

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

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

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

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