It's impossible to get around the fact that there's a lot of overhead, necessitating the development of new components built with React while creating an application with TinaCMS.
Not everyone has this kind of time or budget. It would be great if the components we build for Tina.io and community components could be collated into some kind of library of preset blocks.
There's a question to ask here about how much these come pre-styled, or is that onus all on the user (i.e. we just handle the Tina template, general structure, data handing and live editing).
Solution
[ ] Discuss solution and who/how this should be maintained
@Marxoz @landonmaxwell @joshbermanssw @bradystroud
Pain 🩸
It's impossible to get around the fact that there's a lot of overhead, necessitating the development of new components built with React while creating an application with TinaCMS.
Not everyone has this kind of time or budget. It would be great if the components we build for Tina.io and community components could be collated into some kind of library of preset blocks.
There's a question to ask here about how much these come pre-styled, or is that onus all on the user (i.e. we just handle the Tina template, general structure, data handing and live editing).
Solution