Chat Feature

[jackmcdade]

See it in action:
https://github.com/user-attachments/assets/fb5ed370-04b9-4214-9c1c-c1ec258614fe

The only thing about this approach is that it's using localStorage. It's quick and easy and makes this a zero config option, but also means no real persistence of messages, nor will anyone else not on a collaborating entry be able to use the feature.

Wondering if we should broaden the scope of this feature (if we decide to merge it), and support at least sqlite for persistence 🤔

[tao]

I would pay for a "Collaboration Pro" that let me store chat messages in the database, that way it would be much easier to collaborate and work with translators, and translators can leave notes or messages for future translators about what's going on, or why someone was done things a certain way... and if they have a problem with markdown I could jump into the messages and help them out or we could explain something if they run into a problem.

They could also let us know when it's time to review content, or publish content, or if there are delays.

Currently we are exploring setting up Telegram groups just to help manage communication between translators, so we do have a need for a better way to manage communication for specific entries.

I'm sure that makes things more complex like setting up the database persistence, adding notifications when new messages are sent, or being able to @ping someone but it would definitely help the way we work as a team on Statamic.