3 ms·
A lot of the problems you’re talking about have been solved for years now. A common setup might be Forestry CMS, Gatsby SSG, and Netlify to build+deploy. And Ti
by ncphillips 7y ago
A lot of the problems you’re talking about have been solved for years now. A common setup might be Forestry CMS, Gatsby SSG, and Netlify to build+deploy. And Tina Teams will be the future of that:
https://tinacms.org/teams https://tinacms.org/teams
- codegeek 7y agoBut my problem is that my customers cannot run cli. they don't even know what command line is forget running anything on it. So are you saying that Tina teams is built for non tech savvy customers who can use th CMS capability but then everything is auto built/deployed static somewhere AND it also retains any dynamic capabilities that were setup ? Here is a use case: 1. Customer logs in to Tina CMS dashboard as admin (similar to WordPress admin login) 2. Customer creates a landing page with dynamic stuff on it. Say a section with some latest blog posts. Again, this is dynamically pulling in from the database. 3. Customer also creates a "Contact Us" page that has a form that auto emails on submission. 4. Once customer has created these 2 pages above (assuming Tina CMS has nice drag/drop building capability like WordPress page builders), now what happens ?
- ncphillips 7y ago> But my problem is that my customers cannot run cli They don't need to. Netlify watches your Github repository and automatically triggers a deploy when changed. They just press save and it gets deployed. > Tina CMS has nice drag/drop building capability like WordPress page builders It does! So does Forestry, it's called the Blocks feature. https://forestry.io/blog/blocks-give-your-editors-the-power-to-build-pages/ https://forestry.io/blog/blocks-give-your-editors-the-power-... https://tinacms.org/docs/fields/blocks https://tinacms.org/docs/fields/blocks