On Sat, 2018-07-28 at 13:28 -0400, Jason E Bailey wrote:
> I believe there's a difference between what the two end goals are.
> There is a the rendering of a Markdown resource into HTML and then
> there is using a Markdown file to generate a resource.
That is a good distinction to be made, and
On Fri, 2018-07-27 at 15:49 +0200, Bertrand Delacretaz wrote:
> On Fri, Jul 27, 2018 at 3:16 PM Daniel Klco
> wrote:
> > On Fri, Jul 27, 2018, 8:46 AM Jason E Bailey
> > wrote:
>
> ...
> > > Not understanding the phrase "front matter" in it's usage here
> >
> > I'm assuming YAML front matter
On Fri, 2018-07-27 at 10:14 +0200, Andrei Dulvac wrote:
> Hi.
>
> That's cool indeed!
>
> What about using (potentially different) HTL scripts and create a
> Sling
> model that reads the raw markdown?
The markdown files have a default resource type of sling/markdown/file
[1] . This can be
On Fri, 2018-07-27 at 08:07 +0200, Bertrand Delacretaz wrote:
> On Fri, Jul 27, 2018 at 1:18 AM Robert Munteanu
> wrote:
> ...
> > - render everything else as HTML into jcr:description ...
>
> I think rendering is a good idea but how about using a more specific
> property name?
>
> Maybe use
On Fri, 2018-07-27 at 07:51 +0200, Carsten Ziegeler wrote:
> Interesting, I've started similar work some time back but never
> finished
> it :) Back then I thought that this is a cross cutting concern, md
> files
> can be stored anywhere, in the file system, in jcr, fetched by a
> special
> github
such apps.
Regards,
Eugen Stan
Netdava International
Mesaj original
De la: jason.bai...@24601.org
Trimis: 28 iulie 2018 20:28
Către: dev@sling.apache.org
Răsp. la: dev@sling.apache.org
Subiect: Re: Markdown resource provider
I believe there's a difference between what the two end goals
la: jason.bai...@24601.org
> Trimis: 28 iulie 2018 20:28
> Către: dev@sling.apache.org
> Răsp. la: dev@sling.apache.org
> Subiect: Re: Markdown resource provider
>
> I believe there's a difference between what the two end goals are. There
> is a the rendering of a Mark
@sling.apache.org
Subiect: Re: Markdown resource provider
I believe there's a difference between what the two end goals are. There is a
the rendering of a Markdown resource into HTML and then there is using a
Markdown file to generate a resource.
A couple of thoughts on this.
# For a Markdown Resource
I believe there's a difference between what the two end goals are. There is a
the rendering of a Markdown resource into HTML and then there is using a
Markdown file to generate a resource.
A couple of thoughts on this.
# For a Markdown Resource providing attributes, I don't see a reason to use
> Daniel Klco wrote
>> My first thought after reading the last paragraph was - Wouldn't it be
>> cool if the FsResourceProvider was extensible so that specific files could
>> be rendered in a specific manner, then you could add a MarkDown Handler and
>> it would make it easier for other people
On Fri, Jul 27, 2018 at 3:16 PM Daniel Klco wrote:
> On Fri, Jul 27, 2018, 8:46 AM Jason E Bailey wrote:
...
> > Not understanding the phrase "front matter" in it's usage here
> I'm assuming YAML front matter like is used in Jekyll. Correct? ..
That's my understanding as well, like the first
On Fri, Jul 27, 2018, 8:46 AM Jason E Bailey wrote:
> In line
>
> - Jason
>
> On Thu, Jul 26, 2018, at 7:18 PM, Robert Munteanu wrote:
> > Hi,
> >
> > I've been toying around with a Markdown resource provider in the
> > whiteboard [0]. It's very mu
In line
- Jason
On Thu, Jul 26, 2018, at 7:18 PM, Robert Munteanu wrote:
> Hi,
>
> I've been toying around with a Markdown resource provider in the
> whiteboard [0]. It's very much a work-in-progress but since it does
> something - aka render Markdown files, including suppor
Hi.
That's cool indeed!
What about using (potentially different) HTL scripts and create a Sling
model that reads the raw markdown?
- Andrei
On Fri, Jul 27, 2018, 08:07 Bertrand Delacretaz
wrote:
> Hi Robert,
>
> Cool stuff!
>
> On Fri, Jul 27, 2018 at 1:18 AM Robert Munteanu
> wrote:
> ...
Hi Robert,
Cool stuff!
On Fri, Jul 27, 2018 at 1:18 AM Robert Munteanu wrote:
...
> - render everything else as HTML into jcr:description ...
I think rendering is a good idea but how about using a more specific
property name?
Maybe use sling:markdownBody and sling:renderedHtmlBody with the
been toying around with a Markdown resource provider in the
> whiteboard [0]. It's very much a work-in-progress but since it does
> something - aka render Markdown files, including support for arbitrary
> Sling properties, I would like to discuss a couple of design decisions.
>
> 1. The resour
Hi,
I've been toying around with a Markdown resource provider in the
whiteboard [0]. It's very much a work-in-progress but since it does
something - aka render Markdown files, including support for arbitrary
Sling properties, I would like to discuss a couple of design decisions.
1
17 matches
Mail list logo
