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

HTML5, SCSS, Vanilla Js, Fluid Typography

Roc Tanweer•2,500
@RocTanweer
A solution to the Bookmark landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello folks 😀

This challenge was awesome and taught me a lot of things on the way...!

In this challenge I learned how you can apply fluid typography to width, height and font sizes to make things **fully responsive..! ** 😍 This web site is fully responsive without much use of media queries

There are a lot of things that I learned while being with this project, at the same time I believe I have missed some things and details😅 . But that's why we have each other, wouldn't you say? 🤗

Questions

  1. How can I make my Js simpler?
  2. Is there something that I missed while making HTML structure, like should have used this tag instead of that or you missed something?
  3. How can I make my sass code more scalable?

Any other feedbacks are very much welcome 😊

Let's learn together, grow together and Become the best Web developer..! 😎

Happy Coding..! 😴

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

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

    Greetings, Roc Tanweer! 👋

    It's good to see you complete another challenge! 😀 Great job on this one! 👍 Overall, your solution looks good and is responsive and it's wonderful that you learned lots of new things (I always do when completing challenges, as well)! 😊 And I like the animation of the mobile menu icon and the custom attribution that you added to your solution! 😄

    A few things I'd like to suggest are,

    • Adding overflow-x: hidden to the body of the page (or something similar) to prevent a horizontal scroll bar from appearing along the bottom of the page when the image changes in the "Features" section.
    • Adding a max-width to the header of the page in the desktop layout to ensure that it isn't too wide on extra-large screens.
    • Using the <button> element (rather than a <div>) for the hamburger menu icon (since it is button and that will improve the accessibility of your solution).
    • Perhaps taking another look at your class names. If you're trying to use BEM, I believe there should only be one element per classname (in other words, something like block__element instead of block__element__element), so you might want to simplify some of your classnames a little. I don't think classnames have to reflect the actual structure of your HTML unless that makes things confusing, so you might be able to do things like header__link instead of header__nav__links__link.
    • Considering taking a look at this StackOverflow page (as it might help you clear up those few errors on your solution report).
    • I noticed you created the accordion in this challenge with HTML and JS (and it works well, kudos!) but if you're interested, you can create accordions with just HTML by using the <detail> and <summary> elements. It's pretty nice and easy, and you can learn more about it from this helpful MDN page.

    I hope those tips help. 🙂

    Of course—keep coding (and happy coding, too) my friend! 😁

  • MasterKrab•940
    @MasterKrab
    Posted about 4 years ago

    Hello Roc Tanweer, great job on this challenge!

    I think I can help you with a couple of suggestions.

    • You can add an aria-label to links with descriptive text for screen reader users.
    <a href="#" aria-label="Description">
      <i class="icon" aria-hidden="true"></i>
    </a>
    
    • I think the "More info" button should be a link because it will probably send you to another page with more information.

    • The download-box should be an article or section and not just a div.

    • The hover effects should only be on desktop because on mobile is problematic and does not make sense to place it.

    I hope you find it useful, let me know what you think.

    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.

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