Hey Joe,
I can definitely write one up.
Thanks,
Bryan
On Jul 15, 2016 10:43 PM, "Joe Witt" wrote:
> Just wanted to bump this thread. Looked like a lot of folks liked the
> idea. Do you plan to file a JIRA for this Bryan?
>
> On Thu, Jun 9, 2016 at 8:39 AM, Joe Skora wrote:
> > +1
> >
> > On
Just wanted to bump this thread. Looked like a lot of folks liked the
idea. Do you plan to file a JIRA for this Bryan?
On Thu, Jun 9, 2016 at 8:39 AM, Joe Skora wrote:
> +1
>
> On Wed, Jun 8, 2016 at 10:40 AM, Matt Burgess wrote:
>
>> +1 with template
>>
>> On Wed, Jun 8, 2016 at 10:39 AM, dan
+1
On Wed, Jun 8, 2016 at 10:40 AM, Matt Burgess wrote:
> +1 with template
>
> On Wed, Jun 8, 2016 at 10:39 AM, dan bress wrote:
> > +1
> >
> > On Wed, Jun 8, 2016 at 7:05 AM Andre wrote:
> >
> >> +1 on this + a template that matches existing additional.html
> >> On 8 Jun 2016 04:28, "Bryan Ro
+1 with template
On Wed, Jun 8, 2016 at 10:39 AM, dan bress wrote:
> +1
>
> On Wed, Jun 8, 2016 at 7:05 AM Andre wrote:
>
>> +1 on this + a template that matches existing additional.html
>> On 8 Jun 2016 04:28, "Bryan Rosander" wrote:
>>
>> > Hey all,
>> >
>> > When writing documentation (e.g.
+1
On Wed, Jun 8, 2016 at 7:05 AM Andre wrote:
> +1 on this + a template that matches existing additional.html
> On 8 Jun 2016 04:28, "Bryan Rosander" wrote:
>
> > Hey all,
> >
> > When writing documentation (e.g. the additionalDetails.html for a
> > processor) it would be nice to have the opti
+1 on this + a template that matches existing additional.html
On 8 Jun 2016 04:28, "Bryan Rosander" wrote:
> Hey all,
>
> When writing documentation (e.g. the additionalDetails.html for a
> processor) it would be nice to have the option to use Markdown instead of
> html.
>
> I think Markdown is e
Hey Oleg,
I would expect that we could match existing formatting and templates and
that Markdown files would result in more consistent html output than
everyone writing their own html by hand.
I agree though that we should make sure the look and feel can be made
consistent before moving forward.
Personally I am ok either way, however the question I have is consistency and
how different artifacts written via html will be different (look-and-feel) from
the once created using mark up and then transformed.
Oleg
> On Jun 7, 2016, at 2:28 PM, Bryan Rosander wrote:
>
> Hey all,
>
> When w
Hey all,
When writing documentation (e.g. the additionalDetails.html for a
processor) it would be nice to have the option to use Markdown instead of
html.
I think Markdown is easier to read and write than raw HTML and for simple
cases does the job pretty well. It also has the advantage of being
