6 min read
|
Saved February 14, 2026
|
Copied!
Do you care about this?
This article details how Zed Industries uses its own collaborative editor for team meetings and project work. It outlines the features that enhance real-time collaboration and the company’s vision for improving remote teamwork.
If you do, here's more
Zed Industries holds weekly all-hands meetings every Monday at noon ET, where team members share their weekly focuses and updates. During these sessions, real-time collaboration occurs as everyone edits a shared document simultaneously. The primary goal of Zed is to create a responsive, focused, and collaborative code editor. While many existing editors offer some collaborative features, they often come with cumbersome setups and performance issues. Zed aims to eliminate those problems by integrating collaboration into its core design.
The collaboration aspect utilizes Conflict-free Replicated Data Types (CRDTs), ensuring that changes from multiple users merge seamlessly without conflicts. Setting up Zed requires only a GitHub handle, avoiding the need for additional extensions or links. Built-in audio and screen-sharing capabilities mean users can communicate without relying on external tools. The collaboration panel allows users to create and manage channels for different purposes, including project work and company-wide discussions. Channels can be public or restricted, with a permissions system in place.
Zed's channel structure has evolved to support various forms of collaboration. Company-wide discussions take place in designated channels, such as the "this week" channel for planning and the "retrospectives" channel for reflecting on past work. Project-specific channels act as hubs for feature development, housing goals, member lists, and links to relevant GitHub resources. There are also personal focus spaces for individual work. The design of these channels reflects the team's aim to create an effective environment for collaboration, fostering engagement and productivity among remote workers.
Questions about this article
No questions yet.