diff --git a/server/templates/home.hbs b/server/templates/home.hbs index ffef87eb29..d9d3e68673 100644 --- a/server/templates/home.hbs +++ b/server/templates/home.hbs @@ -4,39 +4,60 @@

Introducing Zed—A lightning-fast, collaborative code editor written in Rust.

- We think there’s a better way to write code. -

-

- We’re building Zed because we want to write code in a tool that is: + We think there’s a better way to write code, and it starts with the following assumptions:

Mission-critical tools should be hyper-responsive.

- When you move the cursor or type a character, you should see pixels on the next refresh of your display–every time. Even sub-perceptual pauses add up over the course of a day to create unnecessary stress. Joyful coding starts with an editor that stays out of your way. + When you move the cursor or type a character, you should see pixels on the next refresh of your display–every time. Even sub-perceptual pauses add up over the course of a day to create unnecessary stress. +

+ +

+ Joyful coding starts with an editor that stays out of your way.

Real-time collaboration produces better software.

- When you move the cursor or type a character, you should see pixels on the next refresh of your display–every time. Even sub-perceptual pauses add up over the course of a day to create unnecessary stress. Joyful coding starts with an editor that stays out of your way. + Pull requests have their place, but sometimes you just want to code together. It’s more fun than code review, builds trust between colleagues, and it’s one of the best ways to distribute knowledge through a team. But it has to be easy. +

+ +

+ If you want someone’s perspective on a piece of code, it should be as easy as sending a message to pull them into your working copy and start coding.

-

Keystrokes are the fundamental unit of change.

+

Conversations about software should happen close to the code.

- When you move the cursor or type a character, you should see pixels on the next refresh of your display–every time. Even sub-perceptual pauses add up over the course of a day to create unnecessary stress. Joyful coding starts with an editor that stays out of your way. + If you want to talk about code on GitHub you have to commit and push it first, and pasting code into a chat application sucks.

-

Early access to Zed will open up mid-2022 for small teams and individuals in our community.

+

+ By treating keystrokes as the fundamental unit of change and integrating chat into the editor, we can make it easy to have a conversation about any line of code in any working copy–whether it was committed last year or just typed ten seconds ago. +

+ +

Our goal is to make you as efficient as possible.

+ +

+ If you’re living in a tool for hours every day, you want it to disappear. Every pixel must carry its weight, and the software you’re creating should always be the focus. So we constantly ask ourselves how we can maximize signal and minimize noise. +

+ +

+ Do we need an icon? Do we need a gradient? We all want to achieve mastery. Our goal is to find the most efficient way to accomplish each coding task and make it accessible. We will never dumb things down. +

+ +

———

+ +

Early access to Zed will open up mid-2022 for small teams and individuals in our + + community.

Read our story. Join the waitlist.

-

———

-

Under the hood

Rust

diff --git a/server/templates/story.hbs b/server/templates/story.hbs index fbe4986217..48af0a6be6 100644 --- a/server/templates/story.hbs +++ b/server/templates/story.hbs @@ -1,8 +1,9 @@ {{#> layout }}
-

We think there’s a better way to write code–and we've been working for more than a decade to bring it into existence. -

+

+ We think there’s a better way to write code–and we've been working for more than a decade to bring it into existence. +

Our first attempt was Atom, which we loved like a child but which ultimately fell short of our original vision. When we created Electron in 2012 to serve as Atom's runtime, there weren't a lot of great options for building cross-platform desktop apps.