Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Multi-Page-Website-React-Bootstrap

react, bootstrap
Teodor Jenkler•4,040
@TedJenkler
A solution to the Designo multi-page website challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I did not really showcase any new skills here but rather showed my skill to be able to finish a project and design a site with Figma as a template.

Feedback is welcome

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ahmed Faisal•5,095
    @afrussel
    Posted over 1 year ago

    Hello, @TedJenkler

    Overall, your effort is commendable. However, during the review, I observed several areas that require attention to enhance the overall quality of your work.

    1. Coding Errors:

    • While examining the code, I identified a few instances of coding errors that need rectification to ensure optimal functionality and compliance with best practices.

    2. Missing Font Family:

    • The absence of a defined font family might impact the visual consistency and readability across your web content. It's crucial to specify a suitable font stack to maintain a cohesive and aesthetically pleasing design.

    3. Image Hover Effect:

    • Incorporating a hover effect on images can significantly enrich user interaction and engagement. Implementing this enhancement can elevate the visual appeal and interactivity of your website, creating a more immersive user experience.

    4. Footer Height Adjustment:

    • Optimizing the footer height can contribute to a more balanced layout and overall aesthetics. Lowering the footer height might refine the website's visual structure, providing a more cohesive and aesthetically pleasing design.

    Addressing these aspects will not only resolve the noted issues but also contribute to an improved user experience, design consistency, and code quality across your web project.

    I encourage you to consider these points as opportunities to refine and elevate the quality of your work further.

    Marked as helpful
  • Ehtesham ali•330
    @Ehteshamali-889
    Posted over 1 year ago

    Small fixes needed: Images overlay missing header links styling missing footer styling not matching with design background image missing for section passionate resourceful and friendly

    but overall great work. Keep it up.

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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