hi all !
toying with this idea at the moment, has anyone done this already?
basically have TiddlyWiki as your source of truth for personal and work writing - and then those ready pieces published via a simple pipeline to various sources of your choice
I think this is called POSSE ? (learned about this only yesterday)
A posse possibly. Check whether that definition matches.
As far as publishing is concerned there is more than one type of route.
In simple cases from a TW, URL mediated posting might be the simplest.
Concrete examples might help clarify your aims.
Just a comment
TT
Ok I now understand you are wanting a POSSE (Publish on your Own Site, Syndicate Elsewhere) not a posse (a group of people who have come together for the same purpose).
Reading those docs it looks complicated. Especially with intermediarys.
Is it so complex to pass Tiddler content to another?
Could you give example text source and target?
TT
yeap that one
I’ll see if I can push it to GitHub by the end of the week maybe
started as a wild idea, and now kind of growing into a whole pipeline (with some taxonomy about how such tiddlers are marked in TW and mapped to Hugo etc etc)
but basic premise is the same - you control your sources completely, not any of the big platforms, ultimate source of truth is TW - then your hosted Hugo (or could be Jekyll whatever)
then all the rest, who are getting their version of your precious content (possibly adjusted to match the platform limitation or qwirks etc)
I hope there is a way. This would be amazing to implement.
thanks for encouragement ! definitely is possible yep, of course will require a lot of tweaking and polishing, but I think I have locked in the design / spec more or less
with due level of generalisation (so this should be useful for others with hopefully minimal changes)
at the moment I got side-tracked to kind of related thing - while doing that I realised that my Tiddly Taxonomy is completely out of whack, years of organically creating notes and tags etc will do that yes guilty as charged 
so I am running a quick Taxonomy review - so that whatever structure I put in place for this thing, makes overall sense in relation to other stuff (for example I am also using GSD5 plugin and now my own Subscriptions plugin)
all these things of course should be structured in the best possible way, not to create any structural conflicts, but in fact amplify each other
For some time this was a good strategy. Whatever the repository. In the past I relied on wordpress posts. The key reason is you continue to own the content rather than rely on someone else to store it. Ideally people may visit your source of truth, however be aware if a user subscribes to more than one of the platforms you publish to they may see the same content multiple times. It may be worth curating what appears so people can see your content in different ways, by choosing which platforms to subscribe in.
I think converting all content to a standard within TiddlyWiki then providing the tools to send that content to the different platforms is wise. Allowing some one to install a component for each platform would allow them to install only what they need.
thanks ! yes, there will be of course such duplication and curation and tailoring also to match the target platform specifics
which is all fine by me, the goal for now is to really make sure that the source is not owned by some third-party, which can change rules, or close your account, or shut down something etc
Isn’t this just a matter of creating a custom export format? I used to write blog posts in TW and then export for use in Eleventy. It’s been a while but it worked great. I guess you are talking about something more automated, pushing the content directly?
more like one source format - which will be Markdown
and then converters to various destinations
and yes what I want is a fully automated pipeline - that can be triggered with one script (later on can be even a button but I’d be OK with a script for now)
I’ve been distracted from the TW forum for a little while now, but have long had a plan of using TW as a local source of truth for markdown documents that would then become webpages via hugo or jekyll or something similar, and started working on that with some more seriousness just this last week - and remembered here and thought I should check in with a search. What a timely topic!
I’ve not heard of “POSSE” before, but I like the idea and am keen to see what solutions you come up with.
My aim (and I’ve been tagging some content in my internal this way for some time) is to have content for multiple sites be identified by a tag for the site, and then an “ONLINE” tag to indicate that it’s ready to be published.
I’m using node, so the content can then be trivially picked up from the filesystem and converted using relatively simple scripting outside TW, but I’d be very interested in seeing an in-TW solution, if that’s possible!
(fwiw, done a few individual pages with pandoc (eg: wplace fractals ) but I think hugo will probably be the bigger solution.
I think this would be straightforward to do with some Node code, either against a single-file HTML wiki or a Node one.
But the trouble from a TW perspective is Markdown. If all we want out of our TW is Markdown content like we could have in ten thousand other applications, then all this will work fine. But TW has much more dynamic content than Markdown can handle. So if you have a wiki with lists, filters, macros, procedures, etc. used in displaying your content, it’s all quite a bit more challenging.
thanks for that comment, yes - totally !
but in this case I think I’d be personally fine to have such “publishing” pages in Markdown, for the sake of simplicity to being with
later down the track, this can be extended to full TW syntax, but that is going to be a MUCH bigger scope !
I got slowed down a bit by things, especially the self-inflicted re-org of my wiki taxonomy, should be back on this project soon..
that’s pretty much what I’m doing - restricting myself to md for the pages to be published. The flexibility of full wikitext in the long run though would be great, but my TW is a hybrid of a few things - private notes that should not ever be shared, private brainstormings for ideas that may become public one day, and refined writings that I’m happy to make public.
I did just find this too - though it’s experimental, not been updated in a little over a year, and I’ve not tested it yet - but might be a step towards a wikitext->markdown->{elsewhere} chain?