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

Multi-page - Sass - Node.Js (Express) - Ejs

Antoine•220
@Antoine-Flo
A solution to the Arch Studio multi-page website challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


My first mutli-page website 🙌 there is some details I'm not 100% satisfied with but, next time I'll do it differently. The screenshot looks empty because of the on-scroll animations (Aos library, next time GSAP 👌). Any feedback is welcome.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Adarsh Pratap•5,515
    @adarshcodes
    Posted over 4 years ago

    Hi! @Antoine-Flo, You did amazing work on this challenge.

    • I love the scroll animation you added
    • Your solution is spot on, great work👏
    • A small issue I noticed while checking the responsiveness it seems your site leaves extra blank space to the right side and when it comes to the mobile view, the navigation slider started showing up. (Idk, if it's my browser or a real issue).
    • You can also solve the HTML and Accessibility issues. Nice work! Happy Coding : )
  • Coder•270
    @qb-rivkyb
    Posted over 4 years ago

    Hey! I just looked at your solution after I did the same one. I noticed some hover and active states were missing. You can have a look at mine 😉.

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

    Hello, Antoine! 👋

    Nice to see you complete another challenge! 😀 Great job on this one! 🙌

    Congratulations on completing your first multi-page website (this was quite a project)! 🎉

    Like, adarshcodes mentoined, there seems to be some extra space to the right of the content of the page on most of the pages, producing a horizontal scroll bar along the bottom of the screen. Also, I think it would be nice if the projects on the portfolio page were links (even if they don't go anywhere just yet). 😉

    Other than that, everything looks great and responds well! 👍

    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

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