I'm still working on it and wondering how best to share the information. Right now I have nearly completed a working development system -- a series of templates and scripts -- that when cloned can be used to create a full web site using only Asciidoctor as the HTML generator and Asciidoctor-pdf for PDF output. A series of shell scripts automates build and publication details to a localhost intranet or to a public internet web site. Themes and css styles are easily managed and selected, and I use the Asciidoctor stylesheet factory styles by default. My site (tomswan.com) is an example product and all pages and articles are written using Asciidoctor and my scripts. I am also using the system to publish my own intranet so I have easy access to my notes and other documents in my office and studio using Dropbox as a cloud go-between for file sharing.
Jekyll and Sphinx are both great pieces of software. If I were a web developer, I would consider using either or both. But I'm not. I'm a writer and a musician, and my system is tailored to be a _writer's_ system, not necessarily a programmer's. Only Asciidoctor, Asciidoctor-pdf and a text editor are required (I use Sublime Text 3). My goal is to have a system that I can use to write articles, code examples (mia <http://tomswan.com/blog/posts/2015-07-10-menus-in-asciidoc.html> is a very early example), book-length manuscripts, and annotated musical scores to accompany my instructional videos as in this article <http://tomswan.com/blog/posts/2016-09-01-transcribing-good-or-evil.html>. Because of the great and capable asciidoctor-pdf program, all of my articles on the site are published in HTML and PDF formats. I don't have to create separate documents for downloading -- the _same_ text generates HTML and PDF outputs. ZIP file creation is also sensibly (I think) designed so that I can write an article, build it, and a ZIP file with examples is created for readers to download. I am exploring epub3 now as a book generator, but products are currently limited to articles and web sites. I considered publishing the system on my own site, but I rejected this for several reasons. One, the programming is evolving rapidly. Two, this is early-stage material, _not_ robust, _not_ thoroughly tested, _strictly DIY!_ If there is enough interest, I'll create a Github package for it and release all files as open source. There are many many kludges -- hand written make files and the like that could and should be automatically generated. Working title is currently "Web Writer 2.0." I agree that a blog package of some kind is essential, and here is where my code is sorely lacking. My own Blog <http://tomswan.com/blog> isn't really a blog, I eventually realized, but more of a list of articles on various subjects. Nothing wrong with that, I guess, but I would like to make it a real blog eventually. What would you and others like to have in such a design? Comments welcome. Thanks. -- Tom On Tuesday, January 3, 2017 at 11:31:59 PM UTC-5, Charles Reynolds wrote: > > > > On Wednesday, March 30, 2016 at 5:05:48 AM UTC-8, Tom Swan wrote: >> >> I recently rewrote my web site www.tomswan.com using almost entirely >> Asciidoctor with very little hand HTML coding and no other 3rd party >> platforms. A lot of the .adoc source code will be available for download as >> soon as I can complete my Asciidoc tutorial as promised on the Programming >> page. -- Tom >> > > Bump. > > Tom, have you any update on this? I'm of a strong mind to do this myself. > Asciidoctor contains (almost) everything I need in a static site builder. > Everything but a blog engine and commenting, that is. I'm pretty sure > everything else can be done pretty much with just asciidoctor. > -- You received this message because you are subscribed to the Google Groups "asciidoc" 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/asciidoc. For more options, visit https://groups.google.com/d/optout.
