I am proud of the way it visually turned out, and the readability of the code. There's nothing i wish to change for now on.
What challenges did you encounter, and how did you overcome them?Everything was straight forward, just reading the documentation and everything went smooth.
What specific areas of your project would you like help with?Nothing really
Nice work!
There are a few subtle differences; the default font size should be 16px according to the design. ;)
Nice work! It made me realize I missed handling the click outside event. :D
I started the project trying to use Sass and Tailwind together. After running into many errors and researching best practices, I realized it would be better to simplify the project. In the future, I will keep in mind that over-optimization can often be a hinderance.
What challenges did you encounter, and how did you overcome them?Trying to offset the hero image as it splits for the desktop view was tricky. I had to go back to the basics and research positioning on mdn. It helped me devise a solution that was much simpler than what I'd had before.
What specific areas of your project would you like help with?I feel pretty good about my solution. Any suggestions are welcome!
You’ve made an awesome solution!
It makes me realize that focusing too much on the initial design can sometimes lead to unnecessary rules. I really enjoyed the breakpoints you chose and how you handled the responsiveness.
Seeing your code reminds me that CSS modules can be much cleaner compared to Tailwind.
how use grid-item & css child selectors.
Hi, nice work!
I think your breakpoint changes happen a bit too early. :)
dasd
What challenges did you encounter, and how did you overcome them?asd
What specific areas of your project would you like help with?asd
Hi,
Just a subtle difference 🥲
Great work!
However, be careful with the bullet markers in the unordered list, as they are not properly centered. To my knowledge, this can't be easily fixed with native markers or Tailwind's default utilities. :)
I am proud of trying to improve my code. Next time I will try to use relative units because they provide more flexibility and adaptability for responsive design.
What challenges did you encounter, and how did you overcome them?There was a problem when deploying by Vercel, it didn't work because the images couldn' be read inside the images folder, so I moved the images to the src folder and then it worked.
What specific areas of your project would you like help with?I would like to know why in the following code, relative units in percentage doesn't work but absolute units like px does work.
GitHub
Hi, I tested your code and noticed that in the output generated by Tailwind, it doesn't include a default font size. However, to use rem units, you need to define a base font size. You could, for example, add this to your CSS:
html {
font-size: 16px;
}
Good work overall!
I’m most proud of how Tailwind CSS streamlined my development process.
What challenges did you encounter, and how did you overcome them?Using outline instead of border on the card because the border adds an additional 2 pixels to the element's size, which affects the layout.
I really appreciated your work, especially how you handled the responsiveness. I particularly liked your use of "object-cover w-full h-full" for the image. Awesome work!
This was a complete walkover
There are some subtle differences between your solution and the design. The "Slate" color from Tailwind differs from the one in the design. The same goes for the font sizes in Tailwind, there are a few discrepancies. Also, you missed the drop shadow. ;)
Hello, about the font you have import only font weight 200 so you could only use this weight in your css file. You need to import all font weight you need from google font ;)
