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

Base Apparel coming soon page (HTML, CSS, JS)

Chee Kian Teoh•330
@teoh4770
A solution to the Base Apparel coming soon page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This is my first project that including JavaScript. I have learned JavaScript for a few months now, and I would not consider myself as moderate in JavaScript experience, so this challenge is very good to touch up with my current JavaScript skills.

This is my fourth challenge based on the post from dev community 16 front end projects with designs to help improve your coding skills. And I happy that I take this challenge, because it is indeed challenging to me. I started working on it from morning to afternoon, which took me about 5 hours to complete this challenge.

The JavaScript part was the hardest part in this case, I have to validate the email input to make sure the user fills the correct value, which touches the topic like regex and events. I found that planning the thinking process on paper is really really helpful to me, because it helps me identify which parts of my thinking process is incorrect or illogical.

Another thing I am struggling still is the naming convention for CSS. I use BEM(Block, Element, Modifier) to organize my code, however, since I am new to this methodology, I find myself hard to name the classes properly, which causes me to "ditch the BEM naming method" at midpoint because I am finding this much easier to do. However, I know with the good naming convention, it would be much easier to organize the CSS if the project is getting larger and larger. So I decide to look into the documentation for BEM again.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Chee Kian Teoh'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, 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.