Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found

All solutions

  • Submitted

    Responsive design, tailwindcss, nextjs

    #accessibility#next#tailwind-css#typescript
    • HTML
    • CSS
    • JS

    1


    Feedback is welcomed, CRUD functionality has been implemented and used local storage for persistent data. Styles for buttons and floating labels are implemented for better user experience and interaction.

  • Submitted

    mobile first javascript tailwindcss

    #accessibility#tailwind-css
    • HTML
    • CSS
    • JS

    0


    Any feedback is welcomed. Tech stack comprised of HTML, JavaScript, CSS, and tailwind CSS.

  • Submitted

    Mobile first

    #tailwind-css#accessibility
    • HTML
    • CSS
    • JS

    0


    This is just done in pure javascript and tailwindcss. The layout variation is slightly different from the given design.

  • Submitted

    Responsive design

    #fetch#next#sass/scss#tailwind-css#typescript
    • HTML
    • CSS
    • JS
    • API

    0


    In these challenges. I did not use the given API for searching IP Addresses. I just settled for ipwhois.app/json for testing purposes without signing up. Therefore functionality to search with the domain name is not applied.

  • Submitted

    Mobile first Design next js tailwind

    #next#react#sass/scss#tailwind-css#typescript
    • HTML
    • CSS
    • JS

    0


    constructive feedback is welcome. This project is designed with tailwind CSS and built with next js.

  • Submitted


    Done this challenge using typescript and next js and windicss. Tried this technology stack. Working first time with windicss was little challenging it is an alternative to tailwind CSS. However, I have mixed feelings regarding the utility-first CSS framework. Any feedback is welcome.

  • Submitted


    This challenge was fun to do. I got a little messed up on the flipping section. In the end, I managed to get it done. Any constructive feedback is welcomed.

  • Submitted


    This is a project build with pure js and CSS. This was a fun challenge and at the same time challenging. I have tried to implement all the possible functionality. Any suggestion would be appreciated.

    • No consecutive operators are allowed. eg: +/-*
    • operator gets replaced with a later one. eg: 1+- -> 1+ or 2-* -> 2*
    • A operand can only have a single decimal. eg: 0.1 or 1.0 but not 0..1 or 1..0
    • Infinity if divisor equals zero.
    • Throw an error if the initial operand is '/' or '*'
  • Submitted


    I would appreciate any constructive feedback. The project is built with CSS and Html.

  • Submitted


    This is another challenge so far so good. I have extensively used the Sass module system and partials with the @use rule along with the other variables, mixins, and functions. All customs variables are made with the @map function. Just for the flavor Intersection Observer API is being used in the creation section. It is not perfect. Feedback from communities would be appreciated.

  • Submitted


    Would appreciate the feedback. I have used sass new modules At-rules. I have simply used flex-box and CSS grid for the responsive design layout. And few lines of javascript to control the drop-down menu along with the Sass mixins. It would be helpful if anyone could detail how CSS folders are organized and what design patterns are being followed.

  • Submitted


    Any suggestion is welcome. What would be a better way to scale font size? When using a responsive layout. Different font sizes for different breakpoints or would it be better to use fluid typography.