Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
19
Comments
18
alvarozama
@alvarozama

All solutions

  • Room homepage


    alvarozama•360
    Submitted 12 months ago

    Any ideas as to how the switching of slides could be improved to be more visually interesting would be greatly appreciated.


    1 comment
  • Loopstudios landing page


    alvarozama•360
    Submitted 12 months ago

    Acessibility. I feel like I'm still unable to get the whole aria label, labelledby, expanded, etc. right.


    1 comment
  • NFT preview card component


    alvarozama•360
    Submitted 12 months ago

    Knowing if I used the BEM methodology correctly. I didn't use any Modifier for this challenge and that makes me think I'm probably not doing the BEM thing quite right.


    1 comment
  • E-commerce product page challenge


    alvarozama•360
    Submitted 12 months ago

    Just the accessibility part. I still can't wrap my head around thing like aria-expanded, aria-controls, aria-label, and the like. I feel like I'm probably not using them correctly.


    1 comment
  • News Homepage Challenge


    alvarozama•360
    Submitted 12 months ago

    Checking for missing accessibility features on my HTML markup.


    1 comment
  • Contact Form challenge


    alvarozama•360
    Submitted about 1 year ago

    Pretty much the above stated points. Any help with that would be greatly appreciated.


    1 comment
  • Faq accordion challenge


    alvarozama•360
    Submitted about 1 year ago

    None that I can think of.


    1 comment
  • Interactive Rating Component


    alvarozama•360
    Submitted about 1 year ago

    The component shows what it has to, but I'm not sure if the handling of the form is right. I'd appreciate it if someone could take a look at that.


    1 comment
  • Tip calculator app


    alvarozama•360
    Submitted about 1 year ago

    So, here are the parts of the project that I couldn't quite implement in a satisfactory fashion:

    1. In order to retrieve the value of a given selected percentage button, I looped through them and used an event listener to look for clicks on said buttons. However, both the retrieval of this value and the calculatio of percentages were coded inside the same function, meaning that the calculation is only performed when clicking on a percentage button. As a result of this, the app only works when entering values for the bill and people inputs first and then selecting the desired tip percentage.
    2. In line whith the previous point, I wanted to make it so that the calculations were performed in real time as the user enters, erases or changes values. To do this I tried to create different functions for retrieveng the selected bercentage button value and for performing the calculations, bus was unable to make them work in tandem.
    3. Whenever the user selects a percentage button it becomes highlighted, but if the user selects a different one without using the reset button, the newly selected button becomes properly highlighted, put the previous one doesn't go back to the default state. I could't find a way to fix this and feel like the problem lies, again, with the implementation of my functions and event listeners.

    1 comment
  • Time trecking dashboard challenge


    alvarozama•360
    Submitted about 1 year ago

    I feel like my fetch statemant is not very well polished, specifically in terms of the handling of errors. Other than that, I realized that when opening the console on the live site, everytime I toggle through the different timeframes a lot of unchaught TypeErrors appear and, in all honesty, I have no idea what that's all about. I'd appreciate if someone could point me in the right direction in terms of mending those errors.


    1 comment
  • Newsletter signup challenge


    alvarozama•360
    Submitted about 1 year ago

    If anything, I'd like to improve the design of the mobile layout. I'm not completely satisfied with it.


    1 comment
  • Article preview component


    alvarozama•360
    Submitted about 1 year ago

    While the solution to the problem previously outlined kind of worked, it only did so when loading the page on a certain screen size and sticking to it. Loading the page on a mobile display would make the share button work as long as one remained on that display. However, when trying to go from mobile to desktop display or viceversa, the behaviors of the button would overlap and the speech bubble meant for desktop display would show on mobile, or the SNS bar meant for mobile would show on desktop. I had no idea how to solve this problem and would appreciate some insights on what I coul do differently.


    1 comment
  • Testimonial grid section project


    alvarozama•360
    Submitted about 1 year ago

    Sizing of the whole page, sizing of the grid, sizing of everything. I feel like my grid, while having a fairly similar layout to the one on the model, is visibly larger.


    1 comment
  • Four Card Feature Section


    alvarozama•360
    Submitted about 1 year ago

    None that I can think of right now.


    1 comment
  • Product Preview Card project


    alvarozama•360
    Submitted about 1 year ago

    Same as last time, the breakpoints for media queries are still something I struggle with. Also, for the sake of brevity, I just used the breakpoints for 475 and 1024px screens, so the transition from one to the other is really messy. I intend to work on implementing a solution to make the whole transition more steadily responsive.


    2 comments
  • Recipe page project


    alvarozama•360
    Submitted about 1 year ago

    I resorted to using some awkward span elemts to style the space between the bulletpoints and the text of lists. I'm wondering if there's a better way of doing this.


    1 comment
  • Social links profile challenge


    alvarozama•360
    Submitted about 1 year ago

    None that I can think of right now.


    1 comment
  • Blog preview card using HTML and CSS


    alvarozama•360
    Submitted about 1 year ago

    Making the layout responsive to shrink the container in size when browsing on mobile devices without media queries. Also, I'm under the impression that images don't show on the live site, so I'm not sure if I'm doing something wrong when calling the src on my index.html.


    2 comments
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

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

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

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

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

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

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

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

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

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

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

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

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