Daniel Rodríguez Rivero already has a tool to do this on GitHub called Octowiki <https://github.com/OctoWiki/octowiki.github.io>. I haven't personally used his Octowiki tool to edit TWs on GitHub, but you can click the GitHub link I just provided to give it a look.
He also has a lot of TW stuff on his personal GitHub site too. -Doug On Saturday, March 18, 2017 at 2:30:23 PM UTC-5, Thomas Elmiger wrote: > > Hi all > > Today I found some stuff via Twitter that could be of interest for > publishing TW stuff from Github directly. > > Smashing Magazine published a betaversion of their new website and they > are going very innovative ways using netlify and Hugo amongst many other > things: > > > https://next.smashingmagazine.com/2017/03/a-little-surprise-is-waiting-for-you-here--meet-the-next-smashing-magazine/ > > > To understand netlify and it's philosophy I found the video here helpful: > https://www.netlifycms.org/docs/intro/ > > I could imagine using TW as a CMS instead of their react-based app but I > have no idea how difficult it would be to adapt parts of their system to > process tid files and wikitext instead of markdown … I found it very > interesting nonetheless. > > Have a nice weekend! > Thomas > > === Extract: > > We are moving to a JAMstack: articles published directly to Netlify CDNs, > with a custom shop based on an open-sourced headless E-Commerce GoCommerce > and a job board that’s all just static HTML; content editing with Netlify’s > new open-source, Git-Based CMS, real-time search powered by Algolia, full > HTTP/2 support, and the whole website running as a progressive web app with > a service worker in the background (thanks to the awesome Service Worker > Toolbox library). Booo-yah! > > How does it work? Quite simple, actually. Content is stored in Markdown > files. HTML is pre-baked using the static site generator Hugo, combined > with a modern asset pipeline built with Gulp and webpack, all based on the > Victor Hugo boilerplate. > > We’ve spiced it all up with a handful of fancy APIs, including ones by > Stripe for payments, Algolia for search, Cloudinary for responsive images, > and Netlify’s open-source APIs GoCommerce (a headless e-commerce API), > GoTrue for authentication, and GoTell for our more than 150,000 comments. > -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/875b9e8a-a644-4d64-a649-a5ab62468c5f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
