Custom machines / "Using zag for your own components"

[TzviPM]

@segunadebayo I love the work you've done here with Zag and the entire architecture of zag + ark + panda + chakra. I'd love to get some clarity on the vision of zag.js in terms of supporting it as a standard way of building UI components outside of the context of ark vs as a library with a specific philosophy. If the intention long-term is to make Zag into a library for building cross-framework components driven by state machines, I'd love to see or to even collaborate and pitch in on documentation for how to build custom machines, how to define components in terms of an anatomy, etc.

I also wonder about the future of zag as being split into "Zag - the library for building cross-framework UI driven by state machines" and "Zag - the framework-agnostic state machine-based components behind Ark and Chakra"

[segunadebayo]

Thanks @TzviPM.

You've asked some great questions. Ideally, the Zag.js documentation should include a section on modeling custom components using the state machine architecture we support.

"Zag - the framework-agnostic state machine-based components behind Ark and Chakra"

Zag is being used by folks outside of Ark or Chakra, so we don't want to restrict the branding.

Initially, we wanted to focus on Zag being a component logic powered by state machines, to gain some adoption. Now that we have achieved that, it's reasonable to improve the messaging and documentation as needed.