<asgulor>
Well, if you have time to help me, it will be a real pleasure for me to add Font Awesome to my project
<bobthecow>
because i could tell you what's going on, but i'd just be telling you what that says only slower because i can't type that fast :)
<tom[]>
i have a theory about why there are so many bad examples, tutorials, blogs and wikis that purport to explain software stuff
<bobthecow>
what's that?
<asgulor>
I had an error like this 'Found 3 content files for X; expected 0 or 1' but my main problem is that I want to use HAML
<asgulor>
To give you an example, I would like to include some icons in my layouts
<bobthecow>
asgulor: you read that section?
<asgulor>
Yes, bobthecow
<bobthecow>
okay. so you have two data sources:
<bobthecow>
filesystem and static.
<bobthecow>
stuff in static can't really be filtered... it's pretty much just useful for copying straight into output.
<asgulor>
OK
<bobthecow>
stuff in the filesystem data source is normal nanoc stuff. it can be filtered, etc.
<bobthecow>
so just put font awesome in static, put everything else in content.
<bobthecow>
then you can use haml for the content stuff, and copy the font awesome stuff straight across.
<bobthecow>
the dumb thing this sample site does is put the static stuff in the same "items root" as the normal content, so it's harder to make rules for it.
<tom[]>
if somebody is skilled at x, it doesn't seem like anything in particular when they solve a problem. it's just like any other event. but to someone new to the x, somebody learning and not fully competent, it can seem like a triumph to solve a problem that's challenged them. they want to shout from the hilltops: "I solved it!" but, because being truly skilled at anything is required to b able to know if a solution is right or wrong, the
<tom[]>
chances are high that the one on the hilltop hasn't found a good solution
<asgulor>
I did that. Unfortunately, when I type 'compile '/' do, everything goes wrong
<asgulor>
Of course, I typed 'compile '/' do' in Rules
<bobthecow>
define "everything goes wrong"
<bobthecow>
i think there might be multiple things at play here :P
<asgulor>
Yes, you're right, tom. I actually tried to do it before on my own but I had some problem
<bobthecow>
asgulor: open up nanoc.yaml in your site.
<bobthecow>
under data sources type: static
<bobthecow>
remove the "allow_periods_in_identifiers: true"
<bobthecow>
because it doesn't do anything at all.
<asgulor>
When I changed the rules, I typed 'compile '/' do filter :HAML', I changed 'index.html' in content in index.haml, it doesn't work
<bobthecow>
and change "items_root: /" to "items_root: /assets/"
<bobthecow>
define "it doesn't work"
<bobthecow>
there are lots of ways of not working, and i can't help you until i know which way it is :)
<bobthecow>
in fact, there is only one way of working, and infinite ways of not working.
<asgulor>
Sorry, bob :)
<asgulor>
Well, I don't see icons
<asgulor>
When you compile the github repo, you will see a house icon
<asgulor>
When I change the file with HAML, I just see all my text in italic
<bobthecow>
so does it show you uncompiled haml source?
<asgulor>
Yes
<asgulor>
Actually, I came here to know if someone already use the last version of Font Awesome. Because it seems that there is no compatibility with Nanoc. Is that true?
<bobthecow>
okay. so that's unrelated to the font awesome.
<asgulor>
OK
<bobthecow>
font awesome is 100% compatible with nanoc.
<bobthecow>
everything ever made for the web is 100% compatible with nanoc.
<bobthecow>
nanoc doesn't care.
<asgulor>
OK :)
<bobthecow>
it's like a honeybadger.
<asgulor>
:D
<bobthecow>
can you paste a gist of your rules file so i can follow along?
<bobthecow>
and your config file.
<asgulor>
Well, bob, I would like to try with the last version of Font Awesome in my project
<bobthecow>
yes, we've established this :)
<asgulor>
Can I try again and I will send you my error messages?
<bobthecow>
please paste your config and rules file into a gist so i can see them?