1671

LESSWRONG
LW

1670
PracticalSite Meta
Personal Blog

15

Using the LessWrong Editor for a Static Blog

by Brendan Long
5th Sep 2025
2 min read
4

15

15

Using the LessWrong Editor for a Static Blog
8Brendan Long
4Gordon Seidoh Worley
4Brendan Long
4Gordon Seidoh Worley
New Comment
4 comments, sorted by
top scoring
Click to highlight new comments since: Today at 2:28 PM
[-]Brendan Long2mo80

I found another downside to using the LessWrong editor today: It's really easy to publish drafts by accident, and if you move them back to draft, you're stuck with the original publish date (like with this post that I un-published and then re-published).

Reply
[-]Gordon Seidoh Worley2mo40

Interesting, I've actually gone in the opposite direction.

I now write posts in a Google doc first, then I copy that over to where I'm going to post that (either Substack, which then gets imported to LessWrong, or LessWrong directly).

Reasons for doing that:

  • better offline editing support
  • more easily able to deal with the same document on multiple devices
  • better at catching grammar and spelling errors

Plus then I have an extra backup should anything happen to LessWrong or Substack.

Reply
[-]Brendan Long2mo40

I'm not sure why I didn't do this before, but I just tried and I don't like it quite as much:

  • Footnotes don't transfer.
  • Images aren't allowed in footnotes.
  • You can't add nice captions to images.
  • It's a bit overkill for what I want. Since my main output is Markdown, any feature that doesn't transfer to Markdown just adds complexity to the editor and gets in my way.

I was pleasantly surprised that copying images from Google Docs works though.

I imagine for people with more general posting goals this would be a good idea, but since the only two outputs I care about are LessWrong and Markdown, using the LessWrong editor works better for me.

I don't need a backup on Google Docs since I use my personal site for that (the content is all on GitHub + several of my computers).

Better spellcheck would be nice, but I just run my posts through an AI before posting and it seems to work pretty well.

Reply
[-]Gordon Seidoh Worley1mo40

Ah, right. I'm opposed to footnotes, so I don't use them, and I rarely use image captions, preferring to address any images directly in the text. Those would change the calculus, though, if I wanted them.

Reply
Moderation Log
More from Brendan Long
View more
Curated and popular this week
4Comments
PracticalSite Meta
Personal Blog

My personal website has been using a Markdown-based static site generator for years, since I wanted something easy (and cheap[1]) and wanted to ensure that I wasn't tied to any particular piece of software. The one downside is that I have to write files into a git repo, so it's pretty hard to write posts when I'm not at my computer, and the trivial inconvenience prevents me from writing as much as I want.

LessWrong Editor

Enter: The LessWrong editor. This has several features that have helped me write a lot more on my phone:

  • I can access the editor from anywhere.
  • I can quickly change formatting and see how it looks.
  • When I'm happy with a post, I can copy the content to my personal site.

Being able to drag-and-drop images is really nice when editing on a computer, although I can't seem to get the ¶ symbol menu to work on my phone, so I do need to go on my computer to finish images. Having a post completely planned out still makes that much easier.

It's also nice that I can post to LessWrong, then do the conversion when I get around to it, including retroactively turning a post into a linkpost (for the canonical URL cred[2]).

For example, I wrote this post on LessWrong, then copied it to my personal site, then shared it on Hacker News, and I likely wouldn't have done either of the later things if I didn't have a nice editor to make the first version.

Process

  1. Write the post on LessWrong using the "LessWrong Docs" editor and post it.
  2. At some point, open the post in an editor and convert it from lessWrong Docs to Markdown (don't save since this is lossy).
    • You may need to Activate Markdown in the settings (under "Site Customizations"). Annoyingly, enabling Markdown makes it the default for all posts and comments, but you can manually change them back to LessWrong Docs.
  3. Copy the Markdown into my static site's git repo.
  4. Copy the images.
  5. Add the appropriate metadata (title, date, preview image, link to LessWrong).
  6. Do some other cleanup[3].
  7. Post on my site.
  8. Edit the LessWrong post again and turn it into a link post to my site.

 

So, thanks for the Lightcone team for making such a nice editor and letting me abuse the site's tooling like this. I credit this for at least half of why I started writing a lot more in the last month or so. Getting feedback from Justis on some of my earlier posts also helped a lot with my confidence.

  1. ^

    I paid Amazon 56 cents last month to host my website using S3 + CloudFront.

  2. ^

    Although looking at the source for this article, it looks like LessWrong doesn't set canonical URL's for link posts correctly?

  3. ^

    This process is still kind-of annoying, since Markdown doesn't have a way to say that an image is a caption, so I have to re-style captions on my site; plus I don't want to hotlink all of the images so I have to add them to my site and change the links.

    Finding the motivation to convert an already-successful post is much easier than finding the motivation to write a post from scratch though.