diff --git a/src/routes/_posts/imagining-a-passwordless-future.svx b/src/routes/_posts/imagining-a-passwordless-future.svx
index 1f1d276..f77a9d6 100644
--- a/src/routes/_posts/imagining-a-passwordless-future.svx
+++ b/src/routes/_posts/imagining-a-passwordless-future.svx
@@ -3,6 +3,7 @@ title: Imagining A Passwordless Future
 description: Can we replace passwords with something more user-friendly?
 date: 2021-04-30
 draft: true
+dropcap: false
 ---
 <script>
     import Sidenote from '$lib/Sidenote.svelte';
diff --git a/src/routes/_posts/vue-vs-svelte.svx b/src/routes/_posts/vue-vs-svelte.svx
index ba16609..b19dd62 100644
--- a/src/routes/_posts/vue-vs-svelte.svx
+++ b/src/routes/_posts/vue-vs-svelte.svx
@@ -2,15 +2,13 @@
 title: Thoughts on Vue vs Svelte
 description: They're more similar than they are different, but they say the most bitter enemies are those who have the fewest differences.
 date: 2023-06-29
-draft: true
 ---
 <script>
-    import Dropcap from '$lib/Dropcap.svelte';
     import Sidenote from '$lib/Sidenote.svelte';
 </script>
 
 
-<Dropcap word="Recently">I've had a chance to get to know Vue a bit. Since my frontend framework of choice has previously been Svelte (this blog is built in Svelte, for instance) I was naturally interested in how they compared.</Dropcap>
+Recently I've had a chance to get to know Vue a bit. Since my frontend framework of choice has previously been Svelte (this blog is built in Svelte, for instance) I was naturally interested in how they compared.
 
 Of course, this is only possible because Vue and Svelte are really much more similar than they are different. Even among frontend frameworks, they share a lot of the same basic ideas and high-level concepts, which means that we get to dive right into the nitpicky details and have fun debating `bind:attr={value}` versus `:attr="value"`. In the meantime, a lot of the building blocks are basically the same or at least have equivalents, such as:
 * Single-file components with separate sections for markup, style, and logic
@@ -54,7 +52,7 @@ While Svelte takes the more common approach of wrapping bits of markup in its ow
 </div>
 ```
 
-While Vue's approach may be a tad unorthodox, I find that I actually prefer it in practice. It has the killer feature that, by embedding itself inside the existing HTML, it doesn't mess with my indentation - which is something that has always bugged me about Mustache, Liquid, Jinja, etc.<Sidenote>Maybe it's silly of me to spend time worrying about something so trivial, but hey, this whole post is one big bikeshed anyway.</Sidenote>
+While Vue's approach may be a tad unorthodox, I find that I actually prefer it in practice. It has the killer feature that, by embedding itself inside the existing HTML, it doesn't mess with my indentation - which is something that has always bugged me about Mustache, Liquid, Jinja, etc.<Sidenote>Maybe it's silly of me to spend time worrying<Sidenote>Nested<Sidenote>Doubly-nested sidenote!</Sidenote> sidenote!</Sidenote> about something so trivial,<Sidenote>Second nested sidenote.</Sidenote>  but hey, this whole post is one big bikeshed anyway.</Sidenote>
 
 Additionally (and Vue cites this as the primary advantage of its style, I think) the fact that Vue's custom attributes are all syntactically valid HTML means that you can actually embed Vue templates directly into your page source. Then, when you mount your app to an element containing Vue code, it will automatically figure out what to do with it.<Sidenote>AlpineJS also works this way, but this is the *only* way that it works - it doesn't have an equivalent for Vue's full-fat "app mode" as it were.</Sidenote> This strikes me as a fantastic way to ease the transition between "oh I just need a tiny bit of interactivity on this page, so I'll just sprinkle in some inline components" and "whoops it got kind of complex, guess I have to factor this out into its own app with a build step and all now."