stevedylan.dev
apoena.dev
For your information, I forked your (bloody useful) Sequoia CLI to support multiple use cases:
- I want to publish to my own lexicon, space.litenote.note, where the content is still Markdown but includes specific patterns like
@[youtube]or GitHub notes, so the PWA litenote.space can render enhanced Markdown. - Upload images to create self-contained records in the PDS.
- Add links to other published notes, or remove those links if the notes are still private.
Now, I can simply change a note’s extension to .pub.md, and a GitHub Action, using the forked sequoia cli, publishes it to my PDS. I still need to build an AppView to subscribe to the lexicon and make the content publicly available in the PWA, but the publication part itself is essentially done.
This made me wonder whether the use case “it’s nice to have site.standard.document publication, but I’d also like to publish to other lexicons” would be an interesting addition for the CLI.
Here is the repo https://tangled.org/apoena.dev/sequoia
This is awesome!! 🤯 Love this idea, and glad Sequoia was useful in making it happen!
Adding other lexicon support is a great idea. Definitely something that will take more work. A lot of the CLI is designed around the restraints of standard.site lexicons, so introducing BYOL means we need to rethink how the config is built, how those fields are filled when publishing, etc.
It reminds me of an idea I had a couple of weeks ago, and maybe I could build it into Sequoia in a TUI format. Imagine using lexicon.garden and being able to search for any lexicon. Once you select it, the TUI knows what fields and types need to be filled in order to create the record. Then using that knowledge it presents the form with the types. I did something similar with this project, and I thought about doing this as a web app which didn't make much sense. However if I could somehow put this into a CLI that can be used in other workflows, it gets very interesting... Appreciate this inspo!