January 13, 2021
Update: The Tina API has been evolving, and the content in this post is outdated. For help getting started with Tina, we suggest checking out our getting started doc.
It was around six months ago that we last dug deep into Tina's inline editing experience. At that time, we introduced new features and improved the UI of inline editing. Since then, there have been a few pain points we've run into from time to time.
Building is inherently exploratory, and now that we've established some solid idioms for what inline editing should offer, we can step back and be more thoughtful about how we accomplish those things.
We've done a poor job about being adequately transparent on our thoughts, but the developers among various teams at Forestry.io met multiple times over the past few weeks of 2020 to discuss the problems we want to solve with inline editing, and proposed potential solutions to solve them.
For the next six weeks, the TinaCMS team will be delivering improvements to inline editing that align with the following principles:
We've heard from many users that the additional markup inserted by
react-tinacms-inline creates layout headaches that are hard to reckon with. We plan to introduce some changes that minimize and even eliminate this additional markup, making it possible to include inline editing more seamlessly in your production-ready layout code.
Tina currently has two possible interfaces for editing content: sidebar-based, and inline.
Sidebar-based forms are set up by adding a
Additionally, we are interested in providing more streamlined ways to configure inline forms. Being able to consolidate inline field configuration in a form's config object opens up a lot of opportunities for that.
Check out the GitHub project for this cycle to keep tabs on our work.
Last Edited: January 13, 2021