Provide hello-world as an independent template repo

[benjaminsehl]

Heard this from some folks who were looking to create their own opinionated Hydrogen starters — thought it was an interesting idea. Would love to discuss how feasible this might be.

[duncan-fairley]

To stay on top of changes we have set up an internal repo that periodically pulls the latest from hello-world and demo-store into a folders to alert us to changes that we may want to pull into our H2 projects.

A more ideal configuration might be a separate template repo for hello-world that we could fork to create our own internal template then fork again for each project. Feels like this could make open the door to some more interesting dependency management strategies if I'm thinking about it in the right way.

[danieldietzel]

I think it would be useful for certain common issues or needs. Some examples I coded myself that may be useful for others:

• Implementing meta pixel including add to cart with value
• Making a product card where the selected variant is contained within the component's state instead of the URL (so I can show multiple products with variants on one page)
• Adding a different gallery that natively works with media objects
• Using CDN tailwind if you need to dynamically inject HTML with tailwind classes
• Configuring parts of the app with metaobjects
• Changing routes and redirecting standard routes

Remix does this with community examples: https://github.com/remix-run/examples.

Right now we are mostly copy/pasting code in the shopify discord to help each other but the knowledge is lost as soon as the next conversation starts. Having some community samples could have cut the time in half for me.