On Mon, 2016-09-05 at 09:51 +0000, Ian Clarke wrote: > On Mon, Sep 5, 2016 2:19 AM, Florent Daigniere nextgens@freenetprojec > t.org > wrote: > On Sun, 2016-09-04 at 18:25 +0000, Ian Clarke wrote: > > > > > After that, I have identified a number of coders who can take these > > > > > files, > > > > > convert to HTML, and then publish them on Github using https://jeky > > ll > > > > > rb.com/. > > > > > Any particular reason for that ruby-based tool? We're using python > > everywhere else... > > > > > Yes, because from my research it is the best known and most widely > used tool of > its type, particularly where Github is concerned. My understanding > is that no > prior knowledge of Ruby is required to use Jekyll. > > > What about what we're currently using? > or Pelican (http://blog.getpelican.com/)? > > > > > Are these tools as widely used and as powerful as Jekyll?
I think so. Generating static HTML isn't rocket-science and both Pelican and Jekyll have way too many bells and whistles... We need something that turns MarkDown into templated/themed HTML; nothing else. > Briefly looking at > upwork.com (a good site for finding coders for small projects) there > seems to be > a lot more people with Jekyll experience than Pelican experience. > Doing the templating is (hopefully) a one-off job... that we will pay and get done... as opposed to running the toolkit which we will have to do for every single deployment. My understanding of github pages is that it will neither install nor run ruby/bundler/jekyll ... so to me, it does make sense to standardize on a toolkit that the release managers have and are familiar with. An alternative would be to deploy CI tools along github-pages; that will do all of the above for us (at which point I don't care about the language or technology picked)... but that needs to be budgeted for too. Florent
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Devl mailing list [email protected] https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
