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

Responsive fylo data storage component

bem, accessibility
Agustín Firpo•520
@Arfirpo
A solution to the Fylo data storage component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Frontend Mentor - Fylo data storage component solution

Hi everybody! 👋

This is a solution to the Fylo data storage component challenge on Frontend Mentor.

Overview

The challenge 🎯

Users should be able to:

  • View the optimal layout for the site depending on their device's screen size

Links 🔗

  • Solution URL: Github Repository
  • Live Site URL: Github Page

My process ⚙️

Built with 🛠️

  • Semantic HTML5 markup
  • BEM Methodology
  • CSS custom properties
  • Flexbox
  • CSS Grid
  • Mobile-first workflow
  • Media Queries
  • Javascript

What I learned 📚

This challenge allowed me to learn and practice how to configure an input range and how to use javascript to dynamically update the input color

// Add an event listener for the 'load' event to update values and color on initial load
window.addEventListener('load', () => {
  // Get the current value of the input range as an integer
  const usedValue = parseInt(inputRange.value);
  
  // Update the content of HTML elements with used and remaining values
  storageUsed.innerText = usedValue;
  storageLeft.innerText = 1000 - usedValue;

  // Call the function to update the range color
  updateRangeColor();
});

// Add an event listener to the input range to update values and color
inputRange.addEventListener("input", () => {
  // Get the current value of the input range as an integer
  const usedValue = parseInt(inputRange.value);
  
  // Update the content of HTML elements with used and remaining values
  storageUsed.innerText = usedValue;
  storageLeft.innerText = 1000 - usedValue;

  // Call the function to update the range color
  updateRangeColor();
});

// Function to update the color of the range
function updateRangeColor() {
  // Calculate the percentage of the current value in relation to the maximum value and round the result
  const percent = Math.round((inputRange.value / inputRange.getAttribute('max')) * 100);

  // Update the background style of the input range with a linear gradient
  inputRange.style.background = `linear-gradient(to right, 
    hsl(6, 100%, 80%) 0%, 
    hsl(335, 100%, 65%) ${percent}%, 
    hsl(229, 57%, 11%) ${percent}%, 
    hsl(229, 57%, 11%) 100%)`;
}

Author 🙋🏻‍♂️

  • Twitter/X - @agus_firpo
  • Frontend Mentor - @Arfirpo
  • Linkedin - Agustín Rodrigo Firpo
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mohab Mohammed•180
    @mohap710
    Posted over 1 year ago

    Love the Draggable Indicator, Nice Work 👌

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