convert Markdown post to Gempost

This commit is contained in:
jbowdre 2024-04-14 00:25:06 +00:00 committed by github-actions[bot]
parent 36761b5621
commit de5a2ef099
3 changed files with 33 additions and 12 deletions

View file

@ -0,0 +1,17 @@
I [posted *almost* a month ago](https://scribbles.jbowdre.lol/post/parking-scribbles-for-now-t9dty3yh) that I was pausing my Scribblesing while I focused on further adventures in Geminispace[1]. But then Robb Knight[2] went and released the much-anticipated EchoFeed[3], and I thought it might be fun to see if I could feed my Gemini capsule[4] from Scribbles.
=> https://geminiprotocol.net/ 1: Geminispace
=> https://robb.omg.lol/ 2: Robb Knight
=> https://echofeed.app 3: EchoFeed
=> https://capsule.jbowdre.lol 4: Gemini capsule
After tinkering with it quite a bit today, I think I've got a working (if not particularly elegant) solution.
Now, when EchoFeed sees a new post on my Scribbles feed, it copies the post to a Markdown file in the GitHub repo[1] I use for my capsule. A GitHub Actions workflow is triggered by the creation of that new Markdown file and converts it to the Gemtext format, complete with a YAML sidecar to hold metadata for gempost[2], a static site generator for Gemini. And then the creation of *that* file triggers another workflow which uses gempost to build the site and then push it to my server.
=> https://github.com/jbowdre/capsule 1: GitHub repo
=> https://github.com/justlark/gempost 2: gempost
Now I get to check out all the cool new stuff Vincent has been adding to Scribbles[1] while still maintaining a presence on the altweb. Very exciting!
=> https://scribbles.page/updates 1: cool new stuff Vincent has been adding to Scribbles

View file

@ -0,0 +1,4 @@
id: "urn:uuid:dced2ea6-2872-48d6-b97c-5e5350d588ee"
title: "From Scribbles to Gemini, with EchoFeed"
published: "2024-04-14T00:23:30.000000Z"
updated: "2024-04-14T00:23:30.000000Z"

View file

@ -1,13 +1,13 @@
--- ---
title: "From Scribbles to Gemini, with EchoFeed" title: "From Scribbles to Gemini, with EchoFeed"
published: "2024-04-14T00:23:30.000000Z" published: "2024-04-14T00:23:30.000000Z"
updated: "2024-04-14T00:23:30.000000Z" updated: "2024-04-14T00:23:30.000000Z"
--- ---
I [posted *almost* a month ago](https://scribbles.jbowdre.lol/post/parking-scribbles-for-now-t9dty3yh) that I was pausing my Scribblesing while I focused on further adventures in [Geminispace](https://geminiprotocol.net/). But then [Robb Knight](https://robb.omg.lol/) went and released the much-anticipated [EchoFeed](https://echofeed.app), and I thought it might be fun to see if I could feed my [Gemini capsule](https://capsule.jbowdre.lol) from Scribbles. I [posted *almost* a month ago](https://scribbles.jbowdre.lol/post/parking-scribbles-for-now-t9dty3yh) that I was pausing my Scribblesing while I focused on further adventures in [Geminispace](https://geminiprotocol.net/). But then [Robb Knight](https://robb.omg.lol/) went and released the much-anticipated [EchoFeed](https://echofeed.app), and I thought it might be fun to see if I could feed my [Gemini capsule](https://capsule.jbowdre.lol) from Scribbles.
After tinkering with it quite a bit today, I think I've got a working (if not particularly elegant) solution. After tinkering with it quite a bit today, I think I've got a working (if not particularly elegant) solution.
Now, when EchoFeed sees a new post on my Scribbles feed, it copies the post to a Markdown file in the [GitHub repo](https://github.com/jbowdre/capsule) I use for my capsule. A GitHub Actions workflow is triggered by the creation of that new Markdown file and converts it to the Gemtext format, complete with a YAML sidecar to hold metadata for [gempost](https://github.com/justlark/gempost), a static site generator for Gemini. And then the creation of *that* file triggers another workflow which uses gempost to build the site and then push it to my server. Now, when EchoFeed sees a new post on my Scribbles feed, it copies the post to a Markdown file in the [GitHub repo](https://github.com/jbowdre/capsule) I use for my capsule. A GitHub Actions workflow is triggered by the creation of that new Markdown file and converts it to the Gemtext format, complete with a YAML sidecar to hold metadata for [gempost](https://github.com/justlark/gempost), a static site generator for Gemini. And then the creation of *that* file triggers another workflow which uses gempost to build the site and then push it to my server.
Now I get to check out all the [cool new stuff Vincent has been adding to Scribbles](https://scribbles.page/updates) while still maintaining a presence on the altweb. Very exciting! Now I get to check out all the [cool new stuff Vincent has been adding to Scribbles](https://scribbles.page/updates) while still maintaining a presence on the altweb. Very exciting!