I've just pushed the gem. The main difference in 0.9.11 is that Ryan Tomayko's Tilt library is used to render Markdown and Textile files inside your content/pages folder. This means you can choose which Markdown processor is used to render your content. The default processor is now RDiscount (it was Maruku). There's also a new metadata key (called 'Articles heading'), and trailing slashes are stripped from URLs. More details, upgrade instructions and links to the new docs are on the blog post: http://nestacms.com/blog/version-0-9-11
@Graham, that's awesome. Is there a reason for not using github's redcarpet though? On Thu, Sep 22, 2011 at 6:22 PM, Graham Ashton <graham@effectif.com> wrote: > I've just pushed the gem. > > The main difference in 0.9.11 is that Ryan Tomayko's Tilt library is used > to render Markdown and Textile files inside your content/pages folder. This > means you can choose which Markdown processor is used to render your > content. The default processor is now RDiscount (it was Maruku). > > There's also a new metadata key (called 'Articles heading'), and trailing > slashes are stripped from URLs. > > More details, upgrade instructions and links to the new docs are on the > blog post: > > http://nestacms.com/blog/version-0-9-11 >
On 22 Sep 2011, at 16:24, Misha Reyzlin wrote:
> @Graham, that's awesome. Is there a reason for not using github's
redcarpet though?
Redcarpet was the preferred option, but we're waiting on a patch being
applied to Haml.
See the comments on this commit:
https://github.com/gma/nesta/commit/5e0f2af33f6ccb2886cb67c8d6bc18385773ef83
And on the Redcarpet issue:
https://github.com/gma/nesta/pull/65
And finally, no the haml pull request that needs to be applied first:
https://github.com/nex3/haml/pull/383
I suppose it wouldn't hurt if a few of us chipped in on that thread...
If you want to use Redcarpet anyway, see this article:
http://nestacms.com/docs/creating-content/changing-the-markdown-processor
huh, thanks for the fast answer, as a matter of fact i've been using it since 0.9.4, I've "+1"d the pull request, thanks for the explanation! On Thu, Sep 22, 2011 at 6:38 PM, Graham Ashton <graham@effectif.com> wrote: > On 22 Sep 2011, at 16:24, Misha Reyzlin wrote: > > > @Graham, that's awesome. Is there a reason for not using github's > redcarpet though? > > Redcarpet was the preferred option, but we're waiting on a patch being > applied to Haml. > > See the comments on this commit: > > https://github.com/gma/nesta/commit/5e0f2af33f6ccb2886cb67c8d6bc18385773ef83 > > And on the Redcarpet issue: > https://github.com/gma/nesta/pull/65 > > And finally, no the haml pull request that needs to be applied first: > https://github.com/nex3/haml/pull/383 > > I suppose it wouldn't hurt if a few of us chipped in on that thread... > > If you want to use Redcarpet anyway, see this article: > > http://nestacms.com/docs/creating-content/changing-the-markdown-processor >