[birdsarentreal]

I think generally it just muddies the waters from a technical perspective. While it's possible to do a simple version of this quite easily, it's more prone to failure than you would think and anything more complicated than plain text isn't so easy. I think given Tina experimented with this in the past it's likely they'll try to make this work at some point, maybe it's on their roadmap.

[jpohalloran]

Exactly right. We tackled inline editing early on, but it had a lot of hidden complexity. Tina's fields are completely customizable, and if we support inline-editing it would be more challenging to make custom fields work while overlaying the site content. There were also challenges around the inline-editing implementation being very entwined in the user's codebase. We do hope to circle back to inline editing in the future, we just want to make sure we land on a stable solution.

[solarkraft]

Thank you! I just found your last blog post on the topic highlighting a few of the issues (https://tina.io/blog/evolution-of-inline-editing/). The solution you came up with looks exactly like what I had in mind!

Are these all the issues you faced? It seems like you mostly solved them, so I'm guessing there were others.

I wouldn't mind having to use the sidebar for secondary fields, I mostly care about the main content field, where I'd spend most of the time. Since (from a cursory glance) you seem to already provide components for rendering Markdown, I don't see a big issue regarding the coupling, at least for my use case.

[tough]

Yes thanks for the explanation i wanted to link to the experimental package I remember trying