To do this, I've had to basically clone the entire ory elements repo as well so I can access to components like https://github.com/ory/elements/blob/main/src/react-components/button-social.tsx where I can make the changes required. My suggestion to the Ory team, and I know you're probably flat out, is that you have the priorities of these libs backwards. Instead of putting the emphasis on limited design control via opaque components, invert this and make it easy to modify the design. To do so, high level, I'd think about: 1. Creating a package which wraps up standard flows and uses a context or similar to store state (this is React focused btw). 2. Provide a "generator" package which outputs all the components in a way that are easy to modify. 3. Provide some clear guidance and examples of how to implement some common changes to the designs that people will make. The thing that is most likely to change over time will be the flows, by making this a separate versioned package then it will be easy for users to upgrade to changes that are happening in the Ory backend.