-
Notifications
You must be signed in to change notification settings - Fork 94
Description
Hey,
Really cool library, thanks for building this!
I have one request and a few super small bugs/ docs recommendations I hope you find helpful
My feature requests: It would be really cool if the navigation components in the example tempaltes were also available.
Besides that, here are a few difficulties I encountered when setting this up:
I followed the next.js installation and tried out one of the examples but kept getting errors like:
Error: Invalid src prop (https://picsum.photos/id/64/100/100) on next/image, hostname "picsum.photos" is not configured under images in your next.config.js
I eventually figured out I had to do this:
/** @type {import('next').NextConfig} */
const nextConfig = {
images: {
domains: ['picsum.photos']
}
};
However, the next.js docs recommend doing something like this:
module.exports = {
images: {
domains: ['https://picsum.photos/']
}
};
Which led to some errors about module.exports. It was an annoying little error that almost made me quit and move on to something else. I recommend adding something about this to the docs.
For some reason I could not figure out, some buttons seem to lose their styling in some of the examples. This does not happen in all the examples I copied
Small one, but if you want to make your docs really world-class I think it helps to be very obvious. Often when devs are trying new things they follow instructions to the tea.
Int the next.js docs after this step:
npx create-next-app@latest my-app --typescript --tailwind --eslint
Remind users that they must cd into my-app and continue with the rest of the steps. I know it seems obvious, but it got me and I've been working with React for a while.
Unless users are familiar with tailwind, in the step of copying things to global.css, make it obvious in the docs that users should keep
@tailwind base;
@tailwind components;
@tailwind utilities;
PASTE CODE HERE...
or just include everything they need to paste.
The landing testimonials has some small styling issues on mobile
Thanks again for working on this.