Dated from the day each change reached production. Anything that is being built rather than running is at the bottom, and anything on neither list is not built.
Modules and lessons carrying video, audio, PDFs and text, with drip scheduling, quizzes, prerequisites and certificates. Hosts build a course in settings and can keep writing it long after members are enrolled, because a course is not one document that gets saved once.
A lesson body is stored apart from the lesson row. A rule can hide a row and cannot hide a column, so a lesson somebody is not entitled to open does not come back at all rather than arriving and being covered up.
Completion is recomputed from what a member has actually done rather than kept as a counter, so adding a lesson correctly un-finishes whoever had finished the older version of the course.
Every community gets a front page assembled from thirteen sections, arranged by whoever runs it. What a visitor meets is now a decision rather than a default.
A stranger can discover a community rather than needing somebody to send them a link — for the communities whose hosts have decided to be findable.
A community reachable at more than one address now redirects to a single canonical one, so links, search engines and shares all agree on where it lives.
PDF carousels, and video and audio with real players rather than a link to somewhere else.
Name somebody in a post or a reply and they hear about it.
A calendar with RSVPs. Times are rendered in the reader’s own zone, and the host’s zone is named only when the clock genuinely differs — so a London host and a Lisbon reader in winter get no footnote about nothing.
Pictures collected in one place rather than only scattered through the feed, behind the same signed links as everything else.
Threaded discussion with its own space labels and reply counts, separate from the feed so a long conversation does not scroll away.
The product’s own visual system, rendered on every surface in both tones. A community that has stated its own accent keeps it in dark as well as light.
Transfer a community to somebody else, change its address, or close it. Each asks you to type the name, and the check happens in the database rather than in the browser.
Settings now shows what the platform itself did inside your community, readable by you and by nobody else who is not in it.
Sign-in links, forgotten passwords and first-time onboarding, verified end to end from our own domain.
Settings now takes a wide logo, a reversed wide logo, a square mark, a reversed square mark, and a tab icon. Two shapes rather than one, because a wide logo cropped into a box and a mark stretched across a band are both the same mistake. A missing shape falls back to your initial or your name in type — never to a transformed version of artwork you gave us.
Addresses in a post are now links, and the first one gets a preview card. Nobody can write a preview through the interface, so a member cannot forge a card for a page they do not control. A bare domain deliberately stays plain text, because “Node.js” and “index.tsx” look exactly like one.
A picker searchable by what somebody would actually type — “deadline” finds the clock. A reply that is only emoji is a gesture rather than a sentence, so it is set at the size of one. Your own emoji are never swapped for another vendor’s.
Four ways one community’s content could be reached from another, and one way a member could raise their own role, were found and closed. Each was verified by attempting it before and after the fix, because a fix that changes nothing looks identical to one that works.
Invite by shareable link or to a single address. Expiry and use limits are enforced in the database rather than by not showing the link, so a link that has run out genuinely stops working.
A host who signs in at the app now stays signed in on their own community’s address. Sessions previously stopped at the host they were created on.
Sign-in links and notifications now send from success.digital with sender authentication in place, so they arrive rather than landing in spam.
Private messages between members, with three rules enforced in the database rather than the interface: a host cannot read them, a conversation link is not an invitation, and a conversation belongs to one community. Notifications record who wrote, never what was said.
Across posts, spaces and channels — and across people for members. Every query runs on the caller’s own session, so results can never disagree with what that person is allowed to see.
One queue for reports and join requests, oldest first. Pin, hide and delete each take a confirmation step, and every decision is written down.
Stored privately with no public read access at all. The server signs a short-lived link, and only for a post the reader could already open.
Chosen by the host and applied to the whole community without a deploy. Accent, tagline and the word for a shared space are stored as data.
Name, tagline, vocabulary, visibility, indexing and modules, all editable by the host.
Host, moderator and member, at both community and channel level. Isolation between communities is enforced by row-level security.
Five destinations at most in the bottom bar, and never a horizontal scroll.
Events, courses and payments are designed and undecided. When they are built they will appear above this line with a date on them, not below it as a promise.
