Customization - how to do it conveniently?

[studio1902]

Customization - how to do it conveniently?

[robdekort]

Not really. I'm not even sure if I will update my own sites to keep up with the latest Peak additions. It would probably change a lot on a project basis anyway. I'd use it more like a starting point and merge new additions in the other way around.

But I'm very curious about your opinions. Maybe it's good to discuss some to see if it would make sense to merge it in?

[vladdu]

Maybe this is more of a problem while Peak is actively developed while my site is not published yet, so there's always the wish to get the freshest tools. Also it feels nice to go to any of my sites and not have to remember what the configuration was, it takes a while for me to realize "oh, here I didn't have this thingie, that's why it's not working!"

I think the tailwind config is mostly affected. There are many different plugins, some with a lot of configuration. For example, I would like to have the css config you are adding to tailwind as a separate file, as well as the @tailwindcss/typography config.

The rest is probably just things I prefer (like always install statamic/ssg and @tailwindcss/ui). If there's something I feel is more generic I will submit a PR.

[robdekort]

Yeah, I get what you're saying. About the TW file: I've thought about separating it, but t.b.h. I think it's actually really convenient to have it just one file. When separating it, you have to make choices for what to separate and what not. Maybe this is something to revisit. Please share if you have a nice way of doing this. I'm very much open to change!

[robdekort]

Closing this for now! Please feel free to add issues for individual stuff that should be up for debate!

[vladdu]

ok