ics has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
ics has joined #nanoc
jarr0dsz has joined #nanoc
jaspervdj has quit [Ping timeout: 245 seconds]
jaspervdj has joined #nanoc
jarr0dsz has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
jarr0dsz has joined #nanoc
matjas has quit [Ping timeout: 245 seconds]
_rgn has quit [Ping timeout: 245 seconds]
ics has quit [Ping timeout: 252 seconds]
ics has joined #nanoc
matjas has joined #nanoc
_rgn has joined #nanoc
VitamineD has joined #nanoc
VitamineD has quit [Quit: VitamineD]
number-six has quit [Ping timeout: 246 seconds]
number-six has joined #nanoc
ics has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
alerante has joined #nanoc
jugglinmike has joined #nanoc
alerante has quit [Remote host closed the connection]
ics has joined #nanoc
tom[] has joined #nanoc
VitamineD has joined #nanoc
ics has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
VitamineD has quit [Quit: VitamineD]
<tom[]>
is nanoc suitable for my new technical documentation project? it is a collection of a few hundred pages authored in markdown, arranged hierarchically (2 or 3 levels) by topic. the generator (nanoc?) needs to produce the pages with sidebar TOC for navigation
jugglinmike is now known as iros__
iros__ is now known as iros___
iros___ is now known as jugglinmike
tantalum has joined #nanoc
<bobthecow>
tom[]: yes.
skroon has quit [Read error: Connection reset by peer]
skroon has joined #nanoc
<Evolution>
tom[]: I like it for that, yes. though I'd consider asciidoc over markdown for that much doc
<tom[]>
Evolution: i'll check out asciidoc. tnx
<tom[]>
bobthecow: tnx
<tom[]>
can you suggest any "skeleton" projects for nanoc i could use as example or maybe even a basis to adapt?
<bobthecow>
github's API docs are written in nanoc, lots of people use those as a basis for things.
jarr0dsz has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
jarr0dsz has joined #nanoc
<bobthecow>
there are a couple of people writing courseware using nanoc. i don't remember who. mebbe ddfreyne would?
<tom[]>
pity there isn't a linter for php as strict and rude as jslint
<bobthecow>
do you use PHPCS?
<bobthecow>
you can make it as strict as you want.
<tom[]>
yes, but it's not as good
<bobthecow>
i personally prefer jshint.
<tom[]>
exactly. phpcs like jslint is whatever you want. so you can ask it to ok anything
<tom[]>
i mean, like jshint
<bobthecow>
agreed.
<bobthecow>
and that's why i prefer jshint.
<tom[]>
and why i don't
<bobthecow>
because i don't have to write code exactly like crockford for it to be good.
<bobthecow>
it just needs to be consistent and not do stupid things.
<tom[]>
my opinion about coding standards and style doesn't matter.
<tom[]>
just tell me what it should be
<bobthecow>
yeah. and jshint will do that if you run it with default options.
<bobthecow>
but it won't berate you about things that don't matter.
<bobthecow>
there's "make it standard" and there's "make it exactly like so"
<tom[]>
sould like an opinion i'm not competent to hold
<bobthecow>
:)
<tom[]>
i'm a bad programmer
<tom[]>
been doing it for 35 years and learned not to trust myself
<tom[]>
marginally competent
<bobthecow>
basically for code standards i grab a reasonably well adopted standard that doesn't seem like too much busy work and use that.
<bobthecow>
for PHP, that's the PSR standards
<bobthecow>
for Ruby, I use GitHub's style guide.
<bobthecow>
for JS, I use jslint.
<bobthecow>
*jshint
<bobthecow>
because it's less work, but catches all the things i need to catch.
<guardian>
Evolution: why asciidoc over markdown?
<tom[]>
i've been researching that too
<Evolution>
guardian: markdown has a few limitations I ran into in the format for my needs. asciidoc can be exported to a wide range of formats, so the same document can be used for website, pdf , etc.
<Evolution>
I'm still using markdown for quite a bit, but for 'formal' project documentation, asciidoc was a better fit for us.
<Evolution>
entirely personal opinion.
<guardian>
ok
<tom[]>
md becomes hard, i've found, when i needed to do a lot of references (cross, footnotes, sections, pages)