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

maker-prelaunch-landing-page with vanilla JS animated with AOS

SukiyakiFiend•115
@josuke0227
A solution to the Maker pre-launch landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Fist implementation of stying with BEM. I appreciate your advice about the usage of BEM. Any other advice is also appreciated!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted about 4 years ago

    Hello there, Josuke! 👋

    Good work on this challenge! 👍 The on-scroll animations in your solution are very nice! 😀

    I'd like to suggest,

    • Adding a max-width to a few of the sections of the page so that they maintain their size when the screen width grows larger (and don't start to seem stretched or anything).
    • Perhaps making the heading of the hero section of the page a tad bit bigger in the tablet/mobile layout (it seems a little small).

    Keep coding (and happy coding, too)! 😁

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted about 4 years ago

    Yours is really good and those observers , are those observers? I don't really use react but I use other api for that one. For the BEM, well we use BEM to be reusable right, but the thing is that, we just don't use them because they are easy to use since we can just declare one block then just append their child names right. We use them so that we avoid multiple stylings. We should first look at the layout then take note of different sections and look for the similarities of it, that similarity will be our block in BEM naming. Then we'll just add the states, in the manner of -- syntax. One best example of this is using a block of flexbox, since you can just manipulate any layout just using that and just adding different states like flex--column which will be flex-direction something like that. Well it just takes time to properly grasp BEM principles but that is the gist of it. Really, your work is good^

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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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