00:00:06 <Aeyoun> xjjk: hi 00:00:19 <xjjk> Aeyoun: greetings! 00:00:28 <Aeyoun> xjjk: I was just about to go to bed (I’ in CET). 00:00:44 <Aeyoun> xjjk: you wanted some theming tips, right? 00:00:48 <xjjk> yes 00:01:16 <Aeyoun> xjjk: <p class="readtime" title="Estimated time to read at 220 words per minute">${post.reading_time} min to read</p> 00:01:17 <xjjk> e.g. https://www.aeyoun.com/posts/2015-drmday-drm-in-my-life.html… the title is the dark green part on that page 00:01:33 <xjjk> what's the light green? are you rendering the description tag in your theme? 00:01:55 <xjjk> Aeyoun: ah… where is reading_time coming from? 00:02:04 <xjjk> I tried to write a plugin that did that myself, but didn't get anywhere 00:02:17 <xjjk> are you calculating that manually for each post as metadata? 00:02:20 <Aeyoun> xjjk: this is my my post_header.tmpl override: 00:02:31 <Aeyoun> https://www.irccloud.com/pastebin/ybQ0rzec 00:02:48 <xjjk> ah 00:04:01 <Aeyoun> xjjk: I manually add a description meta data to each post. because SEO. later found out my bounce rate dropped from ~30% to ~2% once I started showing the description underneath the main title. (bounce rate being people-from-search-who-immediately-leave-the-page) 00:04:42 <xjjk> Aeyoun: wow 00:05:02 <xjjk> adding such a thing has been on my list of things to do for a while 00:05:08 -travis-ci:#nikola- getnikola/nikola#4924 (smarter-CDN - d33c568 : Roberto Alsina): The build is still failing. 00:05:09 -travis-ci:#nikola- Change view: https://github.com/getnikola/nikola/compare/39ea3b67b000...d33c568b785e 00:05:09 -travis-ci:#nikola- Build details: http://travis-ci.org/getnikola/nikola/builds/61699807 00:05:24 <Aeyoun> I wrote good descriptions, but people didn’t see the description when they got to the page. so they didn’t recognize it as the same page/content. that is my theory, at least. 00:05:27 <xjjk> at minimum, for a description that was sharable on social media 00:05:31 <xjjk> right 00:05:54 <Aeyoun> xjjk: the description is already included in OpenGraph and Twitter cards. assuming you use the base theme or something inheriting from it. 00:06:26 <xjjk> how were you calculating reading_time? 00:06:38 -travis-ci:#nikola- getnikola/nikola#4923 (smarter-CDN - 39ea3b6 : Roberto Alsina): The build is still failing. 00:06:39 -travis-ci:#nikola- Change view: https://github.com/getnikola/nikola/compare/2f5743bd4d18...39ea3b67b000 00:06:39 -travis-ci:#nikola- Build details: http://travis-ci.org/getnikola/nikola/builds/61699074 00:06:39 <Aeyoun> xjjk: what do you think about the "newest posts" thing at the bottom? added it earlier today. (you may have to reload because caching). https://www.aeyoun.com/posts/lenovo-yoga3-pro-review.html#footer 00:06:44 <Aeyoun> xjjk: <p class="readtime" title="Estimated time to read at 220 words per minute">${post.reading_time} min to read</p> 00:07:01 <xjjk> where does reading_time come from? 00:07:06 <Aeyoun> xjjk: it’s already baked in to Nikola. 00:07:09 <xjjk> post.reading_time 00:07:11 <xjjk> ohhh 00:07:19 <Aeyoun> xjjk: added it some time back 00:07:22 <xjjk> ah 00:07:41 <Aeyoun> https://github.com/getnikola/nikola/blob/master/nikola/post.py#L616 00:07:49 <xjjk> yah, I see it now 00:08:22 <xjjk> Aeyoun: I like the newest posts block! 00:09:01 <Aeyoun> xjjk: reading time is by default only suggested used here, https://github.com/getnikola/nikola/blob/master/nikola/conf.py.in#L542-L557 — but is available in global scope for theming if you want it. 00:09:17 <xjjk> reading_time isn't exposed in any of the default themes is it? never noticed it's apparently been there since 2013 00:09:57 <Aeyoun> xjjk: as I just said, RSS config example is only place that use it. (where its most useful, frankly — proises readers that there is actually more content) 00:10:39 <xjjk> I see 00:10:44 <Aeyoun> xjjk: https://www.aeyoun.com/assets/js/newposts.js ;) You need GENERATE_ATOM = True (since Nikola 7.4) and probably customize the class-names and variables. No need to rebuild pages every time you have a new post. 00:11:18 <xjjk> Aeyoun: I see, done w/ AJAX 00:11:35 <xjjk> would be a lot shorter w/ jQuery, haha 00:12:06 <Aeyoun> xjjk: yeah but I don’t use any jQuery. (nether do most developers who depend on that giant library) 00:12:23 <Aeyoun> Doesn’t work in every old browser out there, but the theme will adopt and show a bigger ad instead. :D 00:12:39 <xjjk> I'm waiting for Bootstrap to support Zepto 00:13:13 <Aeyoun> I think bootstrap and jquery is adding more complexity and overhead than benefits. 00:13:37 <Aeyoun> especially considering that you load giant libraries form which you only use a few functions. 00:13:56 <Aeyoun> Things should be lean and only include as much code as they need to. 00:14:00 <xjjk> I've been hacking onto the default theme, but have been procrastinating writing a new one from scratch w/ a slimmer library footprint 00:14:18 <xjjk> though mainly I just want something that looks better 00:14:32 * Aeyoun used to work for a browser vendor, and users were constantly complaining about memory and such to *us* and not the stupid sites who loaded three version of jquery 00:14:43 <xjjk> haha, right 00:15:00 <Aeyoun> xjjk: switch to the base theme and start by writing files/assets/css/custom.css. 00:15:08 <xjjk> yeah, done that 00:15:24 <xjjk> http://blog.samat.org/ 00:15:34 <xjjk> mostly, at this point, a lot of silly animations 00:15:40 <Aeyoun> … 00:15:42 <xjjk> is the extent of customization done 00:15:50 <Aeyoun> xjjk: animations should only come as a direct response to user action. 00:16:00 * Aeyoun was an interaction designer at some point too :P 00:16:13 <xjjk> the page having loaded is a user interaction, I'll argue 00:17:03 <Aeyoun> No. To the user, the page should already have loaded. Anything to slow it down is an annoyance. ;) 00:17:28 <Aeyoun> xjjk: you need some :hover on these tags, http://blog.samat.org/tag/ :) 00:17:46 <xjjk> yeah, I wanted to turn that into a tag cloud at some point 00:17:57 <xjjk> ralsina_: I think you mentioned ages ago at having a theme contest 00:18:05 <ralsina_> yepp 00:18:09 <ralsina_> never got around to it 00:18:11 <Aeyoun> xjjk: you haven’t made it any better by animating different things in different direction at the same time. :P hehe. 00:18:26 <xjjk> Aeyoun: different directions? which page? 00:18:36 <xjjk> or do you mean the navbar + content coming from different directions 00:18:58 <Aeyoun> xjjk: I was referring to that, yeah. 00:19:07 <xjjk> I was planning on reversing that actually, thanks for noticing 00:20:26 <Aeyoun> xjjk: tracking readership in any way? 00:20:40 <xjjk> Aeyoun: other than Google Analytics, no 00:20:48 <Aeyoun> that is a yes, then 00:20:51 <xjjk> I have a lot of out-dated content 00:21:03 <ralsina_> xjjk: there is a "bricks" class somewhere which looks nicer than that 00:21:22 <xjjk> so until I can get myself writing more (probably via making stuff look a little bit more appealing to me) I'm not focused on actively tracking it 00:21:27 <xjjk> ralsina_: "bricks" class? 00:21:31 <ralsina_> yes 00:21:34 <ralsina_> IIRC 00:21:51 <Aeyoun> xjjk: you see your front-page? compare that to mine. had one like your’s. started recycling things with multi-column (pushed things down and then back to the top in the second column). man, did that increase the number of pageviews per session and per unique user. ;) 00:22:19 <Aeyoun> multi-column layout 101: https://www.irccloud.com/pastebin/14DunTID 00:22:43 <xjjk> Aeyoun: learning flexbox has been on my TODO list, haha 00:22:48 <xjjk> Aeyoun: wow, simple… 00:23:14 <xjjk> ralsina_: sorry, what do you mean by bricks? 00:23:39 <Aeyoun> xjjk: don’t learn flexbox. not yet.you’ll be tempted to use it everywhere and it’s not well adopted enough. sorry. :( its hard to progressively enhance a layout with flexbox as its an entirely different layout thinking. 00:24:03 <ralsina_> xjjk: I see your tags page. There was, IIRC a bricks class in the stylesheet that looked somewhat nicer, that's all 00:24:10 <xjjk> ralsina_: ahh 00:24:19 <xjjk> it's whatever is default in bootstrap3-jinja 00:25:09 <Aeyoun> ralsina_: was there a bug about configurable themes? we talked colors and fonts earlier. this week. 00:25:20 <ralsina_> Aeyoun: no bug 00:25:29 <Aeyoun> uhm, I talked at least. can’t remember if I were talking to myself or not. :P that happens. 00:26:31 <Aeyoun> xjjk: by the by, drop the old raspberry. get yourself a nice pi 2 and drop raspbian. so nice with a pi 2 to use *actual debian* instead of raspbian. so much better with the mirrors and package availability, security updates, and more. 00:27:20 <xjjk> Aeyoun: haha I'm using it for a company project, it's what we've unfortunately settled on before the rpi2 was ever announced 00:27:54 <ralsina_> Aeyoun: I can confirm you talked to me :) 00:28:34 <Aeyoun> ralsina_: making a bug now 00:28:48 <ralsina_> This smarter-CDN branch is going to be *so* neat 00:28:54 <ralsina_> much better than what we have now 00:28:59 <xjjk> ralsina_: saw those commits… what does it do exactly? 00:29:05 <ralsina_> Aeyoun: I can confirm you talked to me :) 00:29:32 <ralsina_> xjjk: currently, the theme author has to handle 4 cases in its templates: 00:29:52 <xjjk> with bundling? 00:29:53 <ralsina_> 1) CDN + webassets 2) CDN - webassets 3) and 4) the other two combos 00:30:05 <ralsina_> This branch makes it so you just handle 2 00:30:11 <xjjk> ah 00:30:21 <ralsina_> And I *think* I can bring it down to just one and doo the right thing 00:30:47 <ralsina_> So, give a list of things you want, and it will use CDN or not and bundle or not and you will have the right code in the page 00:31:01 <xjjk> ah 00:31:17 <xjjk> how much of that logic will need to be in the theme? 00:31:30 <ralsina_> Not any 00:31:51 <ralsina_> the template author will have to describe CSS/JS in a sort of DSL 00:32:27 <ralsina_> like: all.js=bootstrap::js/bootstrap.min.js 00:32:52 <ralsina_> or maybe all.js=bootstrap::js/bootstrap.min.js::3.3.4 if he wants a specific version 00:33:05 <xjjk> I'm assuming the first term is a canonical name for the CDN? 00:33:09 <xjjk> e.g. 'bootstrap' 00:33:12 <ralsina_> yes, from cdnjs 00:33:33 <ralsina_> sort of a debian package::filename::version thing 00:34:12 <ralsina_> And then he can put links_for_bundle(all.js) in the template and the right links will appear 00:34:29 <xjjk> I see 00:34:45 <ralsina_> I still have not figured out how to handle falling back to non-cdn versions right, but it should be possible 00:38:36 <Aeyoun> Is GitHub bot sleepy? 00:38:47 <Aeyoun> https://github.com/getnikola/nikola/issues/1701 – Configurable themes 00:39:06 <ralsina_> got the email 00:41:40 -GitHub[nikola]:#nikola- [nikola] ralsina pushed 2 new commits to smarter-CDN: http://git.io/vUfiW 00:41:40 -GitHub[nikola]:#nikola- nikola/smarter-CDN bfab0d0 Roberto Alsina: fixx template bug 00:41:40 -GitHub[nikola]:#nikola- nikola/smarter-CDN 5e67fbd Roberto Alsina: don't scrape 00:45:13 * Aeyoun is off to bed 00:50:34 -GitHub[nikola]:#nikola- [nikola] ralsina pushed 1 new commit to smarter-CDN: http://git.io/vUfXC 00:50:34 -GitHub[nikola]:#nikola- nikola/smarter-CDN e5fd165 Roberto Alsina: bundle-description DSL 01:06:32 -travis-ci:#nikola- getnikola/nikola#4928 (smarter-CDN - e5fd165 : Roberto Alsina): The build is still failing. 01:06:33 -travis-ci:#nikola- Change view: https://github.com/getnikola/nikola/compare/5e67fbd65298...e5fd165e22d8 01:06:33 -travis-ci:#nikola- Build details: http://travis-ci.org/getnikola/nikola/builds/61704157 08:56:55 <gour> morning 08:57:30 <gour> manual lists 'Client-side cloud tags', so i wonder what id needed to create them? some tweaking with the template(s)? 12:44:53 <Aeyoun> ChrisWarrick: is https://irclogs.getnikola.com/ on github? should have links on front-page to "today’s log". maybe yday and "this month" as well. at least, I go there to look at today or yday’s logs. every other visit is probably coming from the goog’. 12:45:48 <ralsina_> gour: the server provides a json, the client uses JS to fetch it and render it as it wants 12:46:25 <gour> ralsina_: ahh, that's nifty 12:46:42 <ralsina_> We should create more json for client-side to render, in general 12:46:57 <ralsina_> there's for example, a moustache plugin that does the whole page rendering client side 12:47:07 <ralsina_> Galleries should be totally client side JS 12:48:04 <Aeyoun> ralsina_: why isn’t galleries a plug-in? I don’t use it personally. I saw you raised this issue about moving thins out of nikola and into plugins. 12:51:54 <ralsina_> Aeyoun: it is a plugin 12:52:01 <ralsina_> Aeyoun: it just is shipped in core 12:52:42 <Aeyoun> ralsina_: is it used much? 12:52:58 <ralsina_> well, it was one of the main features at the beginning :-) 12:53:04 <ralsina_> AFAIK yes, lots of sites use it 12:53:27 <ralsina_> I think it should share more code with the new images/ stuff too 12:54:01 <Aeyoun> JSON output, https://github.com/getnikola/nikola/issues/1702 – https://github.com/getnikola/nikola/issues/1703 12:54:10 <ralsina_> OTOH the last refactor of it almost made me quit the project because it's incredibly convoluted stuff 12:54:48 <ralsina_> https://github.com/getnikola/nikola/issues?utf8=%E2%9C%93&q=pustule 13:16:33 <gour> how should look 'preamble' of asciidoc post? 13:17:29 <ralsina_> gour: create a asciidoc post using new_post ... like that :-) 13:17:36 <ralsina_> unless it doesn t work, of ourse 13:18:00 <gour> ralsina_: i got it...i thought there is something like '-f asciidoc' :-) 13:18:16 <ralsina_> yes, nikola new_post -f asciidoc 13:18:56 <gour> Exception: Unknown format asciidoc 13:19:12 <gour> it works by using reST header 13:19:32 <gour> you wrote that plugin, but i bet you prefer rst? 13:21:28 <gour> http://paste.opensuse.org/22561797 13:33:46 <ChrisWarrick> gour: unknown format asciidoc? should not happen unless you failed to enable the compiler in COMPILERS 13:52:28 <ChrisWarrick> Aeyoun: no, this page is hosted on my own server without any source sharing. It’s just a simple site with almost no customizations. I guess I could add some links there 14:00:32 * ralsina_ wonders if we could check if a compiler for a format is available and make that error more informative 14:01:25 <ralsina_> Maybe even just "make it work" as long as there's no conflict with extensions 14:25:37 <ChrisWarrick> ralsina_: in other news, I will have to move users.getnikola.com because under their new pricing scheme, we will not be able to run it for free — and I have a free VPS handy. You okay with that? 14:25:59 <ralsina_> ChrisWarrick: you can put it in the same VPS where the rest of the sites are 14:26:24 <ChrisWarrick> ralsina_: I also can do that, provided you will set up everything there 14:26:30 <ralsina_> ChrisWarrick: also, want to setup a demo coil instance? 14:26:36 <ralsina_> ChrisWarrick: I can just give you root :-) 14:26:43 <Aeyoun> where do you guys want recent_posts_json, core plugin or user plugin? 14:26:50 <ChrisWarrick> Aeyoun: user 14:27:01 <ChrisWarrick> Aeyoun: nikola needs a diet 14:27:03 <ralsina_> ChrisWarrick: I can set you up with a nikola_users account, and then make it work there I ll proxy it 14:27:05 <ChrisWarrick> ralsina_: I guess I could work on that 14:27:23 <Aeyoun> {js-date:(post-title,post-link)} as /index.json 14:27:31 <ChrisWarrick> ralsina_: ttyl 14:27:38 <ralsina_> ChrisWarrick: sure 14:29:07 <ChrisWarrick> Aeyoun: https://github.com/getnikola/irclogs-site + added last 7 days to the site 14:30:39 <Aeyoun> ChrisWarrick: thanks, that approach seems much more useful. :) 15:05:42 <Aeyoun> can a plugin injct something into templates (at end of document) without modifying templates now? 15:05:57 -GitHub[nikola]:#nikola- [nikola] ralsina created flog-the-donkey (+1 new commit): http://git.io/vUk1a 15:05:57 -GitHub[nikola]:#nikola- nikola/flog-the-donkey a4e11e5 Roberto Alsina: Fix #1695 15:08:09 -GitHub[nikola]:#nikola- [nikola] ralsina opened pull request #1705: Fix #1695 (master...flog-the-donkey) http://git.io/vUkMz 15:18:10 <gour> ChrisWarrick: ahh, '-f pandoc works' since i configured that for asciidoc 15:27:23 <ralsina_> Aeyoun: hmmm 15:27:36 <ralsina_> Aeyoun: it can modify the setting that usually gets tacked there 15:27:54 <ralsina_> self.site.config["BODY_END"] 15:28:15 <ralsina_> there's something called template_hooks but I never saw how it works 15:29:54 <gour> using asciidoc instead of pandoc gives: http://paste.opensuse.org/58475544 15:31:50 -travis-ci:#nikola- getnikola/nikola#4930 (flog-the-donkey - a4e11e5 : Roberto Alsina): The build passed. 15:31:51 -travis-ci:#nikola- Change view: https://github.com/getnikola/nikola/commit/a4e11e5a40dd 15:31:51 -travis-ci:#nikola- Build details: http://travis-ci.org/getnikola/nikola/builds/61776354 15:33:42 <ralsina_> gour are you using python 3? 15:33:58 <gour> testdoc is here: http://pastebin.com/tJsFUMAF 15:34:14 <ralsina_> gour: because that's a bug. I can't beieve how many bugs I got in such a small plugin ;-) 15:34:20 <gour> ralsina_: ahh, asciidoc does not support py3, right? 15:34:29 <ralsina_> gour: no, a bug in the plugin 15:34:39 <gour> ralsina_: ohh, that's better :-) 15:34:43 <ralsina_> we call asciidoc as an external command so as long as it works it will work 15:35:13 <gour> there are not many nikola users of that plugin? 15:35:31 <ralsina_> Ah. no 15:35:36 <ralsina_> That's indeed a bug in asciidoc 15:36:28 <ralsina_> gour: what happens running asciidoc -b html5 -s -o whatever.html posts/testadoc.adoc 15:36:28 <gour> due to py3k? 15:36:34 <ralsina_> gour: dunno 15:36:48 <ralsina_> that error usually means it's ancient python code trying to run in py3 15:36:59 <ralsina_> but I have no idea wbout how you have things setup :-) 15:37:38 <gour> same error 15:38:29 <ralsina_> ok, your asciidoc is broken 15:39:38 <ralsina_> gour: are you using a manually-installed asciidoc? I suggest you just use your distro's package 15:40:14 <ralsina_> I just tested it with asciidoc 8.6.9 in ubuntu and it works fine 15:42:32 <gour> well, running outside of nikola virtualenv it works, but it fails within py3k nikola one 15:42:47 <ralsina_> gour: what s the 1st line in usr/bin/asciidoc 15:42:54 <gour> i'm using distro package, but i believe soon i will leave linux distros 15:43:19 <gour> ralsina_: #!/usr/bin/env python 15:43:35 <ralsina_> ok, with the virtualenv activated, what's which asciidoc ? 15:44:34 <gour> /usr/bin/asciidoc 15:45:11 <ralsina_> ok, you would have to change that to #!/usr/bin/env python2 15:45:21 <ralsina_> and/or report a packaging bug ;-) 15:46:23 <gour> the former is easier considering i'll leave soon :-) 15:49:38 <gour> ralsina_: see http://pastebin.com/PjwRkKWE 15:54:46 <ralsina_> gour: I don't know enough about asciidoc to know what that means 15:55:05 <ralsina_> probably you need to invoke it differently to build that file, but no idea how 15:55:40 -GitHub[nikola]:#nikola- [nikola] ralsina pushed 1 new commit to master: http://git.io/vUIka 15:55:40 -GitHub[nikola]:#nikola- nikola/master fcf1e15 Roberto Alsina: Merge pull request #1705 from getnikola/flog-the-donkey... 15:57:37 <gour> ralsina_: ok, i've fixed the docs to build cleanly within cli, now it build ok with nikola as well 15:57:51 <ralsina_> awesome 15:59:43 <gour> -f asciidoc put header stuff within <!-- ... --> and this is now rendered, so i wonder how should metadata look for asciidoc post? 16:08:34 <ralsina_> gour: asciidoc is supposed to ignore that, right? 16:11:38 <gour> ralsina_: hhm, asciidoc's comment is '//' 16:12:08 <gour> and that works (as intended) 16:12:54 <gour> iow. not rendered, but no tags either 16:13:05 <ralsina_> gour: the asciidoc plugin is supposed to use // for new_post 16:13:11 <ralsina_> I am loooking at the code right now :-P 16:13:28 <ralsina_> Actually ////\nall metadata here//// 16:13:47 <ralsina_> So, you have <!-- in the OUTPUT because yes, that's a comment 16:15:16 <gour> now it's ok with ////...//// 16:15:30 <gour> but wonder how <!-- ... --> ended up there 16:16:05 <ralsina_> did you create this using asciidoc or pandoc? 16:16:34 <gour> right, it was done via pandoc 1st...now with -f asciidoc it's ok 16:21:14 <ralsina_> cool 16:30:26 <gour> i must say that nikola is really very flexible 16:31:09 <ralsina_> gour: maybe too much :-) 16:32:13 <gour> hugo is advertising itself as 'fast & flexible', but it seems it's more 'just fast' and sacrificing its flexbility by mostly staying within golang's ecosystem... 16:32:22 <Aeyoun> hm, google can’t find plug-ins on plugins.getnikola.com. kind of a discoverability bummer. 16:32:45 <gour> ralsina_: don't cut on that, pls. ;) 16:34:43 <ralsina_> Aeyoun: we could make it more discoverable if someone who knows HTML looks at it ;-) 16:35:32 <Aeyoun> ralsina_: how is the site built now? 16:37:44 <ralsina_> Aeyoun: it's a single HTML page that loads json 16:39:58 <Aeyoun> ralsina_: but the site is not built with nikola? its just one static html+js with a generated json? 16:43:16 <ralsina_> yep 17:04:29 -GitHub[plugins]:#nikola- [plugins] Aeyoun created new-recent-posts-json (+1 new commit): http://git.io/vUIXl 17:04:29 -GitHub[plugins]:#nikola- plugins/new-recent-posts-json 5205306 Daniel Aleksandersen: New plug-in: Recent posts as JSON 17:05:44 -GitHub[plugins]:#nikola- [plugins] Aeyoun opened pull request #79: New plug-in: Recent posts as JSON (master...new-recent-posts-json) http://git.io/vUIX7 17:19:28 -GitHub[nikola]:#nikola- [nikola] ralsina created missing-compilers (+2 new commits): http://git.io/vUIQJ 17:19:28 -GitHub[nikola]:#nikola- nikola/missing-compilers de1db16 Roberto Alsina: suggest plugin installation 17:19:28 -GitHub[nikola]:#nikola- nikola/missing-compilers 42a4592 Roberto Alsina: Nicer error for known but unconfigured compilers 17:22:56 -GitHub[nikola]:#nikola- [nikola] ralsina pushed 1 new commit to missing-compilers: http://git.io/vUI7j 17:22:56 -GitHub[nikola]:#nikola- nikola/missing-compilers 8a430d3 Roberto Alsina: use LOGGER.error instead of naked exceptions 17:25:15 -GitHub[nikola]:#nikola- [nikola] ralsina opened pull request #1706: Missing compilers (master...missing-compilers) http://git.io/vUId8 17:37:36 <travis-ci> [PLUGINS] getnikola/plugins#607 (new-recent-posts-json - 5205306 : Daniel Aleksandersen): The build passed. 17:37:37 <travis-ci> [PLUGINS] Change view: https://github.com/getnikola/plugins/commit/52053066a268 17:37:37 <travis-ci> [PLUGINS] Build details: http://travis-ci.org/getnikola/plugins/builds/61791478 17:46:26 <ChrisWarrick> ralsina_: so, do you want me to migrate the users site to your VPS, or can I just hold it on mine? I won’t harm it, I promise. It just feels easier for me to do it myself, without your assistance/root password… So, what’s your decision? 17:46:40 <ralsina_> ChrisWarrick: keep it in your, np 17:46:58 <ChrisWarrick> ralsina_: thanks 17:47:26 <ChrisWarrick> ralsina_: I’ll handle the migration tomorrow. 17:48:21 <ralsina_> awesome 17:49:07 <ChrisWarrick> ralsina_: coil demo is possible only with https://github.com/getnikola/coil/issues/36 — I hope I will feel productive tomorrow 17:49:32 <ralsina_> ChrisWarrick: I can set it up with redis 17:49:42 <ralsina_> ChrisWarrick: if you don't want to do it yourself 17:49:45 <ChrisWarrick> ralsina_: no need to 17:49:51 <ralsina_> ack 17:49:57 <ChrisWarrick> ralsina_: the single-user mode is not that hard to do 17:50:06 <ChrisWarrick> ralsina_: and we can hold it on your VPS easily 17:50:14 <ralsina_> awesome 17:50:44 <ChrisWarrick> will also be a chance to deprecate the webapp plugin 18:05:42 -travis-ci:#nikola- getnikola/nikola#4934 (missing-compilers - 8a430d3 : Roberto Alsina): The build failed. 18:05:43 -travis-ci:#nikola- Change view: https://github.com/getnikola/nikola/compare/42a459244616...8a430d394fca 18:05:43 -travis-ci:#nikola- Build details: http://travis-ci.org/getnikola/nikola/builds/61793830 18:11:30 -travis-ci:#nikola- getnikola/nikola#4933 (missing-compilers - 42a4592 : Roberto Alsina): The build passed. 18:11:31 -travis-ci:#nikola- Change view: https://github.com/getnikola/nikola/compare/de1db1656f65^...42a459244616 18:11:31 -travis-ci:#nikola- Build details: http://travis-ci.org/getnikola/nikola/builds/61793416 18:41:25 <gour> asciidoc (even Pandoc manual) looks much better today with Nikola...so much so that i wonder is there anything to be missed of Nikola's functionality by not using reST markup or the choice of markup is irrelevant? 18:48:59 -GitHub[plugins]:#nikola- [plugins] Aeyoun pushed 1 new commit to new-recent-posts-json: http://git.io/vULaY 18:48:59 -GitHub[plugins]:#nikola- plugins/new-recent-posts-json 4ad118f Daniel Aleksandersen: Dates are not unique. Warnings are alarming. Arrays are enough. 18:50:00 -GitHub[plugins]:#nikola- [plugins] Aeyoun pushed 1 new commit to new-recent-posts-json: http://git.io/vULaS 18:50:00 -GitHub[plugins]:#nikola- plugins/new-recent-posts-json 823cc0f Daniel Aleksandersen: flake8 19:02:41 -GitHub[coil]:#nikola- [coil] Kwpolska created singlemode (+1 new commit): http://git.io/vULit 19:02:41 -GitHub[coil]:#nikola- coil/singlemode 87e83a2 Chris Warrick: initial draft of single mode (#36)... 19:06:47 <ralsina_> gour: we aim to make the choice of markup as irrelevant as possible 19:07:05 <ralsina_> gour: you will miss that with some markups we provide interesting extensions, but that's about it 19:08:13 <gour> ralsina_: something like this feature in hugo: http://gohugo.io/extras/shortcodes/ ? 19:08:31 <ralsina_> gour: let me see... 19:08:48 <ralsina_> something like that yes 19:09:10 <ralsina_> for example, if you want to link to another post or document, in rst you can use :doc:`the-slug` and it will work 19:09:22 <ralsina_> but you can still do that in asciidoc using the link:// syntax 19:09:33 <ralsina_> although it's not all that well documented :-P 19:09:52 <ralsina_> or using .. media:: http://youtube/blah 19:09:57 <ralsina_> and having it just work 19:10:07 <gour> yeah, i was thinking about those media extensions 19:10:17 <ralsina_> but if you like asciidoc, then using asciidoc-specific workarounds is probably good :-) 19:10:58 <ralsina_> We could probably do shortcodes as a generic solution anyway 19:11:15 <ralsina_> sort of a preprocessor step. it may be tricky to make it not conflict with things 19:12:01 <gour> in general, i like asciidoc markup...some things are cleaner, no '.. stuff' things etc. 19:12:19 <gour> moreover, it's suitable for books without sphinx... 19:12:47 <gour> but having 'shortcodes' as general solution would be great... 19:13:05 <ralsina_> I suppose it's just a matter of configurable begin/end markers 19:13:16 <ralsina_> gour: add a bug for it please 19:14:42 <gour> ralsina_: will do 19:18:23 <gour> ralsina_: https://github.com/getnikola/nikola/issues/1707 19:18:41 <travis-ci> [PLUGINS] getnikola/plugins#609 (new-recent-posts-json - 4ad118f : Daniel Aleksandersen): The build was broken. 19:18:41 <travis-ci> [PLUGINS] Change view: https://github.com/getnikola/plugins/compare/52053066a268...4ad118fa819e 19:18:41 <travis-ci> [PLUGINS] Build details: http://travis-ci.org/getnikola/plugins/builds/61805257 19:28:46 <ralsina_> gour: if you see anything missing in asciidoc support (like, possibility to setup different CLI options, etc) just file bugs and I'll get to them eventually 19:29:10 <gour> ralsina_: np. 19:29:46 <gour> ralsina_: one thing i can think of now is support to call asciidoctor 19:30:09 <ralsina_> you will have to explain the issues a lot since I know nothing about asciidoc ;-) 19:30:54 <gour> it's new/popular implementation of asciidoc written in ruby: http://asciidoctor.org/ 19:32:07 <gour> e.g github uses it http://asciidoctor.org/news/2014/02/04/github-asciidoctor-0.1.4-upgrade-5-things-to-know/ 19:32:28 <ralsina_> gour: it's a drop-in replacement, so it's a matter of making the binary configurable 19:32:35 <ralsina_> gour: should not be a big problem ;-) 19:33:02 <gour> mostly it's drop-in, although there are some syntactic changes 19:33:11 <ralsina_> in the markup itself? 19:33:46 <gour> yep 19:33:56 <ralsina_> not much we can do about that 19:34:05 <ralsina_> maybe have a separate plugin then 19:35:46 <gour> mostlyy it's compatible - http://asciidoctor.org/docs/asciidoc-asciidoctor-diffs/ 19:36:31 <gour> and it's ~20x quicker (based on benchmarks i did on my machine) 19:37:26 <gour> this is also cool - http://asciidoctor.org/docs/install-and-use-asciidoctorjs/ 19:37:38 <gour> there is even firefox add-on 19:38:25 <gour> as well as for chrome - https://github.com/asciidoctor/asciidoctor-chrome-extension 20:09:33 <travis-ci> [PLUGINS] getnikola/plugins#611 (new-recent-posts-json - 823cc0f : Daniel Aleksandersen): The build passed. 20:09:33 <travis-ci> [PLUGINS] Change view: https://github.com/getnikola/plugins/compare/4ad118fa819e...823cc0fac412 20:09:33 <travis-ci> [PLUGINS] Build details: http://travis-ci.org/getnikola/plugins/builds/61805342 20:27:36 -GitHub[nikola]:#nikola- [nikola] ralsina created refactor-scanposts (+1 new commit): http://git.io/vUtWO 20:27:36 -GitHub[nikola]:#nikola- nikola/refactor-scanposts bc60ed9 Roberto Alsina: moved scan_posts dumbly into a plugin 20:34:20 -GitHub[nikola]:#nikola- [nikola] ralsina pushed 1 new commit to refactor-scanposts: http://git.io/vUtBe 20:34:20 -GitHub[nikola]:#nikola- nikola/refactor-scanposts 94ed9f7 Roberto Alsina: baby steps 21:08:24 -travis-ci:#nikola- getnikola/nikola#4937 (refactor-scanposts - 94ed9f7 : Roberto Alsina): The build failed. 21:08:25 -travis-ci:#nikola- Change view: https://github.com/getnikola/nikola/compare/bc60ed9942e8...94ed9f7e1495 21:08:25 -travis-ci:#nikola- Build details: http://travis-ci.org/getnikola/nikola/builds/61817462