@MDDiallo9
Submitted
I can't figure out keyboard controls yet unfortunately
@Aniket200-ind
@MDDiallo9
Submitted
I can't figure out keyboard controls yet unfortunately
@Aniket200-ind
Posted
Great site there!! But I would like to suggest one thing, you can give a fixed height to the main FAQ container as the expansion of accordion is causing CLS problem.
@wlowrimore
Submitted
The biggest hurdle I had in this challenge was the search component. Did anyone else (that used Next.js) run into the e.target.value issue where it called the API after every keystroke? I solved it with debounce. If any of you have a different solution, I would love to hear about it! Thanks!
@Aniket200-ind
Posted
Great work with loading animation.. and the site is good. I am also developing same project in next and this is perfect for me to take inspiration from!!
@defydef
Submitted
This is the solution for Dictionary web app challenge, using React and Tailwind CSS. Feel free to give your feedback, any feedback are welcome π
@Aniket200-ind
Posted
Great site man, loved it!!
@IamArshadAli
Submitted
πββοΈ Hello, Everyone,
Here is my solution for the Time Tracking Dashboard.
94%
on Google Pagespeed Insights! π€©ReactJS
| Designed with TailwindCSS
π οΈ | Mobile-First approach π±prettier-plugin-tailwindcss
to auto-sort TailwindCSS
classes π¨fetch API
to make calls to internal JSON data βοΈBEM
principles to create a consistent structure of TailwindCSS
classesCSS
files to improve site performance πLearned one important thing when injecting SVG's
through inline-CSS
dynamically:
React
so you need quotes around it:backgroundImage: `url("${Background}")`
Reference: Mattia Righetti's answer on StackOverflow
Do you know a better way to deal with using SVG's
as a background imageβ
I'll be happy to hear them. π€
Code Together | Learn Together | Grow Together
@Aniket200-ind
Posted
Great Work! Got inspired from your project and I am also doing this project using nextjs and tailwind. You have done it very well!!
@Lalithanjali-16
Submitted
@Aniket200-ind
Posted
You should give a try to make it responsive, as the content is overflowing on mobile view