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

Build by SCSS, BEM, flex-box, grid-box, vanilla JavaScript and jQuery.

PeaNu•90
@jubeatt
A solution to the Agency landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I've written all my processes in the README, you can find many details from there.

It may need to take some time to read, but I think it's worth it. (Because it really takes me so much time to write😂)

If you think there is something that can be improved or any suggestions, please feel free to let me know.😃

It's a long way to go on the front-end, but I will keep going, and I hope you like this work, thanks!😊

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Matt Studdert•13,611
    @mattstuddert
    Posted almost 4 years ago

    Now that's how to write a README.md file! 🤩 Haha. Amazing work on this project (and the README), Jim!

    You've done a great job, and your solution matches the design nicely. Here are some pointers that will hopefully help you:

    • I'd recommend reading the accessibility report and try resolving those errors/warnings. Once you've updated your code, you can generate a new report using the button at the top of the report page.
    • The "We are creatives" text should really be the h1 on this page as it's the main heading. Also, you've uppercased the content in the HTML itself. Try to avoid doing that as some screen reader software will read this content letter-by-letter, which makes that content inaccessible to screen reader users. Instead, write it normally in your HTML and then use text-transform: uppercase; in your CSS to visually uppercase the text to match the design. This happens in a few other places in the HTML, so I'd recommend doing the same for the rest of the content.
    • It's great to see you using a button to trigger the mobile navigation. If you want to take it further and make it fully accessible, you can add attributes like aria-expanded to help screen reader users. Here's a great article about building accessible mobile navigations to help get you started.

    I hope those pointers help. Let me know if you have any questions!

    Marked as helpful
  • Ngoc Anh Vu-Martell•125
    @anh-vumartell
    Posted almost 4 years ago

    Hello @julbeatt! Your solution looks awesome and thanks for a great README file. I've learned a lot from your reflection notes.

    I'm a beginner in front-end development so I'm glad to learn from fellow front-end developers. I'd love to know which tool do you use to create the Structural drawing in your README file. Thanks and happy coding!

    Marked as helpful
  • Michal•665
    @mbart13
    Posted almost 4 years ago

    hey, I saw your solution in Matt's newsletter

    thought maybe you could be interested to know that aria-controls are not really recommended anymore https://heydonworks.com/article/aria-controls-is-poop/

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

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

Oops! 😬

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

Log in with GitHub