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

    REST Countries API (Next.js & Server Actions + TypeScript + Tailwind)

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

    4


    šŸŽ Features:

    • Next.js Server Actions to fetch data with:
      • Filtering šŸ“‚
      • Pagination ā™»ļø
      • Sorting šŸ”
    • Achieved +95% in Lighthouse score for performance, accessibility, best practices, and SEO. šŸ“Š
    • Resemblance with the original design. šŸŽØ
    • Small animations with Framer motion. šŸŽ¬
    • No errors or warnings using ESLint (Airbnb style guide). āœ”ļø
    • Custom hooks. šŸŽ£
    • Utilized TailwindCSS for responsive styling. šŸŽØ
    • Codebase is well-maintained and formatted using Prettier. šŸ’»

    šŸ› ļø Built With:

    • Next.js 14. āš”
    • TypeScript šŸš€
    • TailwindCSS. šŸŽØ
    • ESLint (Airbnb style guide). šŸ“¦
    • Framer-motion. šŸŽ¬
    • npm - prettier - prettier-plugin-tailwindcss. šŸ’»

    šŸ” Clarifications:

    • While the Rest Countries API was an option, it had limitations like lack of pagination and limited filtering capabilities. I opted to utilize Server Actions in Next.js and the data.json provided with the challenge. This allowed seamless integration with MongoDB for efficient data handling.
    • I acknowledge that continuous polling for change requests might consume more data, but it was implemented for experimental purposes.

    Any suggestions on how I can enhance this solution or achieve even better performance are welcome!

    Thank you. šŸ˜ŠāœŒļø

  • Submitted

    PayAPI multi-page website (Next.js + TypeScript + Tailwind + ESLint)

    #backbone#next#tailwind-css#typescript#lighthouse
    • HTML
    • CSS
    • JS

    12


    šŸŽ Features:

    • Achieved 98% in Lighthouse score for performance, accessibility, best practices, and SEO. šŸ“Š
    • Simplifying form management using react-hook-form. šŸ“
    • TypeScript-first schema declaration and validation usin zod library. āœ….
    • Resemblance with the original design. šŸŽØ
    • Small animations with Framer motion. šŸŽ¬
    • Ensuring a delightful experience for users who prefer reduced motion. šŸš«šŸŽ‰
    • No errors or warnings using ESLint (Airbnb style guide). āœ”ļø
    • Custom hooks. šŸŽ£
    • Progressive Web App (PWA) support. šŸ“±šŸŒ
    • Utilized TailwindCSS for responsive styling. šŸŽØ
    • Codebase is well-maintained and formatted using Prettier. šŸ’»
    • Tested with the TalkBack screen reader on mobile. šŸ“±šŸ”Š
    • Toast Component with Sonner. šŸžšŸ””

    šŸ› ļø Built With:

    • Next.js 14. āš”
    • TypeScript šŸš€
    • TailwindCSS. šŸŽØ
    • react-hook-form and zod. šŸ“
    • ESLint (Airbnb style guide). šŸ“¦
    • Framer-motion. šŸŽ¬
    • npm - prettier - prettier-plugin-tailwindcss. šŸ’»

    Any suggestions on how I can enhance this solution or achieve even better performance are welcome!

    Thank you. šŸ˜ŠāœŒļø

  • Submitted

    Social proof section (Tailwind CSS šŸŽØ)

    #accessibility#lighthouse#pwa#tailwind-css#semantic-ui
    • HTML
    • CSS

    6


    Hi there šŸ‘‹, Iā€™m Melvin, and this is my solution for this challenge. šŸš€

    šŸŽ Features:

    • Achieved 100% in Lighthouse score for performance, accessibility, best practices, and SEO. šŸ“Š
    • Progressive Web App (PWA) support. šŸ“±šŸŒ
    • Utilized TailwindCSS for responsive styling. šŸŽØ
    • Codebase is well-maintained and formatted using Prettier. šŸ’»

    šŸ› ļø Built With:

    • TailwindCSS. šŸŽØ
    • npm - prettier - prettier-plugin-tailwindcss. šŸ’»

    Thank you. šŸ˜ŠāœŒļø

  • Submitted

    FAQ accordion (Tailwind CSS)

    #accessibility#animation#pwa#tailwind-css#lighthouse
    • HTML
    • CSS
    • JS

    6


    Hi there šŸ‘‹, Iā€™m Melvin, and this is my solution for this challenge. šŸš€

    šŸŽ Features:

    • Achieved 100% in Lighthouse score for performance, accessibility, best practices, and SEO. šŸ“Š
    • Progressive Web App (PWA) support. šŸ“±šŸŒ
    • Utilized TailwindCSS for responsive styling. šŸŽØ
    • Codebase is well-maintained and formatted using Prettier. šŸ’»
    • Resemblance with the original design. šŸŽØ
    • No media queries were used. šŸ“±
    • Integrated very small animation. āœØ

    šŸ’» Two Solutions in Two Branches:

    šŸ› ļø Built With:

    • TailwindCSS. šŸŽØ
    • npm - prettier - prettier-plugin-tailwindcss. šŸ’»

    Any suggestions on how I can enhance this solution or achieve even better performance are welcome!

    Thank you. šŸ˜ŠāœŒļø

  • Submitted

    Skilled e-learning landing page (Tailwind CSS)

    #accessibility#lighthouse#pwa#tailwind-css#semantic-ui
    • HTML
    • CSS

    5


    Hi there šŸ‘‹, Iā€™m Melvin, and this is my solution for this challenge. šŸš€

    šŸŽ Features:

    • Achieved 100% in Lighthouse score for performance, accessibility, best practices, and SEO. šŸ“Š
    • Progressive Web App (PWA) support. šŸ“±šŸŒ
    • Utilized TailwindCSS for responsive styling. šŸŽØ
    • Codebase is well-maintained and formatted using Prettier. šŸ’»
    • Resemblance with the original design. šŸŽØ

    šŸ› ļø Built With:

    • TailwindCSS. šŸŽØ
    • npm - Prettier. šŸ’»

    Any suggestions on how I can enhance this solution or achieve even better performance are welcome!

    Thank you. šŸ˜ŠāœŒļø

  • Submitted

    Four card feature section (Tailwind CSS)

    #accessibility#lighthouse#pwa#tailwind-css#semantic-ui
    • HTML
    • CSS

    6


    Hi there šŸ‘‹, Iā€™m Melvin, and this is my solution for this challenge. šŸš€

    šŸŽ Features:

    • Progressive Web App (PWA) support. šŸ“±šŸŒ
    • Achieved 100% in Lighthouse score for performance, accessibility, best practices, and SEO. šŸ“Š
    • Utilized TailwindCSS for responsive styling. šŸŽØ
    • Codebase is well-maintained and formatted using Prettier. šŸ’»
    • Resemblance with the original design. šŸŽØ

    šŸ› ļø Built With:

    • TailwindCSS. šŸŽØ
    • npm - Prettier. šŸ’»

    Any suggestions on how I can enhance this solution or achieve even better performance are welcome!

    Thank you. šŸ˜ŠāœŒļø

  • Submitted

    Time tracking dashboard (Next.js + TypeScript + Tailwind CSS + ESLint)

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

    3


    Hi there šŸ‘‹, Iā€™m Melvin, and this is my solution for this challenge. šŸš€

    šŸŽ Features:

    • Tabbed interfaces. šŸ“‘
    • Controllable using arrow keys and Tab. āŒØļø
    • Tooltip that allows copying statistics. šŸ“Š
    • Resemblance with the original design. šŸŽØ
    • Progressive Web App (PWA) support. šŸ“±šŸŒ
    • Small animations with Framer motion. šŸŽ¬
    • No errors or warnings using ESLint (Airbnb style guide). āœ”ļø
    • Client-side fetching with SWR to simulate an API. šŸŒ
    • Custom hooks. šŸŽ£
    • Tested with the TalkBack screen reader on mobile. šŸ“±

    šŸ› ļø Built With:

    • Nextjs 13.5.4. āš›ļø
    • TypeScript. šŸ“
    • TailwindCSS. šŸŽØ
    • Framer-motion. šŸŽ¬
    • ESLint (Airbnb style guide). šŸ“¦

    ā“ Question:

    Not very proud of the prop drilling in the solution. Any recommendations to avoid it? I've tried using the Context API to reduce it, but I don't see much difference.

    Any suggestions on how I can improve and reduce unnecessary code are welcome!

    Thank you. šŸ˜ŠāœŒļø

  • Submitted

    Fylo dark theme landing page (React JS + Tailwind CSS + Framer Motion)

    #accessibility#framer-motion#lighthouse#react#tailwind-css
    • HTML
    • CSS
    • JS

    16


    Hi there šŸ‘‹, Iā€™m Melvin and this is my solution for this challenge. šŸš€

    šŸŽ Features:

    šŸ› ļø Built With:

    • React JS. āš›ļø
    • React Hook Form. šŸ“
    • Framer Motion. šŸŽ¬
    • TailwindCSS. šŸŽØ
    • npm - prettier - prettier-plugin-tailwindcss. šŸ“¦

    Any suggestions on how I can improve and reduce unnecessary code are welcome!

    Thank you. šŸ˜ŠāœŒļø

  • Submitted

    Article preview component (Tailwind CSS + JavaScript)

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

    13


    Hi there šŸ‘‹, Iā€™m Melvin and this is my solution for this challenge. šŸš€

    šŸ› ļø Built With:

    • TailwindCSS
    • npm - prettier

    Any suggestions on how I can improve and reduce unnecessary code are welcome!

    Thank you. šŸ˜ŠāœŒļø

  • Submitted

    Single price grid component (Tailwind CSS)

    #accessibility#tailwind-css
    • HTML
    • CSS

    9


    Hi there šŸ‘‹, Iā€™m Melvin and this is my solution for this challenge. šŸš€

    šŸ› ļø Built With:

    • TailwindCSS
    • npm - prettier

    Any suggestions on how I can improve and reduce unnecessary code are welcome!

    Thank you. šŸ˜ŠāœŒļø

  • Submitted

    Stats preview card component (Tailwind CSS)

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

    6


    Hi there šŸ‘‹, Iā€™m Melvin and this is my solution for this challenge. šŸš€

    ā“Help:

    • I'm trying to get a 100% score on Lighthouse, any resources or videos you can share would be very helpful. Especially, How to improve my FCP (First Contentful Paint) score?

    šŸ› ļø Built With:

    • TailwindCSS
    • npm - prettier

    Any suggestions on how I can improve and reduce unnecessary code are welcome!

    Thank you. šŸ˜ŠāœŒļø

  • Submitted

    NFT preview card component (Tailwind CSS)

    #accessibility#tailwind-css
    • HTML
    • CSS

    6


    Hi there šŸ‘‹, Iā€™m Melvin and this is my solution for this challenge. šŸš€

    Built With:

    • TailwindCSS
    • npm - prettier

    Any suggestions on how I can improve and reduce unnecessary code are welcome!

    Thank you. šŸ˜ŠāœŒļø

  • Submitted

    Bookmark landing page (React + TailwindCSS)

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

    4


    Hi there šŸ‘‹, Iā€™m Melvin and this is my solution for this challenge. šŸš€

    Help:

    • I'm not very good with animations, I would really appreciate any resources you can provide.

    Built With:

    • React-JS
    • TailwindCSS
    • Yarn - Vite - Prettier

    Any suggestions on how I can improve and reduce unnecessary code are welcome!

    Thank you. šŸ˜ŠāœŒļø

  • Submitted


    Hi there šŸ‘‹, Iā€™m Melvin and this is my solution for this challenge. šŸš€

    Help:

    • Any resource or suggestion on how to create or improve the accessibility of a switcher theme component is welcome; although this is the code for my component, I will be grateful for any suggestions.

    I added:

    • šŸŒ” Light and Dark mode
    • šŸ”§ Using localStorage to save theme preferences

    Built With:

    • React-JS
    • TailwindCSS
    • Yarn - Vite - Prettier

    Any suggestions on how I can improve and reduce unnecessary code are appreciated!

    Thank you. šŸ˜ŠāœŒļø

  • Submitted

    URL shortening API landing page (React šŸš€ + SASS modules + Axios)

    #accessibility#react#sass/scss#vite#axios
    • HTML
    • CSS
    • JS
    • API

    4


    Hi there šŸ‘‹, Iā€™m Melvin and this is my solution for this challenge. šŸš€

    Questions:

    • In React, what is the most popular class naming convention?
    • I've read that it's not recommended to have three or more nested folders within a project, so what's the most common way to organize files in React?

    Features:

    • šŸ”§ Focus on button using forwarding references
    • šŸ”§ Using localStorage to save url
    • šŸ”’ Form validation with react-hook-form
    • šŸ”” Notifications with react-toastify
    • šŸŽØ Custom scrollbar

    Built With:

    • React-JS
    • SASS modules
    • BEM naming convention
    • Axios - Dotenv
    • react-hook-form
    • react-toastify
    • Yarn - Vite

    Any feedback on how I can improve and reduce unnecessary code is welcome!

    Thank you. šŸ˜ŠāœŒļø

  • Submitted

    Ping single column coming soon (React + TailwindCSS + Dark/Light mode)

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

    2


    Hi there šŸ‘‹, Iā€™m Melvin and this is my solution for this challenge. šŸš€

    I added:

    • šŸŒ” Light and Dark mode
    • šŸ”§ Using localStorage to save theme preferences
    • šŸ”’ Form validation with react-hook-form
    • šŸ”” Notifications with react-toastify
    • šŸŽØ Custom scrollbar

    Built With:

    • React-JS
    • TailwindCSS
    • react-hook-form
    • react-toastify
    • Yarn - Vite

    Any feedback on how I can improve and reduce unnecessary code is welcome!

    Thank you. šŸ˜ŠāœŒļø

  • Submitted

    3-Column Card Component (SASS + Flexbox + BEM)

    #accessibility#sass/scss#bem
    • HTML
    • CSS

    5


    Hi there, Iā€™m Melvin and this is my solution for this challenge. šŸ‘‹

    Any feedback on how I can improve and reduce unnecessary code is welcome!

    Thank you. :)

  • Submitted


    Hi there, Iā€™m Melvin and this is my solution for this challenge. šŸ‘‹

    Features:

    • AOS (Animate on Scroll) with prefers-reduced-motion.
    • Custom scrollbar

    Any feedback on how I can improve and reduce unnecessary code is welcome!

    Thank you. :)

  • Submitted

    Advice Generator App (SASS + JS + BEM + Mobile-first)

    #bem#fetch#sass/scss#accessibility
    • HTML
    • CSS
    • JS
    • API

    2


    Hi there, Iā€™m Melvin and this is my solution for this challenge. šŸ‘‹

    • I add a delay and a spinner during loading to prevent the user from spamming the button. Do you think the spinner is accessible enough?
    • What tips would you give me to improve the accessibility of the page?

    Any feedback on how I can improve and reduce unnecessary code is welcome!

    Thank you. :)

  • Submitted

    Interactive Rating Component (SASS + JS + Mobile-first + BEM)

    #bem#sass/scss#accessibility
    • HTML
    • CSS
    • JS

    3


    Hi there, Iā€™m Melvin and this is my solution for this challenge. šŸ‘‹

    • I created some simple animations. I would greatly appreciate any reading resources that can improve the animations.
    • What tips would you give me to improve the accessibility of the page?

    Any feedback on how I can improve and reduce unnecessary code is welcome!

    Thank you. :)

  • Submitted


    Hi there šŸ‘‹, Iā€™m Melvin, and this is my solution for this challenge. šŸš€

    šŸ› ļø Built With:

    • SASS. šŸŽØ
    • BEM notation. šŸ“
    • Mobile-first approach. šŸ“±

    Any suggestions on how I can enhance this solution or achieve even better performance are welcome!

    Thank you. šŸ˜ŠāœŒļø

  • Submitted

    Order summary component (SASS + Mobile first + BEM)

    #accessibility#sass/scss#bem
    • HTML
    • CSS

    1


    Hi there šŸ‘‹, Iā€™m Melvin, and this is my solution for this challenge. šŸš€

    šŸ› ļø Built With:

    • SASS. šŸŽØ
    • BEM notation. šŸ“
    • Mobile-first approach. šŸ“±

    Any suggestions on how I can enhance this solution or achieve even better performance are welcome!

    Thank you. šŸ˜ŠāœŒļø

  • Submitted


    Hi there šŸ‘‹, Iā€™m Melvin, and this is my solution for this challenge. šŸš€

    šŸ› ļø Built With:

    • SASS. šŸŽØ
    • BEM notation. šŸ“
    • Mobile-first approach. šŸ“±

    Any suggestions on how I can enhance this solution or achieve even better performance are welcome!

    Thank you. šŸ˜ŠāœŒļø

  • Submitted


    Hi there šŸ‘‹, Iā€™m Melvin, and this is my solution for this challenge. šŸš€

    šŸ› ļø Built With:

    • SASS. šŸŽØ
    • Gird layout. šŸ“

    Any suggestions on how I can enhance this solution or achieve even better performance are welcome!

    Thank you. šŸ˜ŠāœŒļø