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

My Team Page

Web Frog•1,840
@MasterDev333
A solution to the myteam multi-page website challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I tried to make everything pixel-perfect to the design. Will upload the about and contact us page soon. Any feedback will be appreciated.

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, there! 👋

    I hope that you are doing great. 🙂

    There is only the home page. The other two pages are not built yet. I recommend only submitting the finished project.

    Here are some suggestions for improvements.

    • The aria-label for the hamburger menu should not be hyphenated.
    • For the hamburger menu icon, the icon has been provided by Frontend Mentor. Are you creating your own icon so that you can animate it?
    • Avoid using br elements for presentational purposes. Read the "Accessibility concerns" part of the MDN documentation for br.
    • For images that are used only as decorations (they do not give users any information and serve only an aesthetic purpose), the alt tag should still exist but should be left empty: alt="". This will tell the screen reader to simply skip over the image.
    • Why don't just use the img element? (<div class="testimonial-item__avatar" style="background-image: url('images/avatar-kady.jpg');"></div>) It's less code to write if you just use the img element (with empty alt if you think it's a decorative image).
    • Never remove CSS outlines.
    • I highly recommend writing the styling using the mobile-first approach. It often leads to shorter and better performance code. Also, mobile users won't be required to process all of the desktop styles.
    • 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?

    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! 😄

  • Nikola•120
    @nikola719
    Posted over 4 years ago

    It looks great and it is combined well with animation effect in a harmonious way. The one thing to be distinguished from the others is flexible and fully responsive on every breakpoints. Highly recommended!

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

    Hey, great work, Front-end Master! 👋

    Everything looks nice and responds well! I like the sticky desktop navigation and the transition of the mobile navigation! 👍

    I only suggest adding a hover state to the social media icons in the footer of the page (I think that would be a nice touch). 😉

    Keep coding (and happy coding, too)! 😁

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

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