nanoc

Hey Ulf, That error isn't directly familiar to me, unfortunately. Though I do have a

Hey Pito, I haven't verified myself, but I believe the instructions are still up to date! Cheers,

Thanks for confirming that was right! That led me down the path of realising I didn't actually

Hello everyone, I have many questions and need help when deploying nanoc site to github pages: 1. Do

Hey there, The approach I use in this case is to remove the file (from memory) in the preprocessor:

After all, I did the obvious: cram everything in one single filter, calling `render` directly there

Yes, and nanoc is now running fine for me. Initially it didn't work, so I opened my package

Merci beaucoup, Denis. I'm taking a break from the project that I'll be using Nanoc for (

Hey there, Is there a theme/template that I can use similar to academic theme in hugo which I can use

thanks Eric - searched but couldn't find in the docs (brain not functioning within normal

Thanks for your answer, I really appreciate it! On Tuesday, April 19, 2022 at 1:16:17 AM UTC+7 Eric

Both those charities are on my donation list too! They are two of the ones I give the most to, in

Hi Lukas, There's no trivial way to tell the web server to serve files from two locations. You

Hey there, I released Nanoc 4.12.5 which will work with the default YAML (Psych) that comes with Ruby

UPDATE: just needs gem install webrick. The error is a Ruby 3* issue and is covered in the Nanoc docs

Hi both, Oh, captain I've been hit ! Well, it looks so easy when you know it ! I thought that

Good ideas Dave. I was looking through the `Rules` file options but didn't see anything there.

Many thanks Denis - that's done it! I'll remove you from the repo - yes, the <%= @item[:

Hi Denis that's great news. I'm not ever likely to change the three nanoc sites I maintain to

Hey BB, When using the :asciidoctor filter, all parameters are passed to the Asciidoctor.convert call

Hi Denis Yes, it did, Thanks! Some new git and gh magic I didn't know :) I assume I treat the

I use this kind of thing in my layouts for the Dublin Core metadata - specifically: if you add the

I'd remove the `if` blocks and just run the `gsub` calls. Having both there means you're

Thanks a lot, that explains one thing that was confusing me :) Pito Salas Faculty, Computer Science

Hey both, Thomas is correct — anywhere in lib/ will do. My preference is to use the naming scheme lib

Totally agree about being against the "spirit of the web". Understood about the elinks

Hey Benedikt, I've left a comment in the GitHub discussion. Let me know how it works for you!

I just caught this. Agree - so worth knowing, and not at all obvious. I NEED this. Thanks for leaving

Like the warning code idea! @Pito - it's not Nanoc itself, but (I presume) the Ruby server it

Hey Pito, I believe the issue is this: If a compilation rule uses #write, Nanoc doesn't look for