D
Denis Defreyne
Hi.
I'm happy to announce the final release of nanoc 3.0, the latest =20
version of nanoc, a web publishing tool aimed at small to medium-sized =20=
static or semi-static web sites.
You can install it using Rubygems:
sudo gem install nanoc3
If you are new to nanoc, I recommend checking out the tutorial[tut] =20
and, if you need more, the manual[man].
If you have used nanoc 2.x before, the tutorial[tut] is still a very =20
good resource. You'll definitely want to check out the migration =20
guide[mig], and perhaps the manual[man] as well.
[tut]: http://nanoc.stoneship.org/tutorial/
[man]: http://nanoc.stoneship.org/manual/
[mig]: http://nanoc.stoneship.org/migrating/
Compatibility with nanoc 2.x
----------------------------
nanoc 3.0 is not backward compatible with previous nanoc versions. =20
This is deliberate: focus on the future, leave the past behind. A =20
nanoc 2.x site cannot be compiled with nanoc 3.0.
Fortunately, nanoc 2.x and 3.0 can be installed side by side. The =20
nanoc 2.x commandline tool is called `nanoc` while the nanoc 3.0 one =20
is called `nanoc3`; similarly, the nanoc 2.x namespace is `Nanoc` and =20=
the nanoc 3.0 one is `Nanoc3`. In other words, you can easily use both =20=
nanoc 2.x and 3.0 simultaneously.
New Features
------------
Here's a short list with the biggest additions to nanoc 3.0:
* Multiple data sources so you can load data from multiple locations=96=20=
for example, Twitter, Delicious and Last.fm.
* Filter arguments so you can pass extra arguments when executing a =20
filter. For example, you can now pass Haml options when executing =20
filters, like this: filter :haml, :format =3D> :html5.
* A more compact filesystem-based data source called =20
filesystem_combined that doesn=92t require tons of directories in the =20=
content and layout directories. Cleaner and less verbose.
* An all-new dependency tracking system that ensures that all modified =20=
items and their dependent items are recompiled when the site is =20
compiled. This speeds up site compilation by preventing non-modified =20
pages from being recompiled.
* A rules file which allows processing instructions (filtering pages, =20=
laying out pages) to be specified in a much more DRY way. In addition, =20=
the rules file is much more powerful than specifying processing =20
instructions using item/layout attributes.
If you have questions, feel to drop by on the mailinglist
I'm happy to announce the final release of nanoc 3.0, the latest =20
version of nanoc, a web publishing tool aimed at small to medium-sized =20=
static or semi-static web sites.
You can install it using Rubygems:
sudo gem install nanoc3
If you are new to nanoc, I recommend checking out the tutorial[tut] =20
and, if you need more, the manual[man].
If you have used nanoc 2.x before, the tutorial[tut] is still a very =20
good resource. You'll definitely want to check out the migration =20
guide[mig], and perhaps the manual[man] as well.
[tut]: http://nanoc.stoneship.org/tutorial/
[man]: http://nanoc.stoneship.org/manual/
[mig]: http://nanoc.stoneship.org/migrating/
Compatibility with nanoc 2.x
----------------------------
nanoc 3.0 is not backward compatible with previous nanoc versions. =20
This is deliberate: focus on the future, leave the past behind. A =20
nanoc 2.x site cannot be compiled with nanoc 3.0.
Fortunately, nanoc 2.x and 3.0 can be installed side by side. The =20
nanoc 2.x commandline tool is called `nanoc` while the nanoc 3.0 one =20
is called `nanoc3`; similarly, the nanoc 2.x namespace is `Nanoc` and =20=
the nanoc 3.0 one is `Nanoc3`. In other words, you can easily use both =20=
nanoc 2.x and 3.0 simultaneously.
New Features
------------
Here's a short list with the biggest additions to nanoc 3.0:
* Multiple data sources so you can load data from multiple locations=96=20=
for example, Twitter, Delicious and Last.fm.
* Filter arguments so you can pass extra arguments when executing a =20
filter. For example, you can now pass Haml options when executing =20
filters, like this: filter :haml, :format =3D> :html5.
* A more compact filesystem-based data source called =20
filesystem_combined that doesn=92t require tons of directories in the =20=
content and layout directories. Cleaner and less verbose.
* An all-new dependency tracking system that ensures that all modified =20=
items and their dependent items are recompiled when the site is =20
compiled. This speeds up site compilation by preventing non-modified =20
pages from being recompiled.
* A rules file which allows processing instructions (filtering pages, =20=
laying out pages) to be specified in a much more DRY way. In addition, =20=
the rules file is much more powerful than specifying processing =20
instructions using item/layout attributes.
If you have questions, feel to drop by on the mailinglist
- or the =20=
IRC channel[irc]. On IRC, I'm not always around, but when I am, I'll =20
be happy to answer any questions you have.
- : http://groups.google.com/group/nanoc/
[irc]: irc://chat.freenode.net/#nanoc
Regards,
Denis
--=20
Denis Defreyne
(e-mail address removed)
- : http://groups.google.com/group/nanoc/