Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 4 years ago

Signup form with HTML/CSS/JS

Bojan•40
@Bojan227
A solution to the Intro component with sign-up form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey guys, can someone give me feedback about my code and i tried to make this responsive but i cant achieve this, so please give me any hints on how to make it better? Thank you in advance!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • talentlessDeveloper•340
    @talentlessDeveloper
    Posted almost 4 years ago

    @Bojan277 the desktop version is great! but using desktop approach first means your mobile version is going to inherit values from desktop.

    I don't know how the mobile version looks like but i believe it shouldn't be more than stacking upon each other.

    So in your media query for your mobile,

    • add padding to your container.
    • Remove the left and right margins you added to H1 and p tags.
    • text align center your code.
    • Instead of a 35vw for your right box change it to 100%.
    • Also reduce the font for your h1 tags and placeholders too.

    goodluck

    Marked as helpful
  • Fidel Lim•2,775
    @fidellim
    Posted almost 4 years ago

    Hello Bojan,

    To answer your question, you can try to add this to your media query (max-width:1000px):

    @media (max-width: 1000px)
    .right-box {
        margin-left: 20px;
        width:auto;
    }
    

    Hope it answers your question. :)

    Marked as helpful
  • Raymart Pamplona•16,040
    @pikapikamart
    Posted almost 4 years ago

    Hey, the site's link is broken? Site not found on my end:>

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.

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