04:55 <geotti> Hey, did anyone come around to building a GUI or web interface to nanoc? I'd like to allow some non-techies to author posts

05:00 <geotti> Ok, just found this: https://trello.com/c/dVuvYmxd/65-gui. I guess not

11:11 <ddfreyne> geotti: No, unfortunately not. It’s a very complex problem to tackle.

11:13 <geotti> ddfreyne: yeah, having an interesting discussion with mitchell over in #pelican about what such an editor should do (i.e. be aware of the system itself, the use-case, the user-experience [i.e. hide UI elements as appropriate], be extendable [i.e. new use-cases as plugins]) ...

11:14 <geotti> ddfreyne jaredly did a nice blog-related web-app for hexo over here, which is very simple to use: http://jaredly.github.io/hexo-admin/

11:15 <ddfreyne> geotti: I see dependency tracking as one of the pain points. If one page changes, a lot of other pages can be affected, so compilation can potentially take a long time

11:16 <ddfreyne> I’d ideally also love to have a real-time preview, which would require nanoc to be able to recompile pages in realtime and with a small delay (< 0.5s).

11:16 <geotti> ddfreyne: I don't really know nanoc, but the way it's solved in the above tool is that stuff can be published or not and after you're done you generate/deploy the site

11:16 <ddfreyne> geotti: nanoc does dependency tracking. If the home page contains the latest blog post, and you write a new blog post, the home page will be updated too.

11:16 <ddfreyne> (But other blog posts aren't affected so they are not recompiled)

11:18 <geotti> ddfreyne: I believe this is the way it works in hexo as well (used it for two days, but ultimately it isn't up to my requirements). But you don't need to update everything

11:20 <ddfreyne> geotti: nanoc only recompiles what's necessary

11:20 <ddfreyne> (In case of doubt, it will recompile.)

11:21 <geotti> Hm.. I guess this matters a lot for *huge* sites

11:22 <ddfreyne> geotti: Huge sites are a problem for static site generators, even with dependency tracking

11:22 <geotti> ddfreyne: the question is, whether it'd be possible to ignore this and just recompile everything and leave dependency tracking for a later date

11:22 <ddfreyne> geotti: Huge as in a few thousand pages or more

11:22 <geotti> yes

11:22 <ddfreyne> geotti: nanoc's dependency tracking already exists and works

11:23 <ddfreyne> It's not perfect, but there are some very hard problems to solve anyway (for instance, if you have an ERB-formatted page, how do you know what it depends on? You can only know by compiling the item.)

11:23 <ddfreyne> page == item btw

11:24 <ddfreyne> geotti: I’m a bit feverish atm, so I’m not in the best condition to talk

11:24 <geotti> ddfreyne: I guess we're on par, as I've been up a while ;)

11:25 <geotti> ddfreyne: so the issue is essentially partials?

11:27 <geotti> ddfreyne: what I mean is that maybe it's not necessary to compile the whole item, but just render what can be rendered for the partial?

12:21 <travis-ci> nanoc/nanoc/master bf03823 Denis Defreyne: The build passed.