Opportunities with clearly defined outcomes:
Users will stop confusing Contacts and Sites and will make sure they are mentioning the right people, giving more confidence that some information will be seen by the recipient.
In Ghost Town, if we introduce users to joining sites, they will create and participate in more communities.Joining Sites in Ghosttown
User will getUI: Email Project horacio
ChatGPT/CLI to interact with AI, with the hypertext context. Eric Vicenti
Sign up and Sign in (🔄 in progress)
User Tasks:
Anonymous Accounts
Projects:
New Project for Signin/up Desktop App. Alex Burdiyan
Bea's design on Onboarding. Bea
The onboarding should end up with a beautiful site that the user wants to contribute to and share with others:
onboarding account creation and create sites are two different flows.
Project/Design User creates its on Site. Bea
Pains: In account creation, users add icon images that are more suited as cover images. Images and icons
Join/subscription site and follow behaviour (🔄 in progress)
Edit your Profile.
Vault edit profile horacio Eric Vicenti Vault Design and Settings
Settings page
Create and Publish flow (🔄 in progress)
User Task: Publish a Document to a Site.
Projects:
Forum Usecase Project. horacio
the query block thingy and cards design.
think this unified with the all documents page.
and the explore library.
Scroll reposition:
Create a bug
Friction when different interactions:
When I am on the edit publish flow (it goes back to the top)
When I want to replace and image (in ocasions it loses the position confusing the image you are replacing)
Grid card interactions: Query block
Comments:
Query Block to Regular Blocks?
Let the writer find better the editing options: layouts, indentation, block types: editor commands as grid.
Simplify Editor Menus?
Comment edition:
As a user you can edit a comment
As a user you can delete a comment
Notifications (🔄 in progress).
User Tasks:
Projects:
Comments:
Impossible to follow up conversations.
We want one flow, but if Account Creation flow is too difficult then we might need to different flows. (hopefully not!)
Versions logic: User always access to the latest version. Add a message about version have been updated in a message, users doesn't have to click anything, always access latest version first.
Might be Bug!!!
Bookmark logic flow: you bookmark a document not a site. Right now this functionality is mixed up. Create a block.
User Task: Compose Content on a Draft.
Projects:
Comments:
We have the designs. We need a project.
Design ready for horacio or Iskak Toltay .
Feed versus activity versus notifications: Where it goes?
Search bar behaviour / Search Page
Projects:
Sharing and role permissions flow - Invitation Flow and Permissions. (TBD)
Discover other sites - What is library today (TBD)
Importing content.
User Task:User wants to open a document
Project:
Unreferenced documents: onboarding (TBD)
Private docs. flow review: Show private documents in a document.
See All Documents.
Dark Mode.
Protocol Viewspecs: Level, Collapse, and Filter. Default and Reader configurable Viewspecs.