We’re excited to announce TinaCMS: an open-source site editing toolkit for React-based sites, especially Next.js). See the announcement video at J...
For further actions, you may consider blocking this person and/or reporting abuse
It's up to developers to define if fields should go in the sidebar or if they should be edited inline in the page. See: tinacms.org/docs/inline-editing/
And yes Tina is using
contentEditableunder the hood :)I set up TinaCMS on a Gatsby blog site I'm working on today and it was a quick and easy process. I definitely recommend checking this one out!
Super glad to hear that! <3
This looks great. I was speaking to Frank and the other Forestry folks at Smashing Conf NY (sorry I forgot their names!), and TinaCMS looks really interesting. I'm excited to try it.
Watched the demo it was really amazing🔥. Can't wait to use it in my next project.
Awesome! Reach out in slack or on twitter if you have feedback if you need help.
WOW! Just WOW! this is amazing! Great job. Can't wait to use it!
I have two blogs made with Gatsby, this seems interesting, I'll try it one of these days thanks
Awesome... I will try it
Great tool.
Congratulations for the launch 🚀👍
I wish CMS would decouple, be a headless editor that I can use remotely or embedded. Anyway this CMS looks nice.
Hey, Tina maintainer here.
Using Tina to build your site is an examples of low coupling and high cohesion.
Why is it low coupling? If you need to upgrade Gatsby you don't have to upgrade Tina, and vice versa; if you change your data storage, all your form definitions remain the same; etc.
Why high cohesion? Because everything you need to know about how your content is created, edited, and displayed is grouped together.
These qualities mean TinaCMS provides a substantially better experience for both the developer and the editor
As a developer your workflow is incredibly fast; it's easy to upgrade different parts of the stack independently; and you have way more control then with traditional CMSs.
Content editors get an interface that makes sense to them. In traditional CMSs, editors need to understand how this hug abstract set of form get turned into their website. With Tina, the link is immediately apparent.
For that you can check out AnyMod.com
I'm currently using MDX + NetlifyCMS, but this looks really next gen! Nice work!
While TinaCMS doesn't technically "support" MDX, you can definitely write use MDX components inside your content. Check it out! Maybe you'll be converted ;)
Hi NCPhillips! Can you describe how this can be achieved? Thank you in advanced!
There is actually now a
gatsby-tinacms-mdxplugin!It's still pretty alpha.
npmjs.com/package/gatsby-tinacms-mdx
How does this work for sites that need to localize content or manage multiple branded websites etc? Maybe it doesn't cater for that use case (which is fine) but just trying to understand any limitations that may dictate where it does and doesn't make sense to use it.
Hey, Tina is a very new project (pre 1.0) so we don't have examples of i18n implementations yet. However, I can tell you where we see it going. We want Tina to work for very small sites - like, a personal portfolio - but scale up to very large sites - like, multi-lingual sites with lots of content and many contributors.
Stay tuned here: tinacms.org/community
This looks really good, been searching for something like this for a while so definitely going to test it in my next project, thanks!
Sounds way too nerdy to really catch on.
Is... Is this named after the llama from Napoleon Dynamite?
Tina adds editing functionality to react based sites only? Is there a way to add this editing functionalities to a multi page static site written in html and css?