We track projects' progress at Hypertuesdays. In Development Pitches Completed Canceled

Conversations about technology and enlightenment.

Documents and files User tests UX Foundations Recordings of the interviews Post test Suggested actions UI Components

   Reference Material

Read first , , , and . List of Documents:

Blue: Done, Green: Building, Black: to do, Yellow: Proposal. Set Up Seed Hypermedia Read and Navigate Subscribe and Archive Manage Contacts Write and Collaborate Publish and Broadcast Configure Client, Wallet, and Web Server

SaaS will not be replaced outright by probabilistically generated code. The real risk for existing SaaS products is different: they may become a legacy layer. Workflows and collaboration will move elsewhere, while traditional SaaS is reduced to a backend that merely stores structured data and historical context. In that scenario, SaaS becomes part of the old stack—present, but no longer where the work actually happens. That’s our opportunity: we must excel in workflows and collaboration. Many companies pay significant SaaS costs while using only a small fraction of the available features. We can target those high-cost tools and offer a simpler, more attractive alternative focused on what teams actually use. Instead of competing head-on, we treat existing SaaS platforms as legacy data sources. Our interface becomes the primary workspace, backed by our own authoritative data structures, while legacy SaaS systems are read from, written to, or gradually replaced.

Methodologies are a necessary element for human intellect augmentation.

Product Principles Personas Story Map

Drafting content for widespread distribution

I am accessing the Library all the time. It is incredibly frustrating to have to open the Sidebar all the time—a similar bad experience to changing the account. Accessing the Library is a core step in my navigation. It allows me to switch between Knowledge Repositories. Favourites don't help because they lack the Activity information! I don't think we have settled on the name Library. Sometimes feels precise, sometimes not at all, and I would like something like Home. Anyhow, I am happy to keep the name Library until we have a clear alternative. In addition to the core functionality of switching between knowledge repositories and finding new activity, the Library is my space as a knowledge operator. I can see my subscriptions, my favourites, and everything else stored on my node. The node can be my desktop or my server. The dream experience is a place where I can search for or query any argument or block, and create my own lists of content and views to understand a complex problem better. It should be incredibly flexible and powerful. I propose to add a button to the Top Bar. Similar to Google Chrome: And yes i am removing the search button from there and moving it to both the sidebar and the top of the library!

Every time we have a meeting, it's useful to take notes. When we do, let's put them in this directory.

Top Pains

Tags: #UX, #Frontend, #Backend, #Editor, #Infra, #Seed Bugs, #How Might We Sometimes a Comment is not enough. Write a Note.

Welcome to the Public Home of the Seed Hypermedia Team! Discussions, Projects, and Updates organize this repository.

This is a Story part of the  Map. Pains

Here we post our regular individual updates of our recent progress. We review these documents every week on our "HyperTuesday" team meetings