Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

Responsive using vanilla JS, CSS and HTML (mainly flexbox layout)

Ozan GOKDEMIR•50
@ozangokdemir
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


Hi to everyone reading my post and probably checking my creation !

For this one I had to learn a bit about Javascript. In fact, I started this challenge like 2 months ago, and I learned Javascript basics when I had free time not working.

My first mistake was to trying to handle everything with Javascript (because, you know, it seems so powerful and when you get a new tool you want to use it everywhere !). I ended editing the input fields styles and creating the elements containing error messages only by using JS, but I quickly understood it's not the best way to get this job done...

Finally, after having such a bad time for so long, I got motivated again and I could end this challenge being happy of my result :)

The only little thing that bothers me is this Try it free button... I have 2 issues I couldn't resolve on it :

  1. First, I used flexbox to center the text but I had troubles with the spacing between my emphased text and my normal text. I have an <em> inside an <a> element.
  2. Then when I worked on responsive, I noticed that using flexbox wasn't getting me a good result for 2-lines text. Maybe I should have played with flexbox-shrink property or something ? I ended up using padding to center it, but it becomes sadly ugly around 570px width...

Anyways, thanks if you took some time to read my comments, and I would fell very happy to get your comments and advices on the solution provided. :)

Peace ! Ozan

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Ozan GOKDEMIR's solution.

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, SASS, 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.