ics has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
louquillio has quit [Remote host closed the connection]
louquillio has joined #nanoc
ics has joined #nanoc
ics has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
ics has joined #nanoc
ics has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
ics has joined #nanoc
ics has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
ics has joined #nanoc
tom[] has quit [Ping timeout: 240 seconds]
tom[] has joined #nanoc
ics has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
ics has joined #nanoc
<ddfreyne>
tom[]: The fenced code blocks thing looks useful, but a bit bloated. I use fenced code blocks with nanoc on one site and it uses something like that,b ut simpler.
<ddfreyne>
guardian: The site is not open-source
<ddfreyne>
guardian: It's a SoundCloud intranet site
<ddfreyne>
guardian: As for whether it would work with typeahead.js, not sure. The search page of this site is a JS page that sends the query on return though, so maybe it would!
<ddfreyne>
So... probably, but haven't tried :)
<ddfreyne>
I intend to publish a guide for nanoc+lunrjs.
<ddfreyne>
It works so well that I want to move my nanoc site away from S3 and back onto my VPS again :D
jarr0dsz has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
jarr0dsz has joined #nanoc
ics has quit [Ping timeout: 248 seconds]
gkarekinian has quit [Ping timeout: 240 seconds]
gkarekinian has joined #nanoc
jarr0dsz has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
yogsototh has quit [Ping timeout: 252 seconds]
alerante has joined #nanoc
jugglinmike has joined #nanoc
jugglinmike has quit [Quit: Leaving.]
VitamineD has quit [Quit: VitamineD]
yogsototh has joined #nanoc
jugglinmike has joined #nanoc
jugglinmike has quit [Client Quit]
alerante has quit [Remote host closed the connection]
yogsototh1 has joined #nanoc
yogsototh has quit [Ping timeout: 246 seconds]
VitamineD has joined #nanoc
tantalum has joined #nanoc
alerante has joined #nanoc
alerante has quit [Ping timeout: 252 seconds]
alerante has joined #nanoc
pavelkunc has joined #nanoc
alerante_ has joined #nanoc
alerante has quit [Ping timeout: 268 seconds]
alerante has joined #nanoc
alerante_ has quit [Ping timeout: 248 seconds]
ics has joined #nanoc
alerante_ has joined #nanoc
alerante has quit [Ping timeout: 245 seconds]
alerante_ is now known as alerante
alerante has quit [Remote host closed the connection]
alerante has joined #nanoc
bghost has joined #nanoc
bghost has quit [Changing host]
bghost has joined #nanoc
alerante has quit [Ping timeout: 240 seconds]
<bobthecow>
guardian: mebbe having people use nanoc who approach it backwards will help point at us places for better documentation :)
alerante has joined #nanoc
<guardian>
yeah maybe
<guardian>
I get you kindof agree the first reaction upon reading is like "hmm! hmm? wait? NO!" :)
<summatusmentis>
I'll say, when I was learning the basics, I read through the tutorials, and had no idea where to go
<bobthecow>
summatusmentis: some of us have been in nanoc so long it's hard to see how you'd misunderstand things.
<bobthecow>
so we welcome feedback about making it better for everyone else :)
<bobthecow>
guardian: yep, agreed. but i get some of that with most new nanoc users.
<summatusmentis>
bobthecow: the primary high-level feedback I can give right this minute is that while the tutorials/docs gave high-level explanation on "what a thing is", there was very little information on "how do I use this thing?"
<bobthecow>
so concrete howto type content would help?
<bobthecow>
case studies, example sites, etc?
<summatusmentis>
one can fake their way through that by looking at the API docs (for things like helpers in particular), but that's not super friendly
<summatusmentis>
concretely walking through "what does this thing get me?" would be helpful
<summatusmentis>
could be example sites, could be "here's how you add a blog module", "here's how you create a side-bar", "here's what an external item means"
<summatusmentis>
even things like "do I have to create the item with the nanoc tool?" (answer is no, you can just copy files in)
<summatusmentis>
but there's not ways to find these things out without just trying them
jadd_ has joined #nanoc
alerante_ has joined #nanoc
alerante has quit [Ping timeout: 248 seconds]
alerante_ has quit [Ping timeout: 240 seconds]
tantalum has left #nanoc [#nanoc]
alerante has joined #nanoc
pavelkunc has quit [Quit: Leaving.]
bghost has quit [Quit: leaving]
alerante_ has joined #nanoc
alerante has quit [Ping timeout: 240 seconds]
alerante_ has quit [Remote host closed the connection]
<tom[]>
in order to implement TOC sorting, i cloned https://startpage.com/do/search. but, as a rubynoob, i've no idea how to make nanoc use the clone instead of the installed gem
<tom[]>
i'd ask on a general ruby channel but i don't know how to describe the /lib context in a nanoc site
<bobthecow>
tom[]: i have no idea what you're asking.