Re: Linking the Wiki to the example Flows

On 12/04/2015 11:29 AM, Shane McCarron wrote:
> I think for static publication (gh-pages, TR space) we would want 
> static SVG files just like we don't want ReSpec processing to occur.

<bikeshed>

+1 for static SVG in TR space
+1 for static SVG in gh-pages date-stamped space
-1 for static SVG in gh-pages Editor's draft space

> I also think it is something we can put into a toolchain later.

Can't we data-include the SVG images in ReSpec?

Or *cough* find someone smart that knows ReSpec *looking at
Shane* that could add that feature?

> If you have a critical need right now I will spend a little time and
>  create something we can hook into github post-processing that will 
> automatically generate the SVG version whenever a pml is pushed or 
> something.  Would that help?

-1 for checking anything into Github that we don't have to. I don't
think we have to check in static copies of SVG or PNG files into Github
/unless/ we're creating date-stamped stuff. Even in that case, I think
our toolchain should just include the SVG inline for specs. PNGs should
be checked in only for date-stamped versions.

The general principle is - don't check stuff in we don't absolutely have to.

</bikeshed>

-- manu

-- 
Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
Founder/CEO - Digital Bazaar, Inc.
blog: Web Payments: The Architect, the Sage, and the Moral Voice
https://manu.sporny.org/2015/payments-collaboration/

Received on Monday, 7 December 2015 01:55:05 UTC