10 ms·
Just started looking, & really like this TinaCMS, from what I've seen of the docs. Semi-headless, Git-backed, so each change goes into a commit. MDX, so you ca
by jauntywundrkind 3y ago
Just started looking, & really like this TinaCMS, from what I've seen of the docs.
Semi-headless, Git-backed, so each change goes into a commit. MDX, so you can have a mix of markdown and more complex content (buttons, or more complex components).
Not a massive fan of graphql per se, but there's a very interesting graphql layer for querying your content. One can define schemas for content, and TinaCMS seems to be able to generate fairly rich data ways to query & search your data.
Some of the advanced features are powered by a level.js compatible store, which was the popular interface for data stores on node & js for a while. The content is still git filesystem backed, so one can just throw out the store & rebuild it, but the store makes it fast to query versus having to reread the filesystem each time. Neat.
The point of this article came down to this observation, which rings true to me. I idealize this model where we have outbrains we can file thoughts & data into, and this seems like a great tool for starting:
> something that Chris Coyier said in his segment stuck with me when he talked about his consistency: the fact that he can just type into a CMS and hit send, with minimal things getting in his way, has kept him more consistent in his writing. I do prefer Markdown and my usual local-first workflow, but the fact that I could spit out a blog quickly without any sort of copying and pasting or editing is something I’m excited to try.