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

Mobile-first solution using HTML, SCSS (w/ BEM) and Vanilla JS.

Simon Hernandez•615
@simonhernandez
A solution to the myteam multi-page website challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi Guys, hope you are doing great!

I am very excited to submit this solution, as I got to practice my SCSS skills which I've been trying to improve by making cleaner and more granular partials.

I also practiced and studied a bit of DOM manipulation in order to animate the directors profile cards. (It was really fun :)! )

Lastly, I added some On Scroll Animations, using the AOS Library.

Hope you guys like it! I also would really appreciate any feedback on my code or on the overall project. (Thanks in advance :) )

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vanza Setia•27,715
    @vanzasetia
    Posted over 2 years ago

    Hi, Simon! 👋

    Congratulations on finishing this challenge! 🎉 I hope that you are still online at Frontend Mentor.

    It's great that there's a scrolling animation and in my opinion, it would be better if the users that don't want to see animations can turn off the scrolling animation. You can use prefers-reduced-motion media query to turn off the animation.

    I have some feedback on this solution.

    • Alternative text shouldn't contain any words that are related to the word "image" (e.g. logo).
    • Any interactive elements such as buttons should have an accessible name or label. Otherwise, the screen readers don't know how to pronounce it.
    • Avoid using br elements for presentational purposes. Read the "Accessibility concerns" part of the MDN documentation for br.
    • Wrap the quoted content with p. blockquote element’s content is a quote, not a chunks of characters. Reference: hail2u/html-best-practices #use-appropriate-element-in-blockquote-element
    • Use the em unit for media queries. It adapts when the users change their font size setting. Here are some references.
      • @media - CSS: Cascading Style Sheets | MDN #accessibility_concerns
      • PX, EM or REM Media Queries?
    • Never set font-size on the html element. It will overwrite the user's browser's font size setting.
    • input elements must have a label. I recommend using aria-label to give each of the input an accessible name.

    I have three recommended videos. The first one tells how hard HTML is (HTML is not easy). The other two talk about modern CSS techniques and approaches.

    • Manuel Matuzović - Lost in Translation - YouTube
    • Andy Bell – Be the browser’s mentor, not its micromanager - YouTube
    • Stephanie Eeckles - Scaling CSS Layout Beyond Pixels - YouTube

    I hope this helps! Happy coding!

    Marked as helpful
  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted over 4 years ago

    Hey, Simon! 👋

    You've done a great job on this challenge! Your solution looks good and those animations are amazing! I also like the transition of the "+" and "x" buttons of the director cards. 🤩

    Everything scales up/down pretty well! 👏

    I only suggest taking a look at your solution report and trying to clear up some of the errors that are there (adding a <title> tag to the inline SVGs should help clear up a few errors). 😉

    Keep coding (and happy coding, too)! 😁

    Marked as helpful
  • ahmed brhili•15
    @cyberknight4
    Posted over 4 years ago

    damn bro ur site is lit keep going

  • Itai•670
    @georit
    Posted over 4 years ago

    Great work! I love the on scroll animations. Happy coding 😊

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

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub