# Using the LessWrong Editor for a Static Blog

My [personal website](https://www.brendanlong.com/) has been using [a Markdown-based static site generator](https://getpelican.com/) for years, since I wanted something easy (and cheap[^pywbx0tdd7r]) 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](https://www.lesswrong.com/w/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](#Process).

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](https://developers.google.com/search/docs/crawling-indexing/canonicalization)[^7bcgprk9ws5]).

For example, I wrote [this post on LessWrong](https://www.lesswrong.com/posts/mwsLdPoEQBrSEKgRy/cpu-utilization-is-a-lie), then copied it to [my personal site](https://www.brendanlong.com/cpu-utilization-is-a-lie.html), then shared it [on Hacker News](https://news.ycombinator.com/item?id=45110688#45110975), 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](https://www.lesswrong.com/users/brendan-long/edit) (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[^6xy7062v7tl].
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](https://www.lesswrong.com/posts/mLvek6a9G86EnhJqH/30-days-of-retatrutide#Other_Effects) of why I started writing a lot more in the last month or so. Getting [feedback from Justis](https://www.lesswrong.com/posts/bkDrfofLMKFoMGZkE/psa-the-lesswrong-feedback-service) on some of my earlier posts also helped a lot with my confidence.

[^pywbx0tdd7r]: I paid Amazon 56 cents last month to host my website using S3 + CloudFront. 

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

[^6xy7062v7tl]: 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.