apoena.dev
forked from
stevedylan.dev/sequoia
A CLI for publishing standard.site documents to ATProto
chore: adjust blog post
authored by
+3
-4
docs/docs/pages/blog/introducing-sequoia.mdx
+3
-4
docs/docs/pages/blog/introducing-sequoia.mdx
···
24
24
25
25
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. It 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:
26
26
27
-
<div class="relative w-full" style={{paddingBottom: "73.17%"}}>
28
27
<iframe
29
-
class="absolute left-0 top-0 h-full w-full"
28
+
class="w-full"
29
+
style={{aspectRatio: "16/9"}}
30
30
src="https://www.youtube.com/embed/sxursUHq5kw"
31
31
title="YouTube video player"
32
32
frameborder="0"
33
-
allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
33
+
allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
34
34
referrerpolicy="strict-origin-when-cross-origin"
35
35
allowfullscreen
36
36
></iframe>
37
-
</div>
38
37
39
38
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 more. No more walled gardens, full control of our data, and connected through lexicons.
40
39