Socra Creation Flow

To remove friction in creating socras, let's consider the following changes TODO (new) add trash

To remove friction in creating socras, let's consider the following changes TODO (new) - [x] add trashed warning - [x] add copilot back in - [ ] Make sidebar resizable (not going to do) - [x] actions on socra inbox item (replace date on hover) Generated content not ending up in editor. - In order to stream updates to client, user must be subscribed to websocket for the socra - [x] Make sure that detail socra is subscribed to websocket events. Streaming content updates to the client - ideally, we should support streaming chunks of particular fields to the client (name, content) How to generate content? - On socra created, we should have a name, in addition to the socra's journey context. - When the user creates the socra, we should generate an initial draft of the content using this context. We can do this by appending a "fake" user message at the end of the context with the final instructions. This should also work for content updates... - When should we run summarize/extract tags? TODO: - [x] on socra created, run action socras.socra.created - [x] generate initial content draft - [x] on socra completed, run action socras.socra.completed - [x] generate summary and categorize - [x] home page of socra.com should look quite a lot like a search engine. "I want to..." should be the placeholder/label of the text autocomplete - [ ] Title (Required) - [ ] Content (Optional) - [ ] Once user clicks on create socra, display a simple dialog with title only - similar to the journey creation dialog. Explain what a socra is: A thing you want to do. - [ ] Once user creates the Socra, the title is populated and content is optional - [ ] Have AI Create initial draft of socra, user can accept or not - [ ] When title changes, content updates - [ ] Users can chat with AI on right side, AI will ask questions and clarifications and adjust the content according to user input - [ ] Timeline input must be fixed on the bottom - [ ] Updates on timeline are moved to right side panel - [ ] Reply should be different from update - [ ] Revisions are a tree node - [ ]

In the "Socra Creation Flow," Eduarda Ferreira outlines enhancements aimed at streamlining the process of creating socras. Key action items include adding a trashed warning, reintroducing a copilot feature, and ensuring socras are subscribed to websocket events for real-time updates. The interface aims to resemble a search engine, with an intuitive "I want to..." prompt for user interaction. When a socra is created, an initial draft of content is generated using context, and users will have the opportunity to communicate with AI for further refinements. The task management system includes running specific actions upon socra creation and completion, while updates will be displayed in a right-side panel. Overall, the goal is to enhance content generation, facilitate websocket streaming, and improve user experience through effective UI design and AI assistance.

By Eduarda Ferreira