···11+---
22+layout: minimal
33+---
44+55+# Blog
66+77+::blog-posts
+44
docs/docs/pages/blog/introducing-sequoia.mdx
···11+---
22+layout: minimal
33+title: "Introducing Sequoia: Publishing for the Open Web"
44+date: 2023-11-25
55+---
66+77+# Introducing Sequoia: Publishing for the Open Web
88+99+
1010+1111+Today I'm excited to release a new tool for the [AT Protocol](https://atproto.com): Sequoia. This is a CLI tool that can take your existing self-hosted blog and publish it to the ATmosphere using [Standard.site](https://standard.site) lexicons.
1212+1313+If you haven't explored ATProto you can find a primer [here](https://stevedylan.dev/posts/atproto-starter/), but in short, it's a new way to publish content to the web that puts ownership and control back in the hands of users. Blogs in some ways have already been doing this, but they've been missing a key piece: distribution. One of the unique features of ATProto is [lexicons](), which are schemas that apps build to create folders of content on a user's personal data server. The domain verified nature lets them be indexed and aggregated with ease. Outside of apps, lexicons can be extended by community members to build a common standard. That's exactly how [Standard.site](https://standard.site) was brought about, pushing a new way for standardizing publications and documents on ATProto.
1414+1515+The founders and platforms behind the standard, [leaflet.pub](https://leaflet.pub), [pckt.blog](https://pckt.blog), and [offprint.app](https://offprint.app), all serve to make creating and sharing blogs easy. If you are not a technical person and don't have a blog already, I would highly recommend checking all of them out! However, for those of us who already have blogs, there was a need for a tool that could make it easy to publish existing and new content with this new standard. Thus Sequoia was born.
1616+1717+Sequoia is a relatively simple CLI that can do the following:
1818+- Authenticate with your ATProto handle
1919+- Configure your blog through an interactive setup process
2020+- Create publication and document records on your PDS
2121+- Add necessary verification pieces to your site
2222+- Sync with existing records on your PDS
2323+2424+It's designed to be run inside your existing repo, build a one-time config, and then be part of your regular workflow by publishing content or updating existing content, all following the Standard.site lexicons. The best part? It's designed to be fully interoperable. Doesn't matter if you're using Astro, 11ty, Hugo, Svelte, Next, Gatsby, Zola, you name it. If it's a static blog with markdown, Sequoia will work (and if for some reason it doesn't, [open an issue!](https://tangled.org/stevedylan.dev/sequoia/issues/new)). Here's a quick demo of Sequoia in action:
2525+2626+// Demo
2727+2828+ATProto has proven to be one of the more exciting pieces of technology that has surfaced in the past few years, and it gives some of us hope for a web that is open once ore. No more walled gardens, full control of our data, and connected through lexicons.
2929+3030+Install Sequoia today and check out the [quickstart guide](/quickstart) to publish your content into the ATmosphere 🌳
3131+3232+:::code-group
3333+```bash [npm]
3434+npm i -g sequoia-cli
3535+```
3636+3737+```bash [pnpm]
3838+pnpm i -g sequoia-cli
3939+```
4040+4141+```bash [bun]
4242+bun i -g sequoia-cli
4343+```
4444+:::