On 12/12/20 3:22 PM, Bj?rn W?rmedal wrote: > I?m curious about how authors structure their workflows in geminispace. The thing I've worked out so far for myself is based on the use of a content management system called Logarion (written in Ocaml by Orbifx). I first run it to create a new document based on a title I give. Once the file is made I edit it locally with nano, basically in Gemini format minus Logarion's header. (The documents are meant to be in Markdown, but Gemini is like a subset of that anyway.) When the document is written and marked for publication in its header, I run a script which calls Logarion to export them to GMI along with an index listing ordered by date (date.gmi) that Logarion itself provides. The script then copies the generated content into a directory on my server, and as such it is published. I've been thinking about devising a minimalist alternative to this workflow because it's a little bit overkill for what I'm doing. My thought is that the least a Gemini site or log requires is:
---
Previous in thread (2 of 14): 🗣️ Nico (nico (a) itwont.work)
Next in thread (4 of 14): 🗣️ julien (a) typed-hole.org (julien (a) typed-hole.org)