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: 

Collecting Emails for Community Notifications

Many publishers and community organizers—like those using Substack or WordPress (e.g., Ethosfera)—rely on email to notify their audience about new posts, events, or discussions. Substack makes this seamless by prompting users to enter their email on first visit. Ethosfera uses a simple form in WordPress to collect emails tied to downloading reports. Universities even require a certain domain to join their network. In Seed, we already collect emails during account creation. We could build on this by prompting users to confirm or enter their email when they join a new community or Site. This would allow publishers to send important updates or notifications without relying on external tools, while keeping everything inside the Seed ecosystem. This small UX addition could significantly boost engagement and retention for communities using Seed.

Ethosfera meeting

Notes Solutions Concerns Conclusions

Site Relationships Draft Designs

Member Permission Option 2. Permission for member accessed though account settings only sor the publisher of the site. Joining Experience For Users Panel Settings Document Access Panel

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