Email notifications refactor overview

Email Notifications System Documentation Current User Stories Implementation Receive Email Notifications please read this document with user stories for email notifications. Current Limitations Future Development I think we can bring back the accounts table with a flag to determine if the (accountId, email) entry is a subscription or a linked account to email. -- Add back the accounts table with email linking CREATE TABLE accounts ( accountId TEXT NOT NULL, email TEXT NOT NULL, isAccountLinked BOOLEAN NOT NULL DEFAULT FALSE, createdAt DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP, notifyMentions BOOLEAN NOT NULL DEFAULT FALSE, notifyReplies BOOLEAN NOT NULL DEFAULT FALSE, notifyDocChanges BOOLEAN NOT NULL DEFAULT FALSE, notifySiteDiscussions BOOLEAN NOT NULL DEFAULT FALSE, PRIMARY KEY (accountId, email) ); The only issue is that email preferences are different for own account and subscriptions. Because of that I would instead propose creating a separate table for linking an account to email. CREATE TABLE email_account_links ( email TEXT NOT NULL, accountId TEXT NOT NULL, createdAt DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP, notifyMentions BOOLEAN NOT NULL DEFAULT FALSE, notifyReplies BOOLEAN NOT NULL DEFAULT FALSE, notifyDocChanges BOOLEAN NOT NULL DEFAULT FALSE, notifySiteDiscussions BOOLEAN NOT NULL DEFAULT FALSE, PRIMARY KEY (email, accountId) ); And we could add creation of linking tokens to allow verifying the email address in the welcome email. CREATE TABLE email_account_links ( email TEXT NOT NULL, accountId TEXT NOT NULL, linkingToken TEXT UNIQUE NOT NULL, expiresAt DATETIME NOT NULL, isVerified BOOLEAN NOT NULL DEFAULT FALSE, verifiedAt DATETIME, -- NULL until verified notifyMentions BOOLEAN NOT NULL DEFAULT FALSE, notifyReplies BOOLEAN NOT NULL DEFAULT FALSE, notifyDocChanges BOOLEAN NOT NULL DEFAULT FALSE, notifySiteDiscussions BOOLEAN NOT NULL DEFAULT FALSE, PRIMARY KEY (email, accountId) );      

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)

Navigation Infrastructure

https://linear.app/seedhypermedia/issue/SHM-2020/project-navigation-infrastructure

Editor test coverage

https://linear.app/seedhypermedia/issue/SHM-2016/editor-test-coverage

Design Project: Identity System

We are still shaping the design methodology. Please be flexible and constructive. Currently, we have two Active Design Projects. The other one is . It is hard to have two active projects at the same time, but we want to unblock  with this one so he can start working on the cryptography and backend. A Design Project is different from a Development Project, which we have been using all these years. A Design Project involves deep design work, every team member is expected to participate, and it is usually composed of more than one Development Project. Our Design Process follows Google's Design Sprint Methodology. The goal is to provide a mix of methods for meetings and async work. We can use different techniques depending on the Design Project. However, we should always be aware of the 6 phases. It is very probable that every time we skip a phase, we will end up having to come back and redo it, because the outcome won't work. Below are the 6 phases applied to the current Identity System Design Project. Each document should be a method output. Let's see how we operate async! Everybody is expected to: Phase 1: Understanding Phase 2: Define Phase 3: Sketch Phase 4: Decide Phase 5: Prototype Phase 6: Validation Project Tasks

Design Project: New Users quickly understand the Basics of Seed Hypermedia

Outcome: New Users quickly understand the Basics of Seed Hypermedia Sketching Final Design Tasks

Zero-Knowledge Multi-Device Identity System

Problem Scope Solution Rabbit Holes

Combine Favorites and Sync Subscriptions

Problem Solution

Enhancement Note: Add commentary metadata to Card Embeds and Query Block results

https://linear.app/seedhypermedia/issue/SHM-994/add-commentary-metadata-to-card-embeds-and-query-block-results

Enhancement Note: Email improvements

https://linear.app/seedhypermedia/issue/SHM-1834/major-email-issues

Enhancement Note: Comments on moved documents

https://linear.app/seedhypermedia/issue/SHM-1754/comments-on-moved-documents

Notions: Documents and Pages

Documents and Pages are different notions. In Seed, documents are automatically turned into webpages, which can look confusing to people. Bea is proposing to change the wording to use 'Page' instead of 'Document'. I believe we first need to research the meaning of each notion before taking a drastic decision. Maybe we need both terms! What if a Webpage is a document with a web URL and a layout that you configure in the Preview Screen? Dynamic Webpages, Static Documents Most products get this wrong. Definitions in the Web Context Opportunity to clarify the Notions in the Publish User Task Site Owners want Layouts for their Sites

Unified Auth System

Understanding Auth in HM Today Possible Insight Solutions Improvement Proposal: Move host.s.h.m IDs to h.m Thought Experiment: DomainID "Creation" is an external process to the HM protocol Improvement Proposal: DNS-Focused Identity Improvement Proposal: Login Strategy is to input your personal domain name. Improvement Proposal: No email notifs without an account Enterprise Offerings Workflow: New User Subscription Workflow: New Commenter on Self-Hosted Site Workflow: Log in with Existing Identity (different domain) Workflow: Log in to your own site Workflow: Log in to h.m, or social.nytimes.com How all of this works:

Microsoft Sharepoint

Inspiration