![]() ![]() You can paste content into it and it will clean it up to fit the subset of HTML that Substack supports. ![]() The Substack compose editor incorporates a well built rich-text editor. but what about getting data in? I don’t want to manually assemble a newsletter from all of these different sources of data. They do offer an RSS feed of each newsletter though-add /feed to the newsletter subdomain to get it. Substack doesn’t yet offer an API, and have no public plans to do so. I’m including the full HTML for everything: people don’t need to click through back to my blog to read it, all of the content should be right there in their email client. The blogmarks and quotations come in chronological order afterwards. I include the entries first in reverse chronological order, since usually the entry I’ve just written is the one I want to use for the email subject. My newsletter consists of all of the new entries, blogmarks and quotations since I last sent it out. You can see them defined in models.py in my blog’s open source repo. These live in a PostgreSQL database managed by Django. “Blogmarks” is a name I came up with for bookmarks in 2003.īlogmarks and quotations show up in my blog’s sidebar, entries get the main column-but on mobile the three are combined into a single flow. My blog has three types of content: entries, blogmarks and quotations. I’ve mostly automated that, using an Observable Notebook to generate the HTML. I recently started sending out a weekly-ish email newsletter consisting of content from my blog. Semi-automating a Substack newsletter with an Observable notebook ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |