12:58 <ddfreyne> tom[]: By generating items I mean creating in-memory items in the preprocess block that aggregate the contents of several other items

12:59 <ddfreyne> e.g. If you compile C source code, the .o files can be considered output of the .c files, but then you still need to combine the .o files into an executable, which will not have an on-disk source representation, because it is build from other items

16:27 <tom[]> @ddfreyne: i see. so you were asking about the "merge DSL command to generate items" thing?

17:13 <ddfreyne> yup

17:16 <tom[]> iiuc, i would probably not use something like that

17:17 <tom[]> because each combined/compressed final asset file is assembled from the same base set of sources

17:20 <tom[]> what i have done is 1. put the sources somewhere with whatever basic compilation they need (eg sass). 2. specify null routing for them. 3. create items for final resource files and run then through erb and a suitable compressor. 4. these files contain likes like: <%= @items['/assets/css/base/'].compiled_content() %>

17:22 <tom[]> this allows me to design a set of optimized final asset files, each specified in terms of it's own language and including content from other files

17:23 <tom[]> simple, clear and gives me the control i want

17:28 <tantalum> Hi Guys,

17:28 <number-six> tantalum: ddfreyne (19 days ago): How big is your site, in number of pages?

17:29 <tantalum> number-six, ?

17:29 <tantalum> Any way.

17:30 <tantalum> I have a site and we need a desktop and a mobile version, with the same content

17:30 <tantalum> I've used Item Representations to compile a mobile and desktop version

17:30 <tantalum> but how do I route the representations?

17:31 <tantalum> route '/content/pages/*', :rep => :mobile do .... end ?

17:31 <tantalum> would that be it? the docs are a little vague on that subject

18:12 <ddfreyne> tantalum: yes

18:13 <tantalum> ddfreyne, Thanks... I'm compiling as we speak :-)

18:13 <ddfreyne> tantalum: http://nanoc.ws/docs/reference/rules/

18:13 <ddfreyne> The example on there says

18:13 <ddfreyne> route "/people/*/", :rep => :text do item.identifier.chop + ".txt"

18:13 <ddfreyne> end

18:14 <ddfreyne> tantalum: number-six is a bot that records messages and plays them back when you come back

18:14 <tantalum> I was looking at this http://nanoc.ws/docs/basics/#the-compilation-process

18:14 <ddfreyne> So 19 days ago you had an issue with a large site, I imagine

18:14 <tantalum> it discusses compiling items with reps

18:14 <tantalum> ddfreyne, Yeah, I do

18:15 <ddfreyne> tantalum: Ahh, i twould make sense for the examples there to match, which they currently don't

18:15 <tantalum> it's just me bitching about how long it takes to compile the content

18:15 <tantalum> ddfreyne, Yeah, that's why I was confused

18:16 <ddfreyne> tantalum: What filters are you using? It may be worth reducing the amount of filtering and choosing faster filters

18:16 <ddfreyne> e.g. rubypants is slow, and typogruby is extremely slow

18:17 <tantalum> My slowest filter by far seems to be sass

18:19 <ddfreyne> tantalum: What does compiling with --verbose tell you?

18:19 <ddfreyne> (using the most recent nanoc)

18:20 <ddfreyne> tantalum: How long does it take to compile your site? How many items does it have, roughly?

18:21 <tantalum> ddfreyne, I'll have to check it later... I appreciate the help

18:22 <ddfreyne> You're welcome

18:22 <tantalum> Once I get the mobile site up I', gonna try to cut down the compilation time

18:22 <tantalum> I know my biggest holdup is sass, and I have 1,000+ items

18:22 <tantalum> and two representations for content pages

18:23 <gregkare> There's probably a gem that uses the C libsass, and if not you can just use a binary I guess, that should make it much faster

18:23 <tantalum> so it's not _unexpectedly_ slow

18:23 <gregkare> I have to run, see you!

18:24 <tantalum> Later

18:25 <ddfreyne> Seeya

18:37 <brcwade> Hey, I had a quick question about creating new pages in nanoc that I am getting confused with

18:37 <brcwade> So, when you create a new page, you have to create a new .md file in the content directory

18:38 <brcwade> and that is associated with the default.html html file

18:38 <brcwade> and I know you can create a new html file that is associated with that .md file

18:38 <brcwade> but I'm not sure how to connect the two

18:39 <brcwade> Like, I can't just create a .md page called aboutus.md and then an html page called aboutus.html, it still used the default.html page

18:39 <brcwade> if that makes sense

18:46 <brcwade> probably kind of an easy thing that I'm missing, but I'm new to nanoc

18:54 <tantalum> brcwade, http://nanoc.ws/docs/basics/#the-compilation-process

18:58 <brcwade> so is it the stuff under BUILDING THE ITEM REPRESENTATIONS and ROUTING THE ITEM REPRESENTATIONS ?

18:58 <tantalum> brcwade, It's a two-step process

18:59 <tantalum> First you compile the content, such as translate markdown into HTML, apply the templates... etc

18:59 <tantalum> the second step is routing which matches a representation to an output file

19:02 <brcwade> Is there a specific file where it would be located in?

19:03 <brcwade> oh the Rules file?

19:04 <brcwade> and that would connect the layouts to the content?

19:07 <tom[]> brcwade: it sure does

19:08 <tom[]> brcwade: have you done the tutorial? it's quite good

19:11 <brcwade> I think I found where the issue is, if it is just stuff that I have to change in the Rules file

22:26 <guardian> ddfreyne: can you remind me the js search lib you used with nanoc?

23:10 <dkm> next time tantalum is online someone suggest responsive CSS layouts to him regarding "mobile and desktop" version of his site

23:11 <dkm> I use susy, which is quite nice

23:11 <dkm> http://susy.oddbird.net/demos/magic/

23:12 <dkm> moral of the story, I don't think different versions of the content for mobile vs. desktop should be different nanoc representations