I was excited to work with LeanPub again (now that I have a starting point for my new book) but they only support git integration with Github and Bitbucket...

boo

ironically you can get a book about Gitlab on LeanPub, but you can't use Gitlab to author one 😂

@jjg Surely you can author your book on Gitbook and keep that git repo in sync on Gitlab though?

@h possibly, but I don't want any trace of my on Github.

Honestly after rooting-around in all that I decided that I need to find something else. I really liked Leanpub a couple years ago but we've both changed and we're just not in love anymore 😂

@jjg Leanpub quit calling you all of a sudden? :-)
Anyway, I didn't know that Gitbook was Github-dependent, I must have missed that.
But I think I saw a little FLOSSy one that can be self-hosted too. I'll take a look, I'm needing something like that too.

@h I'm sorry, I conflated Leanpub with Gitbook, Gitbook looks neat :)

This project will need to result in physical books as well as e-books so I need to keep that in mind when I look at publishing options. For now I'm just going to write using basic Markdown and push to a private repo, but if you come across anything cool let me know :)

@jjg I don't know if the Gitbook source published here is enough to self-host everything, or whether that depends on functionality available exclusively through gitbook.com
Worth taking a look.

https://github.com/GitbookIO/gitbook

@h @jjg I think a number of us want/need a git-ish repository for prose. Maybe we should, you know, cooperate.

@Steve @jjg I'll explore the potential to port asciidoctor to #golang, which woud be useful for my own purposes, and see where it leads from there.

@h @jjg It's amusing that you mention Leanpub, because I also had a frustrating experience there, and my local workflow largely replicates the better aspects I found there.

@jjg @h I may have mentioned this long ago, but the best option I've seen is gitit, which is git on the back end, and a wiki on the front end.

@Steve @jjg Is this the one we discussed once, written in Haskell?

@jjg @Steve I mean, not that the language is too important if you just want to write and forget about the tool specifics. In my particular case that kinda matters though, because I would be bundling the documentation tool with something else, and the smaller the dependency set the better.

If I have to deliver and maintain Python, Ruby, or Haskell things, that dramatically increases the complexity of things for a one-man show (at this time).

@h @jjg If there was a gitit instance running somewhere, could you code something to interact with the git back end, independent of the wiki portion? If so, it's no longer an either/or question.

I suppose all we really need is a gitlab instance running on social.coop to get started. People could choose their own interface.

@Steve @jjg Probably not suitable for social.coop at this time, in the middle of major web hosting and sysadmin shuffling.
But maybe an offspring that can later be integrated when everybody is on the same page?

#SocialCoop