Alternate Boilerplate Setup. Could we get a Chakra code gen?

[cdarland]

The barriers to swapping out the existing Tailwinds/PostCSS modules in favor of an alternative flavor of CSS-in-JS are relatively low (it took me about 10 minutes to prune out all Tailwinds), but it would be awesome if an end user could select a few different framework/library preferences during the initial create-hydrogen-app process to create some alternate boilerplate templates.

To play devil's advocate, I can see a scenario where that leads to a nightmare of configurable permutations that all need to be tested, but selfishly, I'm only thinking about styling and component libraries right now.

[morganmccunn]

Valid feedback! I know @cartogram is going to be diving deeper into the CLI to figure out what configurable options or presets we want to include to enable deviation from the current template.

[julrich]

As developers of a component library (like Chakra UI, with more of a focus on Design Systems) the announcement for hydrogen has really piqued our interest!

Mainly because it would be a perfect fit for customers of ours that also need commerce functionality (in addition to a blog, where we use WordPress, landing pages, career pages, etc). This would enable easy integration for a built Design System... and we're already integrating with Sanity anyways... 🤔

@cartogram if input on this is helpful, or if it'd make sense to chat about this, would love to! I guess the main question for us is: How fixed are the frontend / component decisions with this approach? Will you constantly fight against the way "you're suppoed to do it" when trying to use your own components, or is this something that you want to support (e.g. by having cleanly isolated hooks / context options for use with your own frontend layer)?

[cartogram]

Hey @julrich 👋

As developers of a component library (like Chakra UI, with more of a focus on Design Systems)

Cool! I've never used it, but heard good things!

if input on this is helpful, or if it'd make sense to chat about this, would love to!

For sure, are you in the Shopify discord channel? Happy to chat there or here on GitHub.

it would be awesome if an end user could select a few different framework/library preferences during the initial create-hydrogen-app process to create some alternate boilerplate templates.

I actually have another discussion going around a CLI that would provide this experience. The post is slightly out of date with respect to the progress we've made toward this type of tooling, but the approach is still accurate. I'd love to know your thoughts!

I can see a scenario where that leads to a nightmare of configurable permutations that all need to be tested

I address this in the other discussion and demo prototypes of how we may address the testing issue you've identified.

How fixed are the frontend / component decisions with this approach?

We've tried to write down our thinking on this. Have you had a look at this guide? How does that align with what you are after?