Design Updates: Activity Panel, Contacts

Activity Panel Contacts

Document mention email notifications

Demo Brief

Custom Navigation

We have been building a custom navigation UI so you can modify the nav bar of your site! Still working on some minor fixes, but this should be ready for the next release.

Document change email notifications

Demo

Migrating UI Components from Tamagui to Tailwind

(Photo by Miko Guziuk on Unsplash) When we adopted Tamagui, our goal was ambitious but clear: build a unified UI component system that we could reuse across all platforms — Electron (desktop), Web (Remix), and eventually React Native for mobile. The dream of writing once and reusing everywhere was enticing, and early on, it felt like we were on the right track. But reality hit us hard. The Challenges We Faced Admitting Our Part in It Setting a Plan in Motion Choosing Our New Stack Failed Attempts and What We Learned Where We Are Now Thanks for reading! This migration has been a tough but necessary move to keep our momentum as a startup. I’ll continue to share updates as we progress — and hopefully provide more insights for anyone considering a similar shift. Update: 19/06/2025

Unify Accessory panel tabs

This week I worked on making sure users can access to the accessory panels both on web and desktop the same way. The look and feel its not 100% teh same but is very close. This will be improved over time for sure! (Photo by vackground.com on Unsplash)

Feed

We want to bring back Feeds. Problem Solution API Support

Contact Improvement

Problem Solution Design Idea

Inbox

Problem Solution Rabbit Holes / Concerns

Branch Following

Problem Solution

Unify the Search experience across the app

Problem Solution I believe we can use a library like DownShift to create the primitives for all the search instances we need. Scope Rabbit Holes No-Gos

Comment URLs

We need to be able to copy comment URLs, open comment URLs on web and desktop, and we should be able to embed documents Owner: 

Founders Reading List

Augmenting Human Intellect: A Conceptual Framework Authorship Provisions in Augment

Feed of Resources

We have Feeds with events and Feeds with Documents and Comments. On the one hand, we have the Library and the Query block, which display documents and comments. On the other hand, we have Activity Feed showing events. The library is ordered by Activity events. We want the Query block lists also to be requested by Activity events, optionally. I was thinking if we could merge the functionality with the Activity Feed. Currently, it has been decided that the feed will display completely different event items. However, before starting to build it, I want to show the LinkedIn feed where they merge posts, articles, and commentary with activity events. Feed with Documents and Comments as items. Feed with Activity Events Hybrid Feeds

Finding Primitives

Primitives Formal Community versus User Web of Trust

Simplified Site Relationships

Simpler approach Permissions Contact Contact Roles Capability Roles Describes relationship between an account and a document Capabilities Invites Private Actions When a person "joins" a community, they are generally trying to become a member and raise their level of abilities. All roles effectively require two-way consent. Nobody can force you to read or join with a site. And site administrators have the ability to close off abilities to unknown people. Examples Flowchart Protocol Extensions

Comprehensive Site Relationships

The purpose of this document is to describe the most complicated vision that might be necessary. Hopefully we will find ways to simplify this. But some communities may need very advanced relationships and hopefully this document describes almost all of them. Permissions Contact Roles Capabilities Explicit granting of permissions Private Actions When a person "joins" a community, they are generally trying to become a member and raise their level of abilities. All roles effectively require two-way consent. Nobody can force you to read or join with a site. And site administrators have the ability to close off abilities to unknown people. Examples Flowchart Protocol Extensions

Notes on Community Models in Seed

In Seed Hypermedia, we're developing two complementary models for collaboration and trust: the formal community and the user web of trust. A formal community is built for structured collaboration. Membership is explicit and mutual—participants agree to appear on a shared list and to take part in a defined space. This mutuality enables bidirectional permissions and role-based collaboration. Permissions can be scoped both per role and per account. In this model, a Site serves as a shared knowledge repository, where documents are co-authored, versioned, and governed with a common goal in mind. It's ideal for intellectual collectives, research circles, and project-based teams who want durable, verifiable collaboration. In contrast, the user web of trust is informal, lightweight, and decentralized. Here, users build one-way links by following others—trust is expressed individually and does not require reciprocal acknowledgment. This model is designed for discovery, moderation, and social navigation. It’s less about co-creation and more about filtering the open network by relevance, reliability, and proximity. One’s web of trust can surface useful content, suggest reliable voices, and reduce noise without relying on centralized curation. Both models are important to Seed. The formal community supports groups that want to build together. The web of trust empowers individuals to navigate a decentralized environment according to their own values and interests. Together, they allow Seed to remain open and distributed, while enabling structure where needed.