You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@xmlgraphics.apache.org by Chris Bowditch <bo...@hotmail.com> on 2012/04/17 10:19:59 UTC
Re: on changing fop documentation sources to markdown
On 15/04/2012 19:52, The Web Maestro wrote:
> I just added most of the nav for FOP Development (0.95, 1.0, trunk/
> and 'dev'):
Hi Clay,
>
> http://xmlgraphics.staging.apache.org/
>
> As mentioned, there are likely missing things (like java-docs,
> download.cgi, Batik's DEMO, etc.)... It'd be great if folks could take
> a look... I haven't figured out how to add other content, but It Might
> Just Work(tm) if weupload it there via SVN...
Many thanks for working on this.
>
> Come to think of it, we should probably move this to
> general@xmlgraphics.apache.org
> <ma...@xmlgraphics.apache.org>. Or is there a better mailing
> list? I'll refrain from sending to other lists, until we figure out
> where it should go.
>
> Any ideas where this discussion should move, since it entails changes
> to all XML Graphics Project web docs?
Yes this discussion should move to general@ as it will affect all sub
projects of XML Graphics.
Thanks,
Chris
>
> Kind regards,
>
> Clay Leeds
> --
> <the.webmaestro@gmail.com <ma...@gmail.com>> -
> <http://ourlil.com/>
> My religion is simple. My religion is kindness.
> - HH The 14th Dalai Lama of Tibet
>
>
> On Sat, Apr 14, 2012 at 11:53 PM, The Web Maestro
> <the.webmaestro@gmail.com <ma...@gmail.com>> wrote:
>
> I've updated the docs a bit, and gotten much (but not all!) of the
> FOP, Batik & Commons content into the CMS...
>
> We're still missing an adequate navigation system, so I did a
> preliminary job of getting a few links in the sidenav, but it's
> incomplete and ugly as sin. We'll need to build a mechanism to
> hide (collapse?) non-relevant links, but that shouldn't be too hard.
>
> We also need to figure out java-docs, download.cgi, and perhaps
> some other issues...
>
> Without further ado:
>
> http://xmlgraphics.staging.apache.org/
>
>
> Kind regards,
>
> Clay Leeds
> --
> <the.webmaestro@gmail.com <ma...@gmail.com>> -
> <http://ourlil.com/>
> My religion is simple. My religion is kindness.
> - HH The 14th Dalai Lama of Tibet
>
>
> On Thu, Apr 12, 2012 at 10:03 PM, Clay Leeds
> <the.webmaestro@gmail.com <ma...@gmail.com>> wrote:
>
> On Apr 12, 2012, at 6:41 AM, Glenn Adams <glenn@skynav.com
> <ma...@skynav.com>> wrote:
> > Agreed that removing forrest dependency is desirable.
> However, presumably the current xdocs would need to be
> converted to MD, in which case someone will need to construct
> an XSLT to do so. That begs the question of whether it would
> be necessary (at this time) to convert the source format to
> MD, or if an additional step in the CMS based process could
> merely perform that step automatically. If so, then it should
> not be necessary to change the authoring format at this time.
> It could be done as a separate step later.
>
> I am using Forrest 0.8 w markdown plugin. Conversion could be
> scripted, but that would negate the benefit of the CMS.
>
> > What I don't know yet is what we will lose from the
> conversion to MD in terms of ability to markup our source
> docs. Clearly, MD is not as semantically or syntactically rich
> as an XML based source. But do we lose anything of
> consequence? I don't know yet.
> >
> > One thing we may lose if we don't convert to MD is the
> ability to use CMS in-page editing. So that is a
> consideration. Perhaps that option is sufficient to justify
> other potential negatives in converting.
> >
> > G.
>
> One of my goals, was to see some discussion in the DEVers,
> before I complete the task of converting the docs. The
> MarkDown format is not nearly as semantic as xdoc, but it
> serves a different purpose.
>
> It'll take some time, and I'm still prepared to take it on.
> But I was hoping for some discussion ;-)
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org
Re: on changing fop documentation sources to markdown
Posted by The Web Maestro <th...@gmail.com>.
On Sat, Apr 21, 2012 at 9:42 AM, Clay Leeds <th...@gmail.com>wrote:
> On Apr 20, 2012, at 1:36 AM, Pascal Sancho <pa...@takoma.fr>
> wrote:
>
> But there has to be a better way. Can we, as a start, change the CSS file
> xmlgraphics.css so it doesn't have body {color: white;}?
>
> > Note that I have to be very patient when editing the (very long)
> compliance page directly, since it is rendered directly in the preview
> pane. Don't try it if your processor is a little out of age (;-|
>
> > [1] http://www.apache.org/dev/cmsref.html#markdown
>
> Thanks again for the assistance!
>
> Clay
I've committed a change to the CSS, which at least makes it black text on
white background (white on white is difficult to read unless you're a
wizard!).
We'll still need to figure out a solution for the coloring and such... We
should be able to come up with some solution... If nothing else, we could
always commit an HTML file, but we need to find a method to make it so the
CMS doesn't replace it or something silly...
Hand editing all the lines in that file just doesn't seem efficient!
Re: on changing fop documentation sources to markdown
Posted by The Web Maestro <th...@gmail.com>.
On Sat, Apr 21, 2012 at 9:42 AM, Clay Leeds <th...@gmail.com>wrote:
> On Apr 20, 2012, at 1:36 AM, Pascal Sancho <pa...@takoma.fr>
> wrote:
>
> But there has to be a better way. Can we, as a start, change the CSS file
> xmlgraphics.css so it doesn't have body {color: white;}?
>
> > Note that I have to be very patient when editing the (very long)
> compliance page directly, since it is rendered directly in the preview
> pane. Don't try it if your processor is a little out of age (;-|
>
> > [1] http://www.apache.org/dev/cmsref.html#markdown
>
> Thanks again for the assistance!
>
> Clay
I've committed a change to the CSS, which at least makes it black text on
white background (white on white is difficult to read unless you're a
wizard!).
We'll still need to figure out a solution for the coloring and such... We
should be able to come up with some solution... If nothing else, we could
always commit an HTML file, but we need to find a method to make it so the
CMS doesn't replace it or something silly...
Hand editing all the lines in that file just doesn't seem efficient!
Re: on changing fop documentation sources to markdown
Posted by The Web Maestro <th...@gmail.com>.
On Sat, Apr 21, 2012 at 9:42 AM, Clay Leeds <th...@gmail.com>wrote:
> On Apr 20, 2012, at 1:36 AM, Pascal Sancho <pa...@takoma.fr>
> wrote:
>
> But there has to be a better way. Can we, as a start, change the CSS file
> xmlgraphics.css so it doesn't have body {color: white;}?
>
> > Note that I have to be very patient when editing the (very long)
> compliance page directly, since it is rendered directly in the preview
> pane. Don't try it if your processor is a little out of age (;-|
>
> > [1] http://www.apache.org/dev/cmsref.html#markdown
>
> Thanks again for the assistance!
>
> Clay
I've committed a change to the CSS, which at least makes it black text on
white background (white on white is difficult to read unless you're a
wizard!).
We'll still need to figure out a solution for the coloring and such... We
should be able to come up with some solution... If nothing else, we could
always commit an HTML file, but we need to find a method to make it so the
CMS doesn't replace it or something silly...
Hand editing all the lines in that file just doesn't seem efficient!
Re: on changing fop documentation sources to markdown
Posted by Clay Leeds <th...@gmail.com>.
On Apr 20, 2012, at 1:36 AM, Pascal Sancho <pa...@takoma.fr> wrote:
> Hi,
>
> great job, Clay!
>
> I've looked at the compliance page closer, and it seems that rendering doesn't support markdown extras (like "table" or "headerid"), when it is said here [1] that such features are enabled for the CMS.
>
> As a workaround, we can insert html markup inside the markdown, I tried it successfully with the legend table (in the preview pane).
>
> In staging view, there is a CSS issue:
> xmlgraphics.css@17 > body {color: white;} is taken into acccount,
> regardless this rule:
> xmlgraphics.css@17 > #content {color: #333333;}
Wow! Nice work! It's nice to have help on this!
But there has to be a better way. Can we, as a start, change the CSS file xmlgraphics.css so it doesn't have body {color: white;}?
> Note that I have to be very patient when editing the (very long) compliance page directly, since it is rendered directly in the preview pane. Don't try it if your processor is a little out of age (;-|
> [1] http://www.apache.org/dev/cmsref.html#markdown
Thanks again for the assistance!
Clay
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org
Re: on changing fop documentation sources to markdown
Posted by Clay Leeds <th...@gmail.com>.
On Apr 20, 2012, at 1:36 AM, Pascal Sancho <pa...@takoma.fr> wrote:
> Hi,
>
> great job, Clay!
>
> I've looked at the compliance page closer, and it seems that rendering doesn't support markdown extras (like "table" or "headerid"), when it is said here [1] that such features are enabled for the CMS.
>
> As a workaround, we can insert html markup inside the markdown, I tried it successfully with the legend table (in the preview pane).
>
> In staging view, there is a CSS issue:
> xmlgraphics.css@17 > body {color: white;} is taken into acccount,
> regardless this rule:
> xmlgraphics.css@17 > #content {color: #333333;}
Wow! Nice work! It's nice to have help on this!
But there has to be a better way. Can we, as a start, change the CSS file xmlgraphics.css so it doesn't have body {color: white;}?
> Note that I have to be very patient when editing the (very long) compliance page directly, since it is rendered directly in the preview pane. Don't try it if your processor is a little out of age (;-|
> [1] http://www.apache.org/dev/cmsref.html#markdown
Thanks again for the assistance!
Clay
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org
Re: on changing fop documentation sources to markdown
Posted by Clay Leeds <th...@gmail.com>.
On Apr 20, 2012, at 1:36 AM, Pascal Sancho <pa...@takoma.fr> wrote:
> Hi,
>
> great job, Clay!
>
> I've looked at the compliance page closer, and it seems that rendering doesn't support markdown extras (like "table" or "headerid"), when it is said here [1] that such features are enabled for the CMS.
>
> As a workaround, we can insert html markup inside the markdown, I tried it successfully with the legend table (in the preview pane).
>
> In staging view, there is a CSS issue:
> xmlgraphics.css@17 > body {color: white;} is taken into acccount,
> regardless this rule:
> xmlgraphics.css@17 > #content {color: #333333;}
Wow! Nice work! It's nice to have help on this!
But there has to be a better way. Can we, as a start, change the CSS file xmlgraphics.css so it doesn't have body {color: white;}?
> Note that I have to be very patient when editing the (very long) compliance page directly, since it is rendered directly in the preview pane. Don't try it if your processor is a little out of age (;-|
> [1] http://www.apache.org/dev/cmsref.html#markdown
Thanks again for the assistance!
Clay
Re: on changing fop documentation sources to markdown
Posted by Pascal Sancho <pa...@takoma.fr>.
Hi,
great job, Clay!
I've looked at the compliance page closer, and it seems that rendering
doesn't support markdown extras (like "table" or "headerid"), when it is
said here [1] that such features are enabled for the CMS.
As a workaround, we can insert html markup inside the markdown, I tried
it successfully with the legend table (in the preview pane).
In staging view, there is a CSS issue:
xmlgraphics.css@17 > body {color: white;} is taken into acccount,
regardless this rule:
xmlgraphics.css@17 > #content {color: #333333;}
Note that I have to be very patient when editing the (very long)
compliance page directly, since it is rendered directly in the preview
pane. Don't try it if your processor is a little out of age (;-|
[1] http://www.apache.org/dev/cmsref.html#markdown
Le 20/04/2012 04:43, The Web Maestro a écrit :
> On Thu, Apr 19, 2012 at 12:40 AM, Chris Bowditch
> <bowditch_chris@hotmail.com <ma...@hotmail.com>> wrote:
>
> On 19/04/2012 02:02, Clay Leeds wrote:
>
> I replaced the logo for all sites a month or so ago.
>
>
> Thanks Clay - I can see the new logo fine. I was referring to the
> "TM" characters in the text. I can see it everywhere except the top
> level XML Graphics home page, which is a page I definitely changed.
>
>
> Sorry, thought you were talking about the graphic. I fixed the text.
>
> BTW, it's pretty easy for anyone to edit with the CMS now. Here's the
> Apache CMS Reference:
>
> http://www.apache.org/dev/cmsref.html
>
> That will give you a bookmarklet you can use to edit any STAGING page:
>
> Here's your starting point for the XML Graphics Staging site:
>
> http://xmlgraphics.staging.apache.org/
>
> Once we're good to go, anyone will also be able to start editing the
> markdown files themselves...
--
Pascal
Re: on changing fop documentation sources to markdown
Posted by The Web Maestro <th...@gmail.com>.
On Thu, Apr 19, 2012 at 12:40 AM, Chris Bowditch <bowditch_chris@hotmail.com
> wrote:
> On 19/04/2012 02:02, Clay Leeds wrote:
>
>> I replaced the logo for all sites a month or so ago.
>>
>
> Thanks Clay - I can see the new logo fine. I was referring to the "TM"
> characters in the text. I can see it everywhere except the top level XML
> Graphics home page, which is a page I definitely changed.
Sorry, thought you were talking about the graphic. I fixed the text.
BTW, it's pretty easy for anyone to edit with the CMS now. Here's the
Apache CMS Reference:
http://www.apache.org/dev/cmsref.html
That will give you a bookmarklet you can use to edit any STAGING page:
Here's your starting point for the XML Graphics Staging site:
http://xmlgraphics.staging.apache.org/
Once we're good to go, anyone will also be able to start editing the
markdown files themselves...
Cheers!
Clay
Re: on changing fop documentation sources to markdown
Posted by The Web Maestro <th...@gmail.com>.
On Thu, Apr 19, 2012 at 12:40 AM, Chris Bowditch <bowditch_chris@hotmail.com
> wrote:
> On 19/04/2012 02:02, Clay Leeds wrote:
>
>> I replaced the logo for all sites a month or so ago.
>>
>
> Thanks Clay - I can see the new logo fine. I was referring to the "TM"
> characters in the text. I can see it everywhere except the top level XML
> Graphics home page, which is a page I definitely changed.
Sorry, thought you were talking about the graphic. I fixed the text.
BTW, it's pretty easy for anyone to edit with the CMS now. Here's the
Apache CMS Reference:
http://www.apache.org/dev/cmsref.html
That will give you a bookmarklet you can use to edit any STAGING page:
Here's your starting point for the XML Graphics Staging site:
http://xmlgraphics.staging.apache.org/
Once we're good to go, anyone will also be able to start editing the
markdown files themselves...
Cheers!
Clay
Re: on changing fop documentation sources to markdown
Posted by The Web Maestro <th...@gmail.com>.
On Thu, Apr 19, 2012 at 12:40 AM, Chris Bowditch <bowditch_chris@hotmail.com
> wrote:
> On 19/04/2012 02:02, Clay Leeds wrote:
>
>> I replaced the logo for all sites a month or so ago.
>>
>
> Thanks Clay - I can see the new logo fine. I was referring to the "TM"
> characters in the text. I can see it everywhere except the top level XML
> Graphics home page, which is a page I definitely changed.
Sorry, thought you were talking about the graphic. I fixed the text.
BTW, it's pretty easy for anyone to edit with the CMS now. Here's the
Apache CMS Reference:
http://www.apache.org/dev/cmsref.html
That will give you a bookmarklet you can use to edit any STAGING page:
Here's your starting point for the XML Graphics Staging site:
http://xmlgraphics.staging.apache.org/
Once we're good to go, anyone will also be able to start editing the
markdown files themselves...
Cheers!
Clay
Re: on changing fop documentation sources to markdown
Posted by Chris Bowditch <bo...@hotmail.com>.
On 19/04/2012 02:02, Clay Leeds wrote:
> I replaced the logo for all sites a month or so ago.
Thanks Clay - I can see the new logo fine. I was referring to the "TM"
characters in the text. I can see it everywhere except the top level XML
Graphics home page, which is a page I definitely changed.
>
> I'm not at a place I can publish, but if someone can publish the PRODUCTION sites, the logo will show up (be sure to clear cache!).
Cache definitely cleared. I know its only 1 page, but since its the top
page it's important that it adheres to Apache Branding rules.
Thanks,
Chris
>
> Clay
>
> "My religion is simple. My religion is kindness."
> - HH The Dalai Lama of Tibet
>
> On Apr 18, 2012, at 7:09 AM, Chris Bowditch<bo...@hotmail.com> wrote:
>
>> On 18/04/2012 13:52, Clay Leeds wrote:
>>> On Apr 18, 2012, at 5:12 AM, Chris Bowditch<bo...@hotmail.com> wrote:
>>>> On 18/04/2012 07:24, The Web Maestro wrote:
>>>>
>>>> Hi Clay,
>>>>
>>>>> I added the logo (in GIF, JPG, PNG& SVG formats... ;-)
>>>> Thanks, but I don't yet see it on the staging website. Is there a delay before that appears?
>> Hi Clay,
>>
>>> Strange. The new logo showed up when I refreshed it. Perhaps it's your cache? Try loading only the logo.
>> Yes you are right. It was my browser cache. I can now see the updated logo.
>>
>>>>> Sponsorship& Thanks were already there. License is on the Legal page, which is there, but I've added it to the sidebar as well, along with the Security page. ;-)
>>>> Thanks. I can now see the 4 required links.
>>>>
>>>>> I also got the Compliance table working. Unfortunately, the CMS is stripping the 'class="ForrestTable"', so the coloring is White-On-White (but if you select the text, you'll see the content and layout is there).
>>>>>
>>>>> As for the navigation menu, I'd like it to collapse most of the links, except the section you're in. Anyone have a favorite jQuery menu they like for this? If not, I'll see about finding one...
>>>> All the "TM" logos are missing from the content and headers though. It took me quite some time to add them to all the pages. Will you be able to re-sync the content with the latest xdocs as it would take quite some time to re-apply them and I want to tell the board that FOP, Commons and XML Graphics sites are now brand compliant in the upcoming report.
>>> The current LIVE site has it, so we should be good informing the board it's there, no?
>>>
>>> Weird. When I added the content, I did an `svn up` to ensure it was recent content. I'm sure I'll have to re-synch, anyway, so we'll see. I wish it were a caching thing!
>> I can see the TM logos in most of the content after clearing the cache. Just the XML Graphics top page doesn't appear to have them now.
>>
>> Thanks,
>>
>> Chris
>>
>>>> Thanks,
>>>>
>>>> Chris
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: general-help@xmlgraphics.apache.org
>
>
>
Re: on changing fop documentation sources to markdown
Posted by Chris Bowditch <bo...@hotmail.com>.
On 19/04/2012 02:02, Clay Leeds wrote:
> I replaced the logo for all sites a month or so ago.
Thanks Clay - I can see the new logo fine. I was referring to the "TM"
characters in the text. I can see it everywhere except the top level XML
Graphics home page, which is a page I definitely changed.
>
> I'm not at a place I can publish, but if someone can publish the PRODUCTION sites, the logo will show up (be sure to clear cache!).
Cache definitely cleared. I know its only 1 page, but since its the top
page it's important that it adheres to Apache Branding rules.
Thanks,
Chris
>
> Clay
>
> "My religion is simple. My religion is kindness."
> - HH The Dalai Lama of Tibet
>
> On Apr 18, 2012, at 7:09 AM, Chris Bowditch<bo...@hotmail.com> wrote:
>
>> On 18/04/2012 13:52, Clay Leeds wrote:
>>> On Apr 18, 2012, at 5:12 AM, Chris Bowditch<bo...@hotmail.com> wrote:
>>>> On 18/04/2012 07:24, The Web Maestro wrote:
>>>>
>>>> Hi Clay,
>>>>
>>>>> I added the logo (in GIF, JPG, PNG& SVG formats... ;-)
>>>> Thanks, but I don't yet see it on the staging website. Is there a delay before that appears?
>> Hi Clay,
>>
>>> Strange. The new logo showed up when I refreshed it. Perhaps it's your cache? Try loading only the logo.
>> Yes you are right. It was my browser cache. I can now see the updated logo.
>>
>>>>> Sponsorship& Thanks were already there. License is on the Legal page, which is there, but I've added it to the sidebar as well, along with the Security page. ;-)
>>>> Thanks. I can now see the 4 required links.
>>>>
>>>>> I also got the Compliance table working. Unfortunately, the CMS is stripping the 'class="ForrestTable"', so the coloring is White-On-White (but if you select the text, you'll see the content and layout is there).
>>>>>
>>>>> As for the navigation menu, I'd like it to collapse most of the links, except the section you're in. Anyone have a favorite jQuery menu they like for this? If not, I'll see about finding one...
>>>> All the "TM" logos are missing from the content and headers though. It took me quite some time to add them to all the pages. Will you be able to re-sync the content with the latest xdocs as it would take quite some time to re-apply them and I want to tell the board that FOP, Commons and XML Graphics sites are now brand compliant in the upcoming report.
>>> The current LIVE site has it, so we should be good informing the board it's there, no?
>>>
>>> Weird. When I added the content, I did an `svn up` to ensure it was recent content. I'm sure I'll have to re-synch, anyway, so we'll see. I wish it were a caching thing!
>> I can see the TM logos in most of the content after clearing the cache. Just the XML Graphics top page doesn't appear to have them now.
>>
>> Thanks,
>>
>> Chris
>>
>>>> Thanks,
>>>>
>>>> Chris
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: general-help@xmlgraphics.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org
Re: on changing fop documentation sources to markdown
Posted by Chris Bowditch <bo...@hotmail.com>.
On 19/04/2012 02:02, Clay Leeds wrote:
> I replaced the logo for all sites a month or so ago.
Thanks Clay - I can see the new logo fine. I was referring to the "TM"
characters in the text. I can see it everywhere except the top level XML
Graphics home page, which is a page I definitely changed.
>
> I'm not at a place I can publish, but if someone can publish the PRODUCTION sites, the logo will show up (be sure to clear cache!).
Cache definitely cleared. I know its only 1 page, but since its the top
page it's important that it adheres to Apache Branding rules.
Thanks,
Chris
>
> Clay
>
> "My religion is simple. My religion is kindness."
> - HH The Dalai Lama of Tibet
>
> On Apr 18, 2012, at 7:09 AM, Chris Bowditch<bo...@hotmail.com> wrote:
>
>> On 18/04/2012 13:52, Clay Leeds wrote:
>>> On Apr 18, 2012, at 5:12 AM, Chris Bowditch<bo...@hotmail.com> wrote:
>>>> On 18/04/2012 07:24, The Web Maestro wrote:
>>>>
>>>> Hi Clay,
>>>>
>>>>> I added the logo (in GIF, JPG, PNG& SVG formats... ;-)
>>>> Thanks, but I don't yet see it on the staging website. Is there a delay before that appears?
>> Hi Clay,
>>
>>> Strange. The new logo showed up when I refreshed it. Perhaps it's your cache? Try loading only the logo.
>> Yes you are right. It was my browser cache. I can now see the updated logo.
>>
>>>>> Sponsorship& Thanks were already there. License is on the Legal page, which is there, but I've added it to the sidebar as well, along with the Security page. ;-)
>>>> Thanks. I can now see the 4 required links.
>>>>
>>>>> I also got the Compliance table working. Unfortunately, the CMS is stripping the 'class="ForrestTable"', so the coloring is White-On-White (but if you select the text, you'll see the content and layout is there).
>>>>>
>>>>> As for the navigation menu, I'd like it to collapse most of the links, except the section you're in. Anyone have a favorite jQuery menu they like for this? If not, I'll see about finding one...
>>>> All the "TM" logos are missing from the content and headers though. It took me quite some time to add them to all the pages. Will you be able to re-sync the content with the latest xdocs as it would take quite some time to re-apply them and I want to tell the board that FOP, Commons and XML Graphics sites are now brand compliant in the upcoming report.
>>> The current LIVE site has it, so we should be good informing the board it's there, no?
>>>
>>> Weird. When I added the content, I did an `svn up` to ensure it was recent content. I'm sure I'll have to re-synch, anyway, so we'll see. I wish it were a caching thing!
>> I can see the TM logos in most of the content after clearing the cache. Just the XML Graphics top page doesn't appear to have them now.
>>
>> Thanks,
>>
>> Chris
>>
>>>> Thanks,
>>>>
>>>> Chris
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: general-help@xmlgraphics.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org
Re: on changing fop documentation sources to markdown
Posted by Clay Leeds <th...@gmail.com>.
I replaced the logo for all sites a month or so ago.
I'm not at a place I can publish, but if someone can publish the PRODUCTION sites, the logo will show up (be sure to clear cache!).
Clay
"My religion is simple. My religion is kindness."
- HH The Dalai Lama of Tibet
On Apr 18, 2012, at 7:09 AM, Chris Bowditch <bo...@hotmail.com> wrote:
> On 18/04/2012 13:52, Clay Leeds wrote:
>> On Apr 18, 2012, at 5:12 AM, Chris Bowditch<bo...@hotmail.com> wrote:
>>> On 18/04/2012 07:24, The Web Maestro wrote:
>>>
>>> Hi Clay,
>>>
>>>> I added the logo (in GIF, JPG, PNG& SVG formats... ;-)
>>> Thanks, but I don't yet see it on the staging website. Is there a delay before that appears?
>
> Hi Clay,
>
>> Strange. The new logo showed up when I refreshed it. Perhaps it's your cache? Try loading only the logo.
>
> Yes you are right. It was my browser cache. I can now see the updated logo.
>
>>
>>>> Sponsorship& Thanks were already there. License is on the Legal page, which is there, but I've added it to the sidebar as well, along with the Security page. ;-)
>>> Thanks. I can now see the 4 required links.
>>>
>>>> I also got the Compliance table working. Unfortunately, the CMS is stripping the 'class="ForrestTable"', so the coloring is White-On-White (but if you select the text, you'll see the content and layout is there).
>>>>
>>>> As for the navigation menu, I'd like it to collapse most of the links, except the section you're in. Anyone have a favorite jQuery menu they like for this? If not, I'll see about finding one...
>>> All the "TM" logos are missing from the content and headers though. It took me quite some time to add them to all the pages. Will you be able to re-sync the content with the latest xdocs as it would take quite some time to re-apply them and I want to tell the board that FOP, Commons and XML Graphics sites are now brand compliant in the upcoming report.
>> The current LIVE site has it, so we should be good informing the board it's there, no?
>>
>> Weird. When I added the content, I did an `svn up` to ensure it was recent content. I'm sure I'll have to re-synch, anyway, so we'll see. I wish it were a caching thing!
>
> I can see the TM logos in most of the content after clearing the cache. Just the XML Graphics top page doesn't appear to have them now.
>
> Thanks,
>
> Chris
>
>>
>>> Thanks,
>>>
>>> Chris
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org
Re: on changing fop documentation sources to markdown
Posted by Clay Leeds <th...@gmail.com>.
I replaced the logo for all sites a month or so ago.
I'm not at a place I can publish, but if someone can publish the PRODUCTION sites, the logo will show up (be sure to clear cache!).
Clay
"My religion is simple. My religion is kindness."
- HH The Dalai Lama of Tibet
On Apr 18, 2012, at 7:09 AM, Chris Bowditch <bo...@hotmail.com> wrote:
> On 18/04/2012 13:52, Clay Leeds wrote:
>> On Apr 18, 2012, at 5:12 AM, Chris Bowditch<bo...@hotmail.com> wrote:
>>> On 18/04/2012 07:24, The Web Maestro wrote:
>>>
>>> Hi Clay,
>>>
>>>> I added the logo (in GIF, JPG, PNG& SVG formats... ;-)
>>> Thanks, but I don't yet see it on the staging website. Is there a delay before that appears?
>
> Hi Clay,
>
>> Strange. The new logo showed up when I refreshed it. Perhaps it's your cache? Try loading only the logo.
>
> Yes you are right. It was my browser cache. I can now see the updated logo.
>
>>
>>>> Sponsorship& Thanks were already there. License is on the Legal page, which is there, but I've added it to the sidebar as well, along with the Security page. ;-)
>>> Thanks. I can now see the 4 required links.
>>>
>>>> I also got the Compliance table working. Unfortunately, the CMS is stripping the 'class="ForrestTable"', so the coloring is White-On-White (but if you select the text, you'll see the content and layout is there).
>>>>
>>>> As for the navigation menu, I'd like it to collapse most of the links, except the section you're in. Anyone have a favorite jQuery menu they like for this? If not, I'll see about finding one...
>>> All the "TM" logos are missing from the content and headers though. It took me quite some time to add them to all the pages. Will you be able to re-sync the content with the latest xdocs as it would take quite some time to re-apply them and I want to tell the board that FOP, Commons and XML Graphics sites are now brand compliant in the upcoming report.
>> The current LIVE site has it, so we should be good informing the board it's there, no?
>>
>> Weird. When I added the content, I did an `svn up` to ensure it was recent content. I'm sure I'll have to re-synch, anyway, so we'll see. I wish it were a caching thing!
>
> I can see the TM logos in most of the content after clearing the cache. Just the XML Graphics top page doesn't appear to have them now.
>
> Thanks,
>
> Chris
>
>>
>>> Thanks,
>>>
>>> Chris
>>
>
Re: on changing fop documentation sources to markdown
Posted by Clay Leeds <th...@gmail.com>.
I replaced the logo for all sites a month or so ago.
I'm not at a place I can publish, but if someone can publish the PRODUCTION sites, the logo will show up (be sure to clear cache!).
Clay
"My religion is simple. My religion is kindness."
- HH The Dalai Lama of Tibet
On Apr 18, 2012, at 7:09 AM, Chris Bowditch <bo...@hotmail.com> wrote:
> On 18/04/2012 13:52, Clay Leeds wrote:
>> On Apr 18, 2012, at 5:12 AM, Chris Bowditch<bo...@hotmail.com> wrote:
>>> On 18/04/2012 07:24, The Web Maestro wrote:
>>>
>>> Hi Clay,
>>>
>>>> I added the logo (in GIF, JPG, PNG& SVG formats... ;-)
>>> Thanks, but I don't yet see it on the staging website. Is there a delay before that appears?
>
> Hi Clay,
>
>> Strange. The new logo showed up when I refreshed it. Perhaps it's your cache? Try loading only the logo.
>
> Yes you are right. It was my browser cache. I can now see the updated logo.
>
>>
>>>> Sponsorship& Thanks were already there. License is on the Legal page, which is there, but I've added it to the sidebar as well, along with the Security page. ;-)
>>> Thanks. I can now see the 4 required links.
>>>
>>>> I also got the Compliance table working. Unfortunately, the CMS is stripping the 'class="ForrestTable"', so the coloring is White-On-White (but if you select the text, you'll see the content and layout is there).
>>>>
>>>> As for the navigation menu, I'd like it to collapse most of the links, except the section you're in. Anyone have a favorite jQuery menu they like for this? If not, I'll see about finding one...
>>> All the "TM" logos are missing from the content and headers though. It took me quite some time to add them to all the pages. Will you be able to re-sync the content with the latest xdocs as it would take quite some time to re-apply them and I want to tell the board that FOP, Commons and XML Graphics sites are now brand compliant in the upcoming report.
>> The current LIVE site has it, so we should be good informing the board it's there, no?
>>
>> Weird. When I added the content, I did an `svn up` to ensure it was recent content. I'm sure I'll have to re-synch, anyway, so we'll see. I wish it were a caching thing!
>
> I can see the TM logos in most of the content after clearing the cache. Just the XML Graphics top page doesn't appear to have them now.
>
> Thanks,
>
> Chris
>
>>
>>> Thanks,
>>>
>>> Chris
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org
Re: on changing fop documentation sources to markdown
Posted by Chris Bowditch <bo...@hotmail.com>.
On 18/04/2012 13:52, Clay Leeds wrote:
> On Apr 18, 2012, at 5:12 AM, Chris Bowditch<bo...@hotmail.com> wrote:
>> On 18/04/2012 07:24, The Web Maestro wrote:
>>
>> Hi Clay,
>>
>>> I added the logo (in GIF, JPG, PNG& SVG formats... ;-)
>> Thanks, but I don't yet see it on the staging website. Is there a delay before that appears?
Hi Clay,
> Strange. The new logo showed up when I refreshed it. Perhaps it's your cache? Try loading only the logo.
Yes you are right. It was my browser cache. I can now see the updated logo.
>
>>> Sponsorship& Thanks were already there. License is on the Legal page, which is there, but I've added it to the sidebar as well, along with the Security page. ;-)
>> Thanks. I can now see the 4 required links.
>>
>>> I also got the Compliance table working. Unfortunately, the CMS is stripping the 'class="ForrestTable"', so the coloring is White-On-White (but if you select the text, you'll see the content and layout is there).
>>>
>>> As for the navigation menu, I'd like it to collapse most of the links, except the section you're in. Anyone have a favorite jQuery menu they like for this? If not, I'll see about finding one...
>> All the "TM" logos are missing from the content and headers though. It took me quite some time to add them to all the pages. Will you be able to re-sync the content with the latest xdocs as it would take quite some time to re-apply them and I want to tell the board that FOP, Commons and XML Graphics sites are now brand compliant in the upcoming report.
> The current LIVE site has it, so we should be good informing the board it's there, no?
>
> Weird. When I added the content, I did an `svn up` to ensure it was recent content. I'm sure I'll have to re-synch, anyway, so we'll see. I wish it were a caching thing!
I can see the TM logos in most of the content after clearing the cache.
Just the XML Graphics top page doesn't appear to have them now.
Thanks,
Chris
>
>> Thanks,
>>
>> Chris
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org
Re: on changing fop documentation sources to markdown
Posted by Chris Bowditch <bo...@hotmail.com>.
On 18/04/2012 13:52, Clay Leeds wrote:
> On Apr 18, 2012, at 5:12 AM, Chris Bowditch<bo...@hotmail.com> wrote:
>> On 18/04/2012 07:24, The Web Maestro wrote:
>>
>> Hi Clay,
>>
>>> I added the logo (in GIF, JPG, PNG& SVG formats... ;-)
>> Thanks, but I don't yet see it on the staging website. Is there a delay before that appears?
Hi Clay,
> Strange. The new logo showed up when I refreshed it. Perhaps it's your cache? Try loading only the logo.
Yes you are right. It was my browser cache. I can now see the updated logo.
>
>>> Sponsorship& Thanks were already there. License is on the Legal page, which is there, but I've added it to the sidebar as well, along with the Security page. ;-)
>> Thanks. I can now see the 4 required links.
>>
>>> I also got the Compliance table working. Unfortunately, the CMS is stripping the 'class="ForrestTable"', so the coloring is White-On-White (but if you select the text, you'll see the content and layout is there).
>>>
>>> As for the navigation menu, I'd like it to collapse most of the links, except the section you're in. Anyone have a favorite jQuery menu they like for this? If not, I'll see about finding one...
>> All the "TM" logos are missing from the content and headers though. It took me quite some time to add them to all the pages. Will you be able to re-sync the content with the latest xdocs as it would take quite some time to re-apply them and I want to tell the board that FOP, Commons and XML Graphics sites are now brand compliant in the upcoming report.
> The current LIVE site has it, so we should be good informing the board it's there, no?
>
> Weird. When I added the content, I did an `svn up` to ensure it was recent content. I'm sure I'll have to re-synch, anyway, so we'll see. I wish it were a caching thing!
I can see the TM logos in most of the content after clearing the cache.
Just the XML Graphics top page doesn't appear to have them now.
Thanks,
Chris
>
>> Thanks,
>>
>> Chris
>
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org
Re: on changing fop documentation sources to markdown
Posted by Chris Bowditch <bo...@hotmail.com>.
On 18/04/2012 13:52, Clay Leeds wrote:
> On Apr 18, 2012, at 5:12 AM, Chris Bowditch<bo...@hotmail.com> wrote:
>> On 18/04/2012 07:24, The Web Maestro wrote:
>>
>> Hi Clay,
>>
>>> I added the logo (in GIF, JPG, PNG& SVG formats... ;-)
>> Thanks, but I don't yet see it on the staging website. Is there a delay before that appears?
Hi Clay,
> Strange. The new logo showed up when I refreshed it. Perhaps it's your cache? Try loading only the logo.
Yes you are right. It was my browser cache. I can now see the updated logo.
>
>>> Sponsorship& Thanks were already there. License is on the Legal page, which is there, but I've added it to the sidebar as well, along with the Security page. ;-)
>> Thanks. I can now see the 4 required links.
>>
>>> I also got the Compliance table working. Unfortunately, the CMS is stripping the 'class="ForrestTable"', so the coloring is White-On-White (but if you select the text, you'll see the content and layout is there).
>>>
>>> As for the navigation menu, I'd like it to collapse most of the links, except the section you're in. Anyone have a favorite jQuery menu they like for this? If not, I'll see about finding one...
>> All the "TM" logos are missing from the content and headers though. It took me quite some time to add them to all the pages. Will you be able to re-sync the content with the latest xdocs as it would take quite some time to re-apply them and I want to tell the board that FOP, Commons and XML Graphics sites are now brand compliant in the upcoming report.
> The current LIVE site has it, so we should be good informing the board it's there, no?
>
> Weird. When I added the content, I did an `svn up` to ensure it was recent content. I'm sure I'll have to re-synch, anyway, so we'll see. I wish it were a caching thing!
I can see the TM logos in most of the content after clearing the cache.
Just the XML Graphics top page doesn't appear to have them now.
Thanks,
Chris
>
>> Thanks,
>>
>> Chris
>
Re: on changing fop documentation sources to markdown
Posted by Clay Leeds <th...@gmail.com>.
On Apr 18, 2012, at 5:12 AM, Chris Bowditch <bo...@hotmail.com> wrote:
> On 18/04/2012 07:24, The Web Maestro wrote:
>
> Hi Clay,
>
>> I added the logo (in GIF, JPG, PNG & SVG formats... ;-)
>
> Thanks, but I don't yet see it on the staging website. Is there a delay before that appears?
Strange. The new logo showed up when I refreshed it. Perhaps it's your cache? Try loading only the logo.
>> Sponsorship & Thanks were already there. License is on the Legal page, which is there, but I've added it to the sidebar as well, along with the Security page. ;-)
>
> Thanks. I can now see the 4 required links.
>
>> I also got the Compliance table working. Unfortunately, the CMS is stripping the 'class="ForrestTable"', so the coloring is White-On-White (but if you select the text, you'll see the content and layout is there).
>>
>> As for the navigation menu, I'd like it to collapse most of the links, except the section you're in. Anyone have a favorite jQuery menu they like for this? If not, I'll see about finding one...
>
> All the "TM" logos are missing from the content and headers though. It took me quite some time to add them to all the pages. Will you be able to re-sync the content with the latest xdocs as it would take quite some time to re-apply them and I want to tell the board that FOP, Commons and XML Graphics sites are now brand compliant in the upcoming report.
The current LIVE site has it, so we should be good informing the board it's there, no?
Weird. When I added the content, I did an `svn up` to ensure it was recent content. I'm sure I'll have to re-synch, anyway, so we'll see. I wish it were a caching thing!
> Thanks,
>
> Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org
Re: on changing fop documentation sources to markdown
Posted by Clay Leeds <th...@gmail.com>.
On Apr 18, 2012, at 5:12 AM, Chris Bowditch <bo...@hotmail.com> wrote:
> On 18/04/2012 07:24, The Web Maestro wrote:
>
> Hi Clay,
>
>> I added the logo (in GIF, JPG, PNG & SVG formats... ;-)
>
> Thanks, but I don't yet see it on the staging website. Is there a delay before that appears?
Strange. The new logo showed up when I refreshed it. Perhaps it's your cache? Try loading only the logo.
>> Sponsorship & Thanks were already there. License is on the Legal page, which is there, but I've added it to the sidebar as well, along with the Security page. ;-)
>
> Thanks. I can now see the 4 required links.
>
>> I also got the Compliance table working. Unfortunately, the CMS is stripping the 'class="ForrestTable"', so the coloring is White-On-White (but if you select the text, you'll see the content and layout is there).
>>
>> As for the navigation menu, I'd like it to collapse most of the links, except the section you're in. Anyone have a favorite jQuery menu they like for this? If not, I'll see about finding one...
>
> All the "TM" logos are missing from the content and headers though. It took me quite some time to add them to all the pages. Will you be able to re-sync the content with the latest xdocs as it would take quite some time to re-apply them and I want to tell the board that FOP, Commons and XML Graphics sites are now brand compliant in the upcoming report.
The current LIVE site has it, so we should be good informing the board it's there, no?
Weird. When I added the content, I did an `svn up` to ensure it was recent content. I'm sure I'll have to re-synch, anyway, so we'll see. I wish it were a caching thing!
> Thanks,
>
> Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org
Re: on changing fop documentation sources to markdown
Posted by Clay Leeds <th...@gmail.com>.
On Apr 18, 2012, at 5:12 AM, Chris Bowditch <bo...@hotmail.com> wrote:
> On 18/04/2012 07:24, The Web Maestro wrote:
>
> Hi Clay,
>
>> I added the logo (in GIF, JPG, PNG & SVG formats... ;-)
>
> Thanks, but I don't yet see it on the staging website. Is there a delay before that appears?
Strange. The new logo showed up when I refreshed it. Perhaps it's your cache? Try loading only the logo.
>> Sponsorship & Thanks were already there. License is on the Legal page, which is there, but I've added it to the sidebar as well, along with the Security page. ;-)
>
> Thanks. I can now see the 4 required links.
>
>> I also got the Compliance table working. Unfortunately, the CMS is stripping the 'class="ForrestTable"', so the coloring is White-On-White (but if you select the text, you'll see the content and layout is there).
>>
>> As for the navigation menu, I'd like it to collapse most of the links, except the section you're in. Anyone have a favorite jQuery menu they like for this? If not, I'll see about finding one...
>
> All the "TM" logos are missing from the content and headers though. It took me quite some time to add them to all the pages. Will you be able to re-sync the content with the latest xdocs as it would take quite some time to re-apply them and I want to tell the board that FOP, Commons and XML Graphics sites are now brand compliant in the upcoming report.
The current LIVE site has it, so we should be good informing the board it's there, no?
Weird. When I added the content, I did an `svn up` to ensure it was recent content. I'm sure I'll have to re-synch, anyway, so we'll see. I wish it were a caching thing!
> Thanks,
>
> Chris
Re: on changing fop documentation sources to markdown
Posted by Chris Bowditch <bo...@hotmail.com>.
On 18/04/2012 07:24, The Web Maestro wrote:
Hi Clay,
> On Tue, Apr 17, 2012 at 7:52 AM, Chris Bowditch
> <bowditch_chris@hotmail.com <ma...@hotmail.com>> wrote:
>
> BACKGROUND:
> We are discussing moving XML Graphics web site to ASF-CMS. You
> can see progress here:
>
> http://xmlgraphics.staging.apache.org/
>
>
> I realize its work in progress but it appears like you used an old
> snapshot without the "TM" marks in the content or the new logo
> that you designed. Also the links need to include License,
> Sponsorship, Thanks and Security as per the branding guidelines.
> This content is now live on the main site, so I guess you just
> started with a snapshot from a few weeks ago?
>
>
> I added the logo (in GIF, JPG, PNG & SVG formats... ;-)
Thanks, but I don't yet see it on the staging website. Is there a delay
before that appears?
>
> Sponsorship & Thanks were already there. License is on the Legal page,
> which is there, but I've added it to the sidebar as well, along with
> the Security page. ;-)
Thanks. I can now see the 4 required links.
>
> I also got the Compliance table working. Unfortunately, the CMS is
> stripping the 'class="ForrestTable"', so the coloring is
> White-On-White (but if you select the text, you'll see the content and
> layout is there).
>
> As for the navigation menu, I'd like it to collapse most of the links,
> except the section you're in. Anyone have a favorite jQuery menu they
> like for this? If not, I'll see about finding one...
All the "TM" logos are missing from the content and headers though. It
took me quite some time to add them to all the pages. Will you be able
to re-sync the content with the latest xdocs as it would take quite some
time to re-apply them and I want to tell the board that FOP, Commons and
XML Graphics sites are now brand compliant in the upcoming report.
Thanks,
Chris
>
> Clay
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org
Re: on changing fop documentation sources to markdown
Posted by Chris Bowditch <bo...@hotmail.com>.
On 18/04/2012 07:24, The Web Maestro wrote:
Hi Clay,
> On Tue, Apr 17, 2012 at 7:52 AM, Chris Bowditch
> <bowditch_chris@hotmail.com <ma...@hotmail.com>> wrote:
>
> BACKGROUND:
> We are discussing moving XML Graphics web site to ASF-CMS. You
> can see progress here:
>
> http://xmlgraphics.staging.apache.org/
>
>
> I realize its work in progress but it appears like you used an old
> snapshot without the "TM" marks in the content or the new logo
> that you designed. Also the links need to include License,
> Sponsorship, Thanks and Security as per the branding guidelines.
> This content is now live on the main site, so I guess you just
> started with a snapshot from a few weeks ago?
>
>
> I added the logo (in GIF, JPG, PNG & SVG formats... ;-)
Thanks, but I don't yet see it on the staging website. Is there a delay
before that appears?
>
> Sponsorship & Thanks were already there. License is on the Legal page,
> which is there, but I've added it to the sidebar as well, along with
> the Security page. ;-)
Thanks. I can now see the 4 required links.
>
> I also got the Compliance table working. Unfortunately, the CMS is
> stripping the 'class="ForrestTable"', so the coloring is
> White-On-White (but if you select the text, you'll see the content and
> layout is there).
>
> As for the navigation menu, I'd like it to collapse most of the links,
> except the section you're in. Anyone have a favorite jQuery menu they
> like for this? If not, I'll see about finding one...
All the "TM" logos are missing from the content and headers though. It
took me quite some time to add them to all the pages. Will you be able
to re-sync the content with the latest xdocs as it would take quite some
time to re-apply them and I want to tell the board that FOP, Commons and
XML Graphics sites are now brand compliant in the upcoming report.
Thanks,
Chris
>
> Clay
Re: on changing fop documentation sources to markdown
Posted by Chris Bowditch <bo...@hotmail.com>.
On 18/04/2012 07:24, The Web Maestro wrote:
Hi Clay,
> On Tue, Apr 17, 2012 at 7:52 AM, Chris Bowditch
> <bowditch_chris@hotmail.com <ma...@hotmail.com>> wrote:
>
> BACKGROUND:
> We are discussing moving XML Graphics web site to ASF-CMS. You
> can see progress here:
>
> http://xmlgraphics.staging.apache.org/
>
>
> I realize its work in progress but it appears like you used an old
> snapshot without the "TM" marks in the content or the new logo
> that you designed. Also the links need to include License,
> Sponsorship, Thanks and Security as per the branding guidelines.
> This content is now live on the main site, so I guess you just
> started with a snapshot from a few weeks ago?
>
>
> I added the logo (in GIF, JPG, PNG & SVG formats... ;-)
Thanks, but I don't yet see it on the staging website. Is there a delay
before that appears?
>
> Sponsorship & Thanks were already there. License is on the Legal page,
> which is there, but I've added it to the sidebar as well, along with
> the Security page. ;-)
Thanks. I can now see the 4 required links.
>
> I also got the Compliance table working. Unfortunately, the CMS is
> stripping the 'class="ForrestTable"', so the coloring is
> White-On-White (but if you select the text, you'll see the content and
> layout is there).
>
> As for the navigation menu, I'd like it to collapse most of the links,
> except the section you're in. Anyone have a favorite jQuery menu they
> like for this? If not, I'll see about finding one...
All the "TM" logos are missing from the content and headers though. It
took me quite some time to add them to all the pages. Will you be able
to re-sync the content with the latest xdocs as it would take quite some
time to re-apply them and I want to tell the board that FOP, Commons and
XML Graphics sites are now brand compliant in the upcoming report.
Thanks,
Chris
>
> Clay
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org
Re: on changing fop documentation sources to markdown
Posted by The Web Maestro <th...@gmail.com>.
On Tue, Apr 17, 2012 at 7:52 AM, Chris Bowditch
<bo...@hotmail.com>wrote:
> BACKGROUND:
>> We are discussing moving XML Graphics web site to ASF-CMS. You can see
>> progress here:
>>
>> http://xmlgraphics.staging.**apache.org/<http://xmlgraphics.staging.apache.org/>
>>
>
> I realize its work in progress but it appears like you used an old
> snapshot without the "TM" marks in the content or the new logo that you
> designed. Also the links need to include License, Sponsorship, Thanks and
> Security as per the branding guidelines. This content is now live on the
> main site, so I guess you just started with a snapshot from a few weeks ago?
I added the logo (in GIF, JPG, PNG & SVG formats... ;-)
Sponsorship & Thanks were already there. License is on the Legal page,
which is there, but I've added it to the sidebar as well, along with the
Security page. ;-)
I also got the Compliance table working. Unfortunately, the CMS is
stripping the 'class="ForrestTable"', so the coloring is White-On-White
(but if you select the text, you'll see the content and layout is there).
As for the navigation menu, I'd like it to collapse most of the links,
except the section you're in. Anyone have a favorite jQuery menu they like
for this? If not, I'll see about finding one...
Clay
Re: on changing fop documentation sources to markdown
Posted by The Web Maestro <th...@gmail.com>.
On Tue, Apr 17, 2012 at 7:52 AM, Chris Bowditch
<bo...@hotmail.com>wrote:
> BACKGROUND:
>> We are discussing moving XML Graphics web site to ASF-CMS. You can see
>> progress here:
>>
>> http://xmlgraphics.staging.**apache.org/<http://xmlgraphics.staging.apache.org/>
>>
>
> I realize its work in progress but it appears like you used an old
> snapshot without the "TM" marks in the content or the new logo that you
> designed. Also the links need to include License, Sponsorship, Thanks and
> Security as per the branding guidelines. This content is now live on the
> main site, so I guess you just started with a snapshot from a few weeks ago?
I added the logo (in GIF, JPG, PNG & SVG formats... ;-)
Sponsorship & Thanks were already there. License is on the Legal page,
which is there, but I've added it to the sidebar as well, along with the
Security page. ;-)
I also got the Compliance table working. Unfortunately, the CMS is
stripping the 'class="ForrestTable"', so the coloring is White-On-White
(but if you select the text, you'll see the content and layout is there).
As for the navigation menu, I'd like it to collapse most of the links,
except the section you're in. Anyone have a favorite jQuery menu they like
for this? If not, I'll see about finding one...
Clay
Re: on changing fop documentation sources to markdown
Posted by The Web Maestro <th...@gmail.com>.
On Tue, Apr 17, 2012 at 7:52 AM, Chris Bowditch
<bo...@hotmail.com>wrote:
> BACKGROUND:
>> We are discussing moving XML Graphics web site to ASF-CMS. You can see
>> progress here:
>>
>> http://xmlgraphics.staging.**apache.org/<http://xmlgraphics.staging.apache.org/>
>>
>
> I realize its work in progress but it appears like you used an old
> snapshot without the "TM" marks in the content or the new logo that you
> designed. Also the links need to include License, Sponsorship, Thanks and
> Security as per the branding guidelines. This content is now live on the
> main site, so I guess you just started with a snapshot from a few weeks ago?
I added the logo (in GIF, JPG, PNG & SVG formats... ;-)
Sponsorship & Thanks were already there. License is on the Legal page,
which is there, but I've added it to the sidebar as well, along with the
Security page. ;-)
I also got the Compliance table working. Unfortunately, the CMS is
stripping the 'class="ForrestTable"', so the coloring is White-On-White
(but if you select the text, you'll see the content and layout is there).
As for the navigation menu, I'd like it to collapse most of the links,
except the section you're in. Anyone have a favorite jQuery menu they like
for this? If not, I'll see about finding one...
Clay
Re: on changing fop documentation sources to markdown
Posted by Chris Bowditch <bo...@hotmail.com>.
On 17/04/2012 14:59, Clay Leeds wrote:
> NOTE: Moving discussion to general@. Please make all further responses to general@.
Hi Clay,
Thanks for moving to general@
>
> BACKGROUND:
> We are discussing moving XML Graphics web site to ASF-CMS. You can see progress here:
>
> http://xmlgraphics.staging.apache.org/
I realize its work in progress but it appears like you used an old
snapshot without the "TM" marks in the content or the new logo that you
designed. Also the links need to include License, Sponsorship, Thanks
and Security as per the branding guidelines. This content is now live on
the main site, so I guess you just started with a snapshot from a few
weeks ago?
>
> ToDo:
> - Lots.
> - Style& templating work
> - Non-HTML content (figure out how to handle java-docs, download.cgi, demo stuff, etc.--might not be too difficult, just a matter of committing to CMS content/ dirs?)
>
> Done:
> - most HTML content
Thanks,
Chris
> Clay
>
> "My religion is simple. My religion is kindness."
> - HH The Dalai Lama of Tibet
>
> On Apr 17, 2012, at 1:19 AM, Chris Bowditch<bo...@hotmail.com> wrote:
>
>> On 15/04/2012 19:52, The Web Maestro wrote:
>>> I just added most of the nav for FOP Development (0.95, 1.0, trunk/ and 'dev'):
>> Hi Clay,
>>> http://xmlgraphics.staging.apache.org/
>>>
>>> As mentioned, there are likely missing things (like java-docs, download.cgi, Batik's DEMO, etc.)... It'd be great if folks could take a look... I haven't figured out how to add other content, but It Might Just Work(tm) if weupload it there via SVN...
>> Many thanks for working on this.
>>
>>> Come to think of it, we should probably move this to general@xmlgraphics.apache.org<ma...@xmlgraphics.apache.org>. Or is there a better mailing list? I'll refrain from sending to other lists, until we figure out where it should go.
>>>
>>> Any ideas where this discussion should move, since it entails changes to all XML Graphics Project web docs?
>> Yes this discussion should move to general@ as it will affect all sub projects of XML Graphics.
>>
>> Thanks,
>>
>> Chris
>>
>>> Kind regards,
>>>
>>> Clay Leeds
>>> --
>>> <th...@gmail.com>> -<http://ourlil.com/>
>>> My religion is simple. My religion is kindness.
>>> - HH The 14th Dalai Lama of Tibet
>>>
>>>
>>> On Sat, Apr 14, 2012 at 11:53 PM, The Web Maestro<th...@gmail.com>> wrote:
>>>
>>> I've updated the docs a bit, and gotten much (but not all!) of the
>>> FOP, Batik& Commons content into the CMS...
>>>
>>> We're still missing an adequate navigation system, so I did a
>>> preliminary job of getting a few links in the sidenav, but it's
>>> incomplete and ugly as sin. We'll need to build a mechanism to
>>> hide (collapse?) non-relevant links, but that shouldn't be too hard.
>>>
>>> We also need to figure out java-docs, download.cgi, and perhaps
>>> some other issues...
>>>
>>> Without further ado:
>>>
>>> http://xmlgraphics.staging.apache.org/
>>>
>>>
>>> Kind regards,
>>>
>>> Clay Leeds
>>> --
>>> <th...@gmail.com>> -
>>> <http://ourlil.com/>
>>> My religion is simple. My religion is kindness.
>>> - HH The 14th Dalai Lama of Tibet
>>>
>>>
>>> On Thu, Apr 12, 2012 at 10:03 PM, Clay Leeds
>>> <th...@gmail.com>> wrote:
>>>
>>> On Apr 12, 2012, at 6:41 AM, Glenn Adams<glenn@skynav.com
>>> <ma...@skynav.com>> wrote:
>>> > Agreed that removing forrest dependency is desirable.
>>> However, presumably the current xdocs would need to be
>>> converted to MD, in which case someone will need to construct
>>> an XSLT to do so. That begs the question of whether it would
>>> be necessary (at this time) to convert the source format to
>>> MD, or if an additional step in the CMS based process could
>>> merely perform that step automatically. If so, then it should
>>> not be necessary to change the authoring format at this time.
>>> It could be done as a separate step later.
>>>
>>> I am using Forrest 0.8 w markdown plugin. Conversion could be
>>> scripted, but that would negate the benefit of the CMS.
>>>
>>> > What I don't know yet is what we will lose from the
>>> conversion to MD in terms of ability to markup our source
>>> docs. Clearly, MD is not as semantically or syntactically rich
>>> as an XML based source. But do we lose anything of
>>> consequence? I don't know yet.
>>> >
>>> > One thing we may lose if we don't convert to MD is the
>>> ability to use CMS in-page editing. So that is a
>>> consideration. Perhaps that option is sufficient to justify
>>> other potential negatives in converting.
>>> >
>>> > G.
>>>
>>> One of my goals, was to see some discussion in the DEVers,
>>> before I complete the task of converting the docs. The
>>> MarkDown format is not nearly as semantic as xdoc, but it
>>> serves a different purpose.
>>>
>>> It'll take some time, and I'm still prepared to take it on.
>>> But I was hoping for some discussion ;-)
>>>
>>>
>>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org
Re: on changing fop documentation sources to markdown
Posted by Chris Bowditch <bo...@hotmail.com>.
On 17/04/2012 14:59, Clay Leeds wrote:
> NOTE: Moving discussion to general@. Please make all further responses to general@.
Hi Clay,
Thanks for moving to general@
>
> BACKGROUND:
> We are discussing moving XML Graphics web site to ASF-CMS. You can see progress here:
>
> http://xmlgraphics.staging.apache.org/
I realize its work in progress but it appears like you used an old
snapshot without the "TM" marks in the content or the new logo that you
designed. Also the links need to include License, Sponsorship, Thanks
and Security as per the branding guidelines. This content is now live on
the main site, so I guess you just started with a snapshot from a few
weeks ago?
>
> ToDo:
> - Lots.
> - Style& templating work
> - Non-HTML content (figure out how to handle java-docs, download.cgi, demo stuff, etc.--might not be too difficult, just a matter of committing to CMS content/ dirs?)
>
> Done:
> - most HTML content
Thanks,
Chris
> Clay
>
> "My religion is simple. My religion is kindness."
> - HH The Dalai Lama of Tibet
>
> On Apr 17, 2012, at 1:19 AM, Chris Bowditch<bo...@hotmail.com> wrote:
>
>> On 15/04/2012 19:52, The Web Maestro wrote:
>>> I just added most of the nav for FOP Development (0.95, 1.0, trunk/ and 'dev'):
>> Hi Clay,
>>> http://xmlgraphics.staging.apache.org/
>>>
>>> As mentioned, there are likely missing things (like java-docs, download.cgi, Batik's DEMO, etc.)... It'd be great if folks could take a look... I haven't figured out how to add other content, but It Might Just Work(tm) if weupload it there via SVN...
>> Many thanks for working on this.
>>
>>> Come to think of it, we should probably move this to general@xmlgraphics.apache.org<ma...@xmlgraphics.apache.org>. Or is there a better mailing list? I'll refrain from sending to other lists, until we figure out where it should go.
>>>
>>> Any ideas where this discussion should move, since it entails changes to all XML Graphics Project web docs?
>> Yes this discussion should move to general@ as it will affect all sub projects of XML Graphics.
>>
>> Thanks,
>>
>> Chris
>>
>>> Kind regards,
>>>
>>> Clay Leeds
>>> --
>>> <th...@gmail.com>> -<http://ourlil.com/>
>>> My religion is simple. My religion is kindness.
>>> - HH The 14th Dalai Lama of Tibet
>>>
>>>
>>> On Sat, Apr 14, 2012 at 11:53 PM, The Web Maestro<th...@gmail.com>> wrote:
>>>
>>> I've updated the docs a bit, and gotten much (but not all!) of the
>>> FOP, Batik& Commons content into the CMS...
>>>
>>> We're still missing an adequate navigation system, so I did a
>>> preliminary job of getting a few links in the sidenav, but it's
>>> incomplete and ugly as sin. We'll need to build a mechanism to
>>> hide (collapse?) non-relevant links, but that shouldn't be too hard.
>>>
>>> We also need to figure out java-docs, download.cgi, and perhaps
>>> some other issues...
>>>
>>> Without further ado:
>>>
>>> http://xmlgraphics.staging.apache.org/
>>>
>>>
>>> Kind regards,
>>>
>>> Clay Leeds
>>> --
>>> <th...@gmail.com>> -
>>> <http://ourlil.com/>
>>> My religion is simple. My religion is kindness.
>>> - HH The 14th Dalai Lama of Tibet
>>>
>>>
>>> On Thu, Apr 12, 2012 at 10:03 PM, Clay Leeds
>>> <th...@gmail.com>> wrote:
>>>
>>> On Apr 12, 2012, at 6:41 AM, Glenn Adams<glenn@skynav.com
>>> <ma...@skynav.com>> wrote:
>>> > Agreed that removing forrest dependency is desirable.
>>> However, presumably the current xdocs would need to be
>>> converted to MD, in which case someone will need to construct
>>> an XSLT to do so. That begs the question of whether it would
>>> be necessary (at this time) to convert the source format to
>>> MD, or if an additional step in the CMS based process could
>>> merely perform that step automatically. If so, then it should
>>> not be necessary to change the authoring format at this time.
>>> It could be done as a separate step later.
>>>
>>> I am using Forrest 0.8 w markdown plugin. Conversion could be
>>> scripted, but that would negate the benefit of the CMS.
>>>
>>> > What I don't know yet is what we will lose from the
>>> conversion to MD in terms of ability to markup our source
>>> docs. Clearly, MD is not as semantically or syntactically rich
>>> as an XML based source. But do we lose anything of
>>> consequence? I don't know yet.
>>> >
>>> > One thing we may lose if we don't convert to MD is the
>>> ability to use CMS in-page editing. So that is a
>>> consideration. Perhaps that option is sufficient to justify
>>> other potential negatives in converting.
>>> >
>>> > G.
>>>
>>> One of my goals, was to see some discussion in the DEVers,
>>> before I complete the task of converting the docs. The
>>> MarkDown format is not nearly as semantic as xdoc, but it
>>> serves a different purpose.
>>>
>>> It'll take some time, and I'm still prepared to take it on.
>>> But I was hoping for some discussion ;-)
>>>
>>>
>>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org
>
>
>
Re: on changing fop documentation sources to markdown
Posted by Chris Bowditch <bo...@hotmail.com>.
On 17/04/2012 14:59, Clay Leeds wrote:
> NOTE: Moving discussion to general@. Please make all further responses to general@.
Hi Clay,
Thanks for moving to general@
>
> BACKGROUND:
> We are discussing moving XML Graphics web site to ASF-CMS. You can see progress here:
>
> http://xmlgraphics.staging.apache.org/
I realize its work in progress but it appears like you used an old
snapshot without the "TM" marks in the content or the new logo that you
designed. Also the links need to include License, Sponsorship, Thanks
and Security as per the branding guidelines. This content is now live on
the main site, so I guess you just started with a snapshot from a few
weeks ago?
>
> ToDo:
> - Lots.
> - Style& templating work
> - Non-HTML content (figure out how to handle java-docs, download.cgi, demo stuff, etc.--might not be too difficult, just a matter of committing to CMS content/ dirs?)
>
> Done:
> - most HTML content
Thanks,
Chris
> Clay
>
> "My religion is simple. My religion is kindness."
> - HH The Dalai Lama of Tibet
>
> On Apr 17, 2012, at 1:19 AM, Chris Bowditch<bo...@hotmail.com> wrote:
>
>> On 15/04/2012 19:52, The Web Maestro wrote:
>>> I just added most of the nav for FOP Development (0.95, 1.0, trunk/ and 'dev'):
>> Hi Clay,
>>> http://xmlgraphics.staging.apache.org/
>>>
>>> As mentioned, there are likely missing things (like java-docs, download.cgi, Batik's DEMO, etc.)... It'd be great if folks could take a look... I haven't figured out how to add other content, but It Might Just Work(tm) if weupload it there via SVN...
>> Many thanks for working on this.
>>
>>> Come to think of it, we should probably move this to general@xmlgraphics.apache.org<ma...@xmlgraphics.apache.org>. Or is there a better mailing list? I'll refrain from sending to other lists, until we figure out where it should go.
>>>
>>> Any ideas where this discussion should move, since it entails changes to all XML Graphics Project web docs?
>> Yes this discussion should move to general@ as it will affect all sub projects of XML Graphics.
>>
>> Thanks,
>>
>> Chris
>>
>>> Kind regards,
>>>
>>> Clay Leeds
>>> --
>>> <th...@gmail.com>> -<http://ourlil.com/>
>>> My religion is simple. My religion is kindness.
>>> - HH The 14th Dalai Lama of Tibet
>>>
>>>
>>> On Sat, Apr 14, 2012 at 11:53 PM, The Web Maestro<th...@gmail.com>> wrote:
>>>
>>> I've updated the docs a bit, and gotten much (but not all!) of the
>>> FOP, Batik& Commons content into the CMS...
>>>
>>> We're still missing an adequate navigation system, so I did a
>>> preliminary job of getting a few links in the sidenav, but it's
>>> incomplete and ugly as sin. We'll need to build a mechanism to
>>> hide (collapse?) non-relevant links, but that shouldn't be too hard.
>>>
>>> We also need to figure out java-docs, download.cgi, and perhaps
>>> some other issues...
>>>
>>> Without further ado:
>>>
>>> http://xmlgraphics.staging.apache.org/
>>>
>>>
>>> Kind regards,
>>>
>>> Clay Leeds
>>> --
>>> <th...@gmail.com>> -
>>> <http://ourlil.com/>
>>> My religion is simple. My religion is kindness.
>>> - HH The 14th Dalai Lama of Tibet
>>>
>>>
>>> On Thu, Apr 12, 2012 at 10:03 PM, Clay Leeds
>>> <th...@gmail.com>> wrote:
>>>
>>> On Apr 12, 2012, at 6:41 AM, Glenn Adams<glenn@skynav.com
>>> <ma...@skynav.com>> wrote:
>>> > Agreed that removing forrest dependency is desirable.
>>> However, presumably the current xdocs would need to be
>>> converted to MD, in which case someone will need to construct
>>> an XSLT to do so. That begs the question of whether it would
>>> be necessary (at this time) to convert the source format to
>>> MD, or if an additional step in the CMS based process could
>>> merely perform that step automatically. If so, then it should
>>> not be necessary to change the authoring format at this time.
>>> It could be done as a separate step later.
>>>
>>> I am using Forrest 0.8 w markdown plugin. Conversion could be
>>> scripted, but that would negate the benefit of the CMS.
>>>
>>> > What I don't know yet is what we will lose from the
>>> conversion to MD in terms of ability to markup our source
>>> docs. Clearly, MD is not as semantically or syntactically rich
>>> as an XML based source. But do we lose anything of
>>> consequence? I don't know yet.
>>> >
>>> > One thing we may lose if we don't convert to MD is the
>>> ability to use CMS in-page editing. So that is a
>>> consideration. Perhaps that option is sufficient to justify
>>> other potential negatives in converting.
>>> >
>>> > G.
>>>
>>> One of my goals, was to see some discussion in the DEVers,
>>> before I complete the task of converting the docs. The
>>> MarkDown format is not nearly as semantic as xdoc, but it
>>> serves a different purpose.
>>>
>>> It'll take some time, and I'm still prepared to take it on.
>>> But I was hoping for some discussion ;-)
>>>
>>>
>>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org
Re: on changing fop documentation sources to markdown
Posted by Clay Leeds <th...@gmail.com>.
NOTE: Moving discussion to general@. Please make all further responses to general@.
BACKGROUND:
We are discussing moving XML Graphics web site to ASF-CMS. You can see progress here:
http://xmlgraphics.staging.apache.org/
ToDo:
- Lots.
- Style & templating work
- Non-HTML content (figure out how to handle java-docs, download.cgi, demo stuff, etc.--might not be too difficult, just a matter of committing to CMS content/ dirs?)
Done:
- most HTML content
Clay
"My religion is simple. My religion is kindness."
- HH The Dalai Lama of Tibet
On Apr 17, 2012, at 1:19 AM, Chris Bowditch <bo...@hotmail.com> wrote:
> On 15/04/2012 19:52, The Web Maestro wrote:
>> I just added most of the nav for FOP Development (0.95, 1.0, trunk/ and 'dev'):
> Hi Clay,
>>
>> http://xmlgraphics.staging.apache.org/
>>
>> As mentioned, there are likely missing things (like java-docs, download.cgi, Batik's DEMO, etc.)... It'd be great if folks could take a look... I haven't figured out how to add other content, but It Might Just Work(tm) if weupload it there via SVN...
>
> Many thanks for working on this.
>
>>
>> Come to think of it, we should probably move this to general@xmlgraphics.apache.org <ma...@xmlgraphics.apache.org>. Or is there a better mailing list? I'll refrain from sending to other lists, until we figure out where it should go.
>>
>> Any ideas where this discussion should move, since it entails changes to all XML Graphics Project web docs?
>
> Yes this discussion should move to general@ as it will affect all sub projects of XML Graphics.
>
> Thanks,
>
> Chris
>
>>
>> Kind regards,
>>
>> Clay Leeds
>> --
>> <the.webmaestro@gmail.com <ma...@gmail.com>> - <http://ourlil.com/>
>> My religion is simple. My religion is kindness.
>> - HH The 14th Dalai Lama of Tibet
>>
>>
>> On Sat, Apr 14, 2012 at 11:53 PM, The Web Maestro <the.webmaestro@gmail.com <ma...@gmail.com>> wrote:
>>
>> I've updated the docs a bit, and gotten much (but not all!) of the
>> FOP, Batik & Commons content into the CMS...
>>
>> We're still missing an adequate navigation system, so I did a
>> preliminary job of getting a few links in the sidenav, but it's
>> incomplete and ugly as sin. We'll need to build a mechanism to
>> hide (collapse?) non-relevant links, but that shouldn't be too hard.
>>
>> We also need to figure out java-docs, download.cgi, and perhaps
>> some other issues...
>>
>> Without further ado:
>>
>> http://xmlgraphics.staging.apache.org/
>>
>>
>> Kind regards,
>>
>> Clay Leeds
>> --
>> <the.webmaestro@gmail.com <ma...@gmail.com>> -
>> <http://ourlil.com/>
>> My religion is simple. My religion is kindness.
>> - HH The 14th Dalai Lama of Tibet
>>
>>
>> On Thu, Apr 12, 2012 at 10:03 PM, Clay Leeds
>> <the.webmaestro@gmail.com <ma...@gmail.com>> wrote:
>>
>> On Apr 12, 2012, at 6:41 AM, Glenn Adams <glenn@skynav.com
>> <ma...@skynav.com>> wrote:
>> > Agreed that removing forrest dependency is desirable.
>> However, presumably the current xdocs would need to be
>> converted to MD, in which case someone will need to construct
>> an XSLT to do so. That begs the question of whether it would
>> be necessary (at this time) to convert the source format to
>> MD, or if an additional step in the CMS based process could
>> merely perform that step automatically. If so, then it should
>> not be necessary to change the authoring format at this time.
>> It could be done as a separate step later.
>>
>> I am using Forrest 0.8 w markdown plugin. Conversion could be
>> scripted, but that would negate the benefit of the CMS.
>>
>> > What I don't know yet is what we will lose from the
>> conversion to MD in terms of ability to markup our source
>> docs. Clearly, MD is not as semantically or syntactically rich
>> as an XML based source. But do we lose anything of
>> consequence? I don't know yet.
>> >
>> > One thing we may lose if we don't convert to MD is the
>> ability to use CMS in-page editing. So that is a
>> consideration. Perhaps that option is sufficient to justify
>> other potential negatives in converting.
>> >
>> > G.
>>
>> One of my goals, was to see some discussion in the DEVers,
>> before I complete the task of converting the docs. The
>> MarkDown format is not nearly as semantic as xdoc, but it
>> serves a different purpose.
>>
>> It'll take some time, and I'm still prepared to take it on.
>> But I was hoping for some discussion ;-)
>>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org
Re: on changing fop documentation sources to markdown
Posted by Clay Leeds <th...@gmail.com>.
NOTE: Moving discussion to general@. Please make all further responses to general@.
BACKGROUND:
We are discussing moving XML Graphics web site to ASF-CMS. You can see progress here:
http://xmlgraphics.staging.apache.org/
ToDo:
- Lots.
- Style & templating work
- Non-HTML content (figure out how to handle java-docs, download.cgi, demo stuff, etc.--might not be too difficult, just a matter of committing to CMS content/ dirs?)
Done:
- most HTML content
Clay
"My religion is simple. My religion is kindness."
- HH The Dalai Lama of Tibet
On Apr 17, 2012, at 1:19 AM, Chris Bowditch <bo...@hotmail.com> wrote:
> On 15/04/2012 19:52, The Web Maestro wrote:
>> I just added most of the nav for FOP Development (0.95, 1.0, trunk/ and 'dev'):
> Hi Clay,
>>
>> http://xmlgraphics.staging.apache.org/
>>
>> As mentioned, there are likely missing things (like java-docs, download.cgi, Batik's DEMO, etc.)... It'd be great if folks could take a look... I haven't figured out how to add other content, but It Might Just Work(tm) if weupload it there via SVN...
>
> Many thanks for working on this.
>
>>
>> Come to think of it, we should probably move this to general@xmlgraphics.apache.org <ma...@xmlgraphics.apache.org>. Or is there a better mailing list? I'll refrain from sending to other lists, until we figure out where it should go.
>>
>> Any ideas where this discussion should move, since it entails changes to all XML Graphics Project web docs?
>
> Yes this discussion should move to general@ as it will affect all sub projects of XML Graphics.
>
> Thanks,
>
> Chris
>
>>
>> Kind regards,
>>
>> Clay Leeds
>> --
>> <the.webmaestro@gmail.com <ma...@gmail.com>> - <http://ourlil.com/>
>> My religion is simple. My religion is kindness.
>> - HH The 14th Dalai Lama of Tibet
>>
>>
>> On Sat, Apr 14, 2012 at 11:53 PM, The Web Maestro <the.webmaestro@gmail.com <ma...@gmail.com>> wrote:
>>
>> I've updated the docs a bit, and gotten much (but not all!) of the
>> FOP, Batik & Commons content into the CMS...
>>
>> We're still missing an adequate navigation system, so I did a
>> preliminary job of getting a few links in the sidenav, but it's
>> incomplete and ugly as sin. We'll need to build a mechanism to
>> hide (collapse?) non-relevant links, but that shouldn't be too hard.
>>
>> We also need to figure out java-docs, download.cgi, and perhaps
>> some other issues...
>>
>> Without further ado:
>>
>> http://xmlgraphics.staging.apache.org/
>>
>>
>> Kind regards,
>>
>> Clay Leeds
>> --
>> <the.webmaestro@gmail.com <ma...@gmail.com>> -
>> <http://ourlil.com/>
>> My religion is simple. My religion is kindness.
>> - HH The 14th Dalai Lama of Tibet
>>
>>
>> On Thu, Apr 12, 2012 at 10:03 PM, Clay Leeds
>> <the.webmaestro@gmail.com <ma...@gmail.com>> wrote:
>>
>> On Apr 12, 2012, at 6:41 AM, Glenn Adams <glenn@skynav.com
>> <ma...@skynav.com>> wrote:
>> > Agreed that removing forrest dependency is desirable.
>> However, presumably the current xdocs would need to be
>> converted to MD, in which case someone will need to construct
>> an XSLT to do so. That begs the question of whether it would
>> be necessary (at this time) to convert the source format to
>> MD, or if an additional step in the CMS based process could
>> merely perform that step automatically. If so, then it should
>> not be necessary to change the authoring format at this time.
>> It could be done as a separate step later.
>>
>> I am using Forrest 0.8 w markdown plugin. Conversion could be
>> scripted, but that would negate the benefit of the CMS.
>>
>> > What I don't know yet is what we will lose from the
>> conversion to MD in terms of ability to markup our source
>> docs. Clearly, MD is not as semantically or syntactically rich
>> as an XML based source. But do we lose anything of
>> consequence? I don't know yet.
>> >
>> > One thing we may lose if we don't convert to MD is the
>> ability to use CMS in-page editing. So that is a
>> consideration. Perhaps that option is sufficient to justify
>> other potential negatives in converting.
>> >
>> > G.
>>
>> One of my goals, was to see some discussion in the DEVers,
>> before I complete the task of converting the docs. The
>> MarkDown format is not nearly as semantic as xdoc, but it
>> serves a different purpose.
>>
>> It'll take some time, and I'm still prepared to take it on.
>> But I was hoping for some discussion ;-)
>>
>>
>>
>
Re: on changing fop documentation sources to markdown
Posted by Clay Leeds <th...@gmail.com>.
NOTE: Moving discussion to general@. Please make all further responses to general@.
BACKGROUND:
We are discussing moving XML Graphics web site to ASF-CMS. You can see progress here:
http://xmlgraphics.staging.apache.org/
ToDo:
- Lots.
- Style & templating work
- Non-HTML content (figure out how to handle java-docs, download.cgi, demo stuff, etc.--might not be too difficult, just a matter of committing to CMS content/ dirs?)
Done:
- most HTML content
Clay
"My religion is simple. My religion is kindness."
- HH The Dalai Lama of Tibet
On Apr 17, 2012, at 1:19 AM, Chris Bowditch <bo...@hotmail.com> wrote:
> On 15/04/2012 19:52, The Web Maestro wrote:
>> I just added most of the nav for FOP Development (0.95, 1.0, trunk/ and 'dev'):
> Hi Clay,
>>
>> http://xmlgraphics.staging.apache.org/
>>
>> As mentioned, there are likely missing things (like java-docs, download.cgi, Batik's DEMO, etc.)... It'd be great if folks could take a look... I haven't figured out how to add other content, but It Might Just Work(tm) if weupload it there via SVN...
>
> Many thanks for working on this.
>
>>
>> Come to think of it, we should probably move this to general@xmlgraphics.apache.org <ma...@xmlgraphics.apache.org>. Or is there a better mailing list? I'll refrain from sending to other lists, until we figure out where it should go.
>>
>> Any ideas where this discussion should move, since it entails changes to all XML Graphics Project web docs?
>
> Yes this discussion should move to general@ as it will affect all sub projects of XML Graphics.
>
> Thanks,
>
> Chris
>
>>
>> Kind regards,
>>
>> Clay Leeds
>> --
>> <the.webmaestro@gmail.com <ma...@gmail.com>> - <http://ourlil.com/>
>> My religion is simple. My religion is kindness.
>> - HH The 14th Dalai Lama of Tibet
>>
>>
>> On Sat, Apr 14, 2012 at 11:53 PM, The Web Maestro <the.webmaestro@gmail.com <ma...@gmail.com>> wrote:
>>
>> I've updated the docs a bit, and gotten much (but not all!) of the
>> FOP, Batik & Commons content into the CMS...
>>
>> We're still missing an adequate navigation system, so I did a
>> preliminary job of getting a few links in the sidenav, but it's
>> incomplete and ugly as sin. We'll need to build a mechanism to
>> hide (collapse?) non-relevant links, but that shouldn't be too hard.
>>
>> We also need to figure out java-docs, download.cgi, and perhaps
>> some other issues...
>>
>> Without further ado:
>>
>> http://xmlgraphics.staging.apache.org/
>>
>>
>> Kind regards,
>>
>> Clay Leeds
>> --
>> <the.webmaestro@gmail.com <ma...@gmail.com>> -
>> <http://ourlil.com/>
>> My religion is simple. My religion is kindness.
>> - HH The 14th Dalai Lama of Tibet
>>
>>
>> On Thu, Apr 12, 2012 at 10:03 PM, Clay Leeds
>> <the.webmaestro@gmail.com <ma...@gmail.com>> wrote:
>>
>> On Apr 12, 2012, at 6:41 AM, Glenn Adams <glenn@skynav.com
>> <ma...@skynav.com>> wrote:
>> > Agreed that removing forrest dependency is desirable.
>> However, presumably the current xdocs would need to be
>> converted to MD, in which case someone will need to construct
>> an XSLT to do so. That begs the question of whether it would
>> be necessary (at this time) to convert the source format to
>> MD, or if an additional step in the CMS based process could
>> merely perform that step automatically. If so, then it should
>> not be necessary to change the authoring format at this time.
>> It could be done as a separate step later.
>>
>> I am using Forrest 0.8 w markdown plugin. Conversion could be
>> scripted, but that would negate the benefit of the CMS.
>>
>> > What I don't know yet is what we will lose from the
>> conversion to MD in terms of ability to markup our source
>> docs. Clearly, MD is not as semantically or syntactically rich
>> as an XML based source. But do we lose anything of
>> consequence? I don't know yet.
>> >
>> > One thing we may lose if we don't convert to MD is the
>> ability to use CMS in-page editing. So that is a
>> consideration. Perhaps that option is sufficient to justify
>> other potential negatives in converting.
>> >
>> > G.
>>
>> One of my goals, was to see some discussion in the DEVers,
>> before I complete the task of converting the docs. The
>> MarkDown format is not nearly as semantic as xdoc, but it
>> serves a different purpose.
>>
>> It'll take some time, and I'm still prepared to take it on.
>> But I was hoping for some discussion ;-)
>>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org