Publishing a Zola Blog to AT Protocol with Sequoia and wisp.place

2026-07-12

The AT Protocol is an open social networking protocol designed around portable identities, decentralized data, and interoperable applications. Unlike traditional platforms where content is locked inside a single service, AT Protocol allows users to own their identity and publish content through independent services called Personal Data Servers (PDS).

One interesting use case is publishing a personal blog using the site.standard lexicon, allowing blog posts to become part of the AT Protocol ecosystem.

---

What is AT Protocol?

AT Protocol (Authenticated Transfer Protocol) is the foundation behind the Bluesky ecosystem. It separates identity, data storage, and applications:

• DID (Decentralized Identifier): Your portable identity.
• PDS (Personal Data Server): Stores your posts and account data.
• App Views: Applications that index and display AT Protocol content.

Instead of creating a blog tied to a specific platform, a site can publish structured documents that other AT Protocol clients can discover and display.

---

Converting a Zola Blog to standard.site

Zola is a fast static site generator written in Rust. It is great for personal blogs because it produces simple HTML files without requiring a database.

To publish a Zola blog through AT Protocol, the workflow is:

1. Write posts normally using Markdown and Zola front matter.
2. Build the static website with Zola.
3. Use Sequoia to convert posts into site.standard.document records.
4. Publish those records to your AT Protocol account.

Sequoia acts as a bridge between traditional static websites and AT Protocol by mapping blog metadata such as titles, dates, and content into AT Protocol records.

A typical workflow looks like:

zola build
sequoia import public/
sequoia publish

After publishing, each article receives an AT URI:

at://did:plc:example/site.standard.document/xxxxx

This URI uniquely identifies the post across the AT Protocol network.

---

Hosting on wisp.place

After generating the static website, the final HTML files can be hosted on wisp.place.

The deployment process is simple:

1. Build the Zola website.
2. Upload the generated public/ directory to wisp.place.
3. Configure the domain and HTTPS.
4. Keep AT Protocol records synchronized through Sequoia.

This creates a hybrid blog:

• Zola provides a fast traditional website.
• AT Protocol provides portable content ownership.
• wisp.place provides simple static hosting.

---

Conclusion

AT Protocol does not replace traditional websites; it extends them. A Zola blog can continue working as a normal static website while also becoming part of an open social web through site.standard.

With Sequoia and wisp.place, a personal blog can combine the simplicity of static hosting with the flexibility of decentralized publishing.