Re: [www] OOo Website Conversion
Thanks for the work, Dave.
Dave Fisher wrote:
Hi -
Progress.
On Aug 8, 2011, at 8:38 AM, Kay Schenk wrote:
On 08/08/2011 08:29 AM, Dave Fisher wrote:
Hi Kay,
I was able to get HTML wrapped using the Apache CMS last night. I'm not ready
to commit anything yet. I'll summarize where I am and possible next steps.
In order to make progress the key was investigating the source for the {% %}
template tagging. This is found here:
cms/build/lib/Dotiac/DTL/Tag
I changed view.pm to include an html_page procedure
In path.pm I added a pattern for html wrapping.
our @patterns = (
[qr!\.mdtext$!, single_narrative => { template =>
"single_narrative.html" }],
[qr!\.html$!, html_page => { template => "html_page.html" }],
) ;
ah! good! So this can be parsed on a page by page basis? If so, super!
The template html_page.html looks a lot like single_narrative.html but adds an
override to the content block.
{% extends "skeleton.html" %}
{% block content %}{% autoescape off %}{{ content }}{% endautoescape %}{%
endblock %}
Now is this:
{% extends "skeleton.html" %}
{% block content %}{% autoescape off %}{{ content }}{% endautoescape %}{%
endblock %}
{$ endextends $}
We keep a single skeleton which is good.
This is great news! Thanks for your wonderful insights and work!
You are welcome. With a few tweaks things are committed and the process works!
Next steps are
- blocks for javascript and css insertion.
For testing purposes I split the www/index.html into an index.style and
shortened index.html.
I'm not sure if this is best or if the split needs to be done while processing
the view. This is a subject for tomorrow.
Also, this page needs a lot of work on styles to make it look like before. Kenai stores
content in places we may not have access to via the svn repos like "branding"
- controlling sidenav. The current html_page.html is not very good for the
pages that Carl modified in the download directory.
For all html wrapped content I now turn off the sidenav. For mdtext the sidenav
remains.
- header and footer framework
For tomorrow.
- online cms editing of html
Confirmed the editing of html. There is syntax coloring in the CMS WebGUI.
- scripting of Kenai html into CMS compatible - stripping of headers and
extraction of javascript and css.
To be discussed. It depends on how many sets of special page styles are really
needed. Here is how it currently works:
Here is the script for wrapping the html:
sub html_page {
my %args = @_;
my %styleargs = @_;
my $file = "content$args{path}";
my $template = $args{template};
$args{breadcrumbs} = breadcrumbs($args{path});
read_text_file $file, \%args;
my $page_path = $file;
$page_path =~ s/\.[^.]+$/.page/;
if (-d $page_path) {
for my $f (grep -f, glob "$page_path/*.mdtext") {
$f =~ m!/([^/]+)\.mdtext$! or die "Bad filename: $f\n";
$args{$1} = {};
read_text_file $f, $args{$1};
}
}
my $style_path = $file;
$style_path =~ s/\.[^.]+$/.style/;
if (-f $style_path) {
read_text_file $style_path, \%styleargs;
$args{scriptstyle} = $styleargs{content};
}
return Template($template)->render(\%args), html => \%args;
}
Which interacts with templates/skeleton.html
{% block title %}{{ headers.title }}{% endblock %}
{% autoescape off %}{% if scriptstyle %}{{ scriptstyle }}{% else %}{% include
"scriptstyle.html"%}{% endif %}{% endautoescape %}
So you see there is a default location for css and javascript.
The question is if there should be a set of selectable javascript/css
templates, or if we want to have these files be next to the file they apply to.
If we go to a specific set of templates method then we would change to:
{% autoescape off %}{% if scriptstyle %}{% include scriptstyle %}{% else %}{% include
"scriptstyle.html"%}{% endif %}{% endautoescape %}
Regards,
Dave
Regards,
Dave
On Aug 7, 2011, at 8:35 AM, Kay Schenk wrote:
On 08/06/2011 09:03 PM, Dave Fisher wrote:
On Aug 4, 2011, at 12:16 PM, Kay Schenk wrote:
I just wanted to report that this script worked just fine as near
as I can tell.
Great. When I did the work for the www and download project I used a
different script which is still a stub as there was a hand editing
step to correct inconsistent line endings.
The post about the script has shown up in several places, but
placing it as its own subject seemed appropriate.
yes...it got buried! :)
Now back to investigating headers/footers.
I added a page to the wiki with some of my thoughts today about
headers and footers for the websites including the MediaWiki and User
Forums.
https://cwiki.apache.org/confluence/display/OOOUSERS/Website+Template
good! this needs regular updating as we iron out issues...I'll take a look
I am going to try a new template/skeleton.html tomorrow.
Regards, Dave
OK, I'm going to
Re: [www] OOo Website Conversion
Am 08/09/2011 03:07 AM, schrieb Dave Fisher:
Hi -
Progress.
On Aug 8, 2011, at 8:38 AM, Kay Schenk wrote:
On 08/08/2011 08:29 AM, Dave Fisher wrote:
Hi Kay,
I was able to get HTML wrapped using the Apache CMS last night. I'm not ready
to commit anything yet. I'll summarize where I am and possible next steps.
In order to make progress the key was investigating the source for the {% %}
template tagging. This is found here:
cms/build/lib/Dotiac/DTL/Tag
I changed view.pm to include an html_page procedure
In path.pm I added a pattern for html wrapping.
our @patterns = (
[qr!\.mdtext$!, single_narrative => { template =>
"single_narrative.html" }],
[qr!\.html$!, html_page => { template => "html_page.html" }],
) ;
ah! good! So this can be parsed on a page by page basis? If so, super!
The template html_page.html looks a lot like single_narrative.html but adds an
override to the content block.
{% extends "skeleton.html" %}
{% block content %}{% autoescape off %}{{ content }}{% endautoescape %}{%
endblock %}
Now is this:
{% extends "skeleton.html" %}
{% block content %}{% autoescape off %}{{ content }}{% endautoescape %}{%
endblock %}
{$ endextends $}
We keep a single skeleton which is good.
This is great news! Thanks for your wonderful insights and work!
You are welcome. With a few tweaks things are committed and the process works!
Next steps are
- blocks for javascript and css insertion.
For testing purposes I split the www/index.html into an index.style and
shortened index.html.
I'm not sure if this is best or if the split needs to be done while processing
the view. This is a subject for tomorrow.
Also, this page needs a lot of work on styles to make it look like before. Kenai stores
content in places we may not have access to via the svn repos like "branding"
- controlling sidenav. The current html_page.html is not very good for the
pages that Carl modified in the download directory.
For all html wrapped content I now turn off the sidenav. For mdtext the sidenav
remains.
When you look at
"http://incubator.apache.org/openofficeorg/download/index.html"; the
sidenav is not really turned off. It's just without content but the
indent still remains. Is that what you wanted? If so, the space is IMHO
too much wasted as you can especially see here:
"http://incubator.apache.org/openofficeorg/download/other.html";
And also here "http://incubator.apache.org/openofficeorg/www/index.html";
we still have a bit to do. :-P
Thanks a lot for unifying the styles. :-)
Marcus
- header and footer framework
For tomorrow.
- online cms editing of html
Confirmed the editing of html. There is syntax coloring in the CMS WebGUI.
- scripting of Kenai html into CMS compatible - stripping of headers and
extraction of javascript and css.
To be discussed. It depends on how many sets of special page styles are really
needed. Here is how it currently works:
Here is the script for wrapping the html:
sub html_page {
my %args = @_;
my %styleargs = @_;
my $file = "content$args{path}";
my $template = $args{template};
$args{breadcrumbs} = breadcrumbs($args{path});
read_text_file $file, \%args;
my $page_path = $file;
$page_path =~ s/\.[^.]+$/.page/;
if (-d $page_path) {
for my $f (grep -f, glob "$page_path/*.mdtext") {
$f =~ m!/([^/]+)\.mdtext$! or die "Bad filename: $f\n";
$args{$1} = {};
read_text_file $f, $args{$1};
}
}
my $style_path = $file;
$style_path =~ s/\.[^.]+$/.style/;
if (-f $style_path) {
read_text_file $style_path, \%styleargs;
$args{scriptstyle} = $styleargs{content};
}
return Template($template)->render(\%args), html => \%args;
}
Which interacts with templates/skeleton.html
{% block title %}{{ headers.title }}{% endblock %}
{% autoescape off %}{% if scriptstyle %}{{ scriptstyle }}{% else %}{% include
"scriptstyle.html"%}{% endif %}{% endautoescape %}
So you see there is a default location for css and javascript.
The question is if there should be a set of selectable javascript/css
templates, or if we want to have these files be next to the file they apply to.
If we go to a specific set of templates method then we would change to:
{% autoescape off %}{% if scriptstyle %}{% include scriptstyle %}{% else %}{% include
"scriptstyle.html"%}{% endif %}{% endautoescape %}
Regards,
Dave
Regards,
Dave
On Aug 7, 2011, at 8:35 AM, Kay Schenk wrote:
On 08/06/2011 09:03 PM, Dave Fisher wrote:
On Aug 4, 2011, at 12:16 PM, Kay Schenk wrote:
I just wanted to report that this script worked just fine as near
as I can tell.
Great. When I did the work for the www and download project I used a
different script which is still a stub as there was a hand editing
step to correct inconsistent line endings.
The post about the script has shown up in several places, but
pl
Re: [www] OOo Website Conversion
On Aug 9, 2011, at 12:22 AM, Marcus (OOo) wrote:
> Am 08/09/2011 03:07 AM, schrieb Dave Fisher:
>> Hi -
>>
>> Progress.
>>
>> On Aug 8, 2011, at 8:38 AM, Kay Schenk wrote:
>>
>>> On 08/08/2011 08:29 AM, Dave Fisher wrote:
Hi Kay,
I was able to get HTML wrapped using the Apache CMS last night. I'm not
ready to commit anything yet. I'll summarize where I am and possible next
steps.
In order to make progress the key was investigating the source for the {%
%} template tagging. This is found here:
cms/build/lib/Dotiac/DTL/Tag
I changed view.pm to include an html_page procedure
In path.pm I added a pattern for html wrapping.
our @patterns = (
[qr!\.mdtext$!, single_narrative => { template =>
"single_narrative.html" }],
[qr!\.html$!, html_page => { template => "html_page.html" }],
) ;
>>>
>>> ah! good! So this can be parsed on a page by page basis? If so, super!
>>>
>>>
The template html_page.html looks a lot like single_narrative.html but
adds an override to the content block.
{% extends "skeleton.html" %}
{% block content %}{% autoescape off %}{{ content }}{% endautoescape %}{%
endblock %}
>>
>> Now is this:
>>
>> {% extends "skeleton.html" %}
>> {% block content %}{% autoescape off %}{{ content }}{% endautoescape %}{%
>> endblock %}
>> {$ endextends $}
>>
We keep a single skeleton which is good.
>>>
>>> This is great news! Thanks for your wonderful insights and work!
>>
>> You are welcome. With a few tweaks things are committed and the process
>> works!
>>
>>>
Next steps are
- blocks for javascript and css insertion.
>>
>> For testing purposes I split the www/index.html into an index.style and
>> shortened index.html.
>>
>> I'm not sure if this is best or if the split needs to be done while
>> processing the view. This is a subject for tomorrow.
>>
>> Also, this page needs a lot of work on styles to make it look like before.
>> Kenai stores content in places we may not have access to via the svn repos
>> like "branding"
>>
- controlling sidenav. The current html_page.html is not very good for the
pages that Carl modified in the download directory.
>>
>> For all html wrapped content I now turn off the sidenav. For mdtext the
>> sidenav remains.
>
> When you look at
> "http://incubator.apache.org/openofficeorg/download/index.html"; the sidenav
> is not really turned off. It's just without content but the indent still
> remains. Is that what you wanted? If so, the space is IMHO too much wasted as
> you can especially see here:
> "http://incubator.apache.org/openofficeorg/download/other.html";
True. The css is not distingusihed. We have some equivalence in id/class names.
We can do this either by the id or by alternative css. Today I lean towards
changing ids.
Converting to the proposed framework will help.
>
> And also here "http://incubator.apache.org/openofficeorg/www/index.html"; we
> still have a bit to do. :-P
We do have a lot to do. It is not always a direct path and I am learning a lot!
We will need to make some choices about page layouts. Where do we want to have
the different types of pages? How much is special and how much fits a "cookie
cutter" model?
>
> Thanks a lot for unifying the styles. :-)
It is very much my pleasure!
I am looking forward to your ideas.
Regards,
Dave
>
> Marcus
>
>
>
- header and footer framework
>>
>> For tomorrow.
>>
- online cms editing of html
>>
>> Confirmed the editing of html. There is syntax coloring in the CMS WebGUI.
>>
- scripting of Kenai html into CMS compatible - stripping of headers and
extraction of javascript and css.
>>
>> To be discussed. It depends on how many sets of special page styles are
>> really needed. Here is how it currently works:
>>
>> Here is the script for wrapping the html:
>>
>> sub html_page {
>> my %args = @_;
>> my %styleargs = @_;
>> my $file = "content$args{path}";
>> my $template = $args{template};
>> $args{breadcrumbs} = breadcrumbs($args{path});
>>
>> read_text_file $file, \%args;
>>
>> my $page_path = $file;
>> $page_path =~ s/\.[^.]+$/.page/;
>> if (-d $page_path) {
>> for my $f (grep -f, glob "$page_path/*.mdtext") {
>> $f =~ m!/([^/]+)\.mdtext$! or die "Bad filename: $f\n";
>> $args{$1} = {};
>> read_text_file $f, $args{$1};
>> }
>> }
>>
>> my $style_path = $file;
>> $style_path =~ s/\.[^.]+$/.style/;
>> if (-f $style_path) {
>> read_text_file $style_path, \%styleargs;
>> $args{scriptstyle} = $styleargs{content};
>> }
>>
>> return Template($template)->render(\%args), html => \%args;
>> }
>>
>> Which interacts with templates/skeleton.html
>>
>> {% block title %}{{ headers.title }}{% endblock %}
>>
>>
Re: [www] OOo Website Conversion
Hi -
I have modified the template process.
For html files the head and body content are extracted and then placed into the
template.
The wrapping is good. There is still work to do with getting to a single
version of the css and javascript.
What is notable it that http://incubator.apache.org/openofficeorg/www and
http://incubator.apache.org/openofficeorg/download are now connected and have
good layout and function.
Next step it work on the footer.
On Aug 9, 2011, at 1:09 AM, Dave Fisher wrote:
>
> On Aug 9, 2011, at 12:22 AM, Marcus (OOo) wrote:
>
>> When you look at
>> "http://incubator.apache.org/openofficeorg/download/index.html"; the sidenav
>> is not really turned off. It's just without content but the indent still
>> remains. Is that what you wanted? If so, the space is IMHO too much wasted
>> as you can especially see here:
>> "http://incubator.apache.org/openofficeorg/download/other.html";
Taken care of.
>>
>> And also here "http://incubator.apache.org/openofficeorg/www/index.html"; we
>> still have a bit to do. :-P
>
> We do have a lot to do. It is not always a direct path and I am learning a
> lot! We will need to make some choices about page layouts. Where do we want
> to have the different types of pages? How much is special and how much fits a
> "cookie cutter" model?
Getting close here as well.
Regards,
Dave
>
>>
>> Thanks a lot for unifying the styles. :-)
>
> It is very much my pleasure!
>
> I am looking forward to your ideas.
>
> Regards,
> Dave
>
>
>>
>> Marcus
>>
>>
>>
> - header and footer framework
>>>
>>> For tomorrow.
>>>
> - online cms editing of html
>>>
>>> Confirmed the editing of html. There is syntax coloring in the CMS WebGUI.
>>>
> - scripting of Kenai html into CMS compatible - stripping of headers and
> extraction of javascript and css.
>>>
>>> To be discussed. It depends on how many sets of special page styles are
>>> really needed. Here is how it currently works:
>>>
>>> Here is the script for wrapping the html:
>>>
>>> sub html_page {
>>>my %args = @_;
>>>my %styleargs = @_;
>>>my $file = "content$args{path}";
>>>my $template = $args{template};
>>>$args{breadcrumbs} = breadcrumbs($args{path});
>>>
>>>read_text_file $file, \%args;
>>>
>>>my $page_path = $file;
>>>$page_path =~ s/\.[^.]+$/.page/;
>>>if (-d $page_path) {
>>>for my $f (grep -f, glob "$page_path/*.mdtext") {
>>>$f =~ m!/([^/]+)\.mdtext$! or die "Bad filename: $f\n";
>>>$args{$1} = {};
>>>read_text_file $f, $args{$1};
>>>}
>>>}
>>>
>>>my $style_path = $file;
>>>$style_path =~ s/\.[^.]+$/.style/;
>>>if (-f $style_path) {
>>>read_text_file $style_path, \%styleargs;
>>>$args{scriptstyle} = $styleargs{content};
>>>}
>>>
>>>return Template($template)->render(\%args), html => \%args;
>>> }
>>>
>>> Which interacts with templates/skeleton.html
>>>
>>> {% block title %}{{ headers.title }}{% endblock %}
>>>
>>> {% autoescape off %}{% if scriptstyle %}{{ scriptstyle }}{% else %}{%
>>> include "scriptstyle.html"%}{% endif %}{% endautoescape %}
>>>
>>> So you see there is a default location for css and javascript.
>>>
>>> The question is if there should be a set of selectable javascript/css
>>> templates, or if we want to have these files be next to the file they apply
>>> to.
>>>
>>> If we go to a specific set of templates method then we would change to:
>>>
>>> {% autoescape off %}{% if scriptstyle %}{% include scriptstyle %}{% else
>>> %}{% include "scriptstyle.html"%}{% endif %}{% endautoescape %}
>>>
>>> Regards,
>>> Dave
>>>
>>>
>
> Regards,
> Dave
>
> On Aug 7, 2011, at 8:35 AM, Kay Schenk wrote:
>
>>
>>
>> On 08/06/2011 09:03 PM, Dave Fisher wrote:
>>>
>>> On Aug 4, 2011, at 12:16 PM, Kay Schenk wrote:
>>>
I just wanted to report that this script worked just fine as near
as I can tell.
>>>
>>> Great. When I did the work for the www and download project I used a
>>> different script which is still a stub as there was a hand editing
>>> step to correct inconsistent line endings.
>>>
The post about the script has shown up in several places, but
placing it as its own subject seemed appropriate.
>>
>> yes...it got buried! :)
>>
Now back to investigating headers/footers.
>>>
>>> I added a page to the wiki with some of my thoughts today about
>>> headers and footers for the websites including the MediaWiki and User
>>> Forums.
>>>
>>> https://cwiki.apache.org/confluence/display/OOOUSERS/Website+Template
>>
>> good! this needs regular updating as we iron out issues...I'll take a
>> look
>>>
>>> I am going to try a new template/skeleton.html tomorrow.
>>>
>>> Regards, Dave
>>
>> OK, I'm going to tr
Re: [www] OOo Website Conversion
Am 08/14/2011 06:58 AM, schrieb Dave Fisher:
Hi -
I have modified the template process.
For html files the head and body content are extracted and then placed into the
template.
The wrapping is good. There is still work to do with getting to a single
version of the css and javascript.
What is notable it that http://incubator.apache.org/openofficeorg/www and
http://incubator.apache.org/openofficeorg/download are now connected and have
good layout and function.
Looks great. Thanks a lot for taking care about the CSS stuff. :-)
Next step it work on the footer.
Currently this is the text:
"Copyright © 2011 The Apache Software Foundation, Licensed under the
Apache License, Version 2.0.
Apache and the Apache feather logos are trademarks of The Apache
Software Foundation."
I don't know if something is missing. However, 1-2 links more to
respective Apache websites for details would be helpful.
Marcus
On Aug 9, 2011, at 1:09 AM, Dave Fisher wrote:
On Aug 9, 2011, at 12:22 AM, Marcus (OOo) wrote:
When you look at "http://incubator.apache.org/openofficeorg/download/index.html"; the
sidenav is not really turned off. It's just without content but the indent still remains. Is that
what you wanted? If so, the space is IMHO too much wasted as you can especially see here:
"http://incubator.apache.org/openofficeorg/download/other.html";
Taken care of.
And also here "http://incubator.apache.org/openofficeorg/www/index.html"; we
still have a bit to do. :-P
We do have a lot to do. It is not always a direct path and I am learning a lot! We will
need to make some choices about page layouts. Where do we want to have the different
types of pages? How much is special and how much fits a "cookie cutter" model?
Getting close here as well.
Regards,
Dave
Thanks a lot for unifying the styles. :-)
It is very much my pleasure!
I am looking forward to your ideas.
Regards,
Dave
Marcus
- header and footer framework
For tomorrow.
- online cms editing of html
Confirmed the editing of html. There is syntax coloring in the CMS WebGUI.
- scripting of Kenai html into CMS compatible - stripping of headers and
extraction of javascript and css.
To be discussed. It depends on how many sets of special page styles are really
needed. Here is how it currently works:
Here is the script for wrapping the html:
sub html_page {
my %args = @_;
my %styleargs = @_;
my $file = "content$args{path}";
my $template = $args{template};
$args{breadcrumbs} = breadcrumbs($args{path});
read_text_file $file, \%args;
my $page_path = $file;
$page_path =~ s/\.[^.]+$/.page/;
if (-d $page_path) {
for my $f (grep -f, glob "$page_path/*.mdtext") {
$f =~ m!/([^/]+)\.mdtext$! or die "Bad filename: $f\n";
$args{$1} = {};
read_text_file $f, $args{$1};
}
}
my $style_path = $file;
$style_path =~ s/\.[^.]+$/.style/;
if (-f $style_path) {
read_text_file $style_path, \%styleargs;
$args{scriptstyle} = $styleargs{content};
}
return Template($template)->render(\%args), html => \%args;
}
Which interacts with templates/skeleton.html
{% block title %}{{ headers.title }}{% endblock %}
{% autoescape off %}{% if scriptstyle %}{{ scriptstyle }}{% else %}{% include
"scriptstyle.html"%}{% endif %}{% endautoescape %}
So you see there is a default location for css and javascript.
The question is if there should be a set of selectable javascript/css
templates, or if we want to have these files be next to the file they apply to.
If we go to a specific set of templates method then we would change to:
{% autoescape off %}{% if scriptstyle %}{% include scriptstyle %}{% else %}{% include
"scriptstyle.html"%}{% endif %}{% endautoescape %}
Regards,
Dave
Regards,
Dave
On Aug 7, 2011, at 8:35 AM, Kay Schenk wrote:
On 08/06/2011 09:03 PM, Dave Fisher wrote:
On Aug 4, 2011, at 12:16 PM, Kay Schenk wrote:
I just wanted to report that this script worked just fine as near
as I can tell.
Great. When I did the work for the www and download project I used a
different script which is still a stub as there was a hand editing
step to correct inconsistent line endings.
The post about the script has shown up in several places, but
placing it as its own subject seemed appropriate.
yes...it got buried! :)
Now back to investigating headers/footers.
I added a page to the wiki with some of my thoughts today about
headers and footers for the websites including the MediaWiki and User
Forums.
https://cwiki.apache.org/confluence/display/OOOUSERS/Website+Template
good! this needs regular updating as we iron out issues...I'll take a look
I am going to try a new template/skeleton.html tomorrow.
Regards, Dave
OK, I'm going to try to start "migrating" some of the old OO.o pages to the
"www" area on Apache today. I won't link them in to anything. This will just be for my
educa
Re: [www] OOo Website Conversion
On 08/13/2011 09:58 PM, Dave Fisher wrote:
Hi -
I have modified the template process.
For html files the head and body content are extracted and then
placed into the template.
super!
The wrapping is good. There is still work to do with getting to a
single version of the css and javascript.
I'm not sure what you mean by this??? Do you mean trying to incorporate
the .css file in download w/ the .css in content/openofficeorg/css?
Or...do you mean a referencing problem? That is -- it seems the top area
for the web site is
https://svn.apache.org/repos/asf/incubator/ooo/site/trunk/content/openofficeorg/
Does this mean *all* styles should reside in --
https://svn.apache.org/repos/asf/incubator/ooo/site/trunk/content/openofficeorg/css
Really I don't know what you mean by your statement.
What is notable it that http://incubator.apache.org/openofficeorg/www
and http://incubator.apache.org/openofficeorg/download are now
connected and have good layout and function.
Next step it work on the footer.
On Aug 9, 2011, at 1:09 AM, Dave Fisher wrote:
On Aug 9, 2011, at 12:22 AM, Marcus (OOo) wrote:
When you look at
"http://incubator.apache.org/openofficeorg/download/index.html";
the sidenav is not really turned off. It's just without content
but the indent still remains. Is that what you wanted? If so, the
space is IMHO too much wasted as you can especially see here:
"http://incubator.apache.org/openofficeorg/download/other.html";
Taken care of.
And also here
"http://incubator.apache.org/openofficeorg/www/index.html"; we
still have a bit to do. :-P
We do have a lot to do. It is not always a direct path and I am
learning a lot! We will need to make some choices about page
layouts. Where do we want to have the different types of pages? How
much is special and how much fits a "cookie cutter" model?
Getting close here as well.
Regards, Dave
Thanks a lot for unifying the styles. :-)
It is very much my pleasure!
I am looking forward to your ideas.
Regards, Dave
Marcus
- header and footer framework
For tomorrow.
- online cms editing of html
Confirmed the editing of html. There is syntax coloring in the
CMS WebGUI.
- scripting of Kenai html into CMS compatible - stripping
of headers and extraction of javascript and css.
To be discussed. It depends on how many sets of special page
styles are really needed. Here is how it currently works:
Here is the script for wrapping the html:
sub html_page { my %args = @_; my %styleargs = @_; my $file =
"content$args{path}"; my $template = $args{template};
$args{breadcrumbs} = breadcrumbs($args{path});
read_text_file $file, \%args;
my $page_path = $file; $page_path =~ s/\.[^.]+$/.page/; if (-d
$page_path) { for my $f (grep -f, glob "$page_path/*.mdtext")
{ $f =~ m!/([^/]+)\.mdtext$! or die "Bad filename: $f\n";
$args{$1} = {}; read_text_file $f, $args{$1}; } }
my $style_path = $file; $style_path =~ s/\.[^.]+$/.style/; if
(-f $style_path) { read_text_file $style_path, \%styleargs;
$args{scriptstyle} = $styleargs{content}; }
return Template($template)->render(\%args), html => \%args;
}
Which interacts with templates/skeleton.html
{% block title %}{{ headers.title }}{% endblock
%}
{% autoescape off %}{% if scriptstyle %}{{ scriptstyle }}{%
else %}{% include "scriptstyle.html"%}{% endif %}{%
endautoescape %}
So you see there is a default location for css and javascript.
The question is if there should be a set of selectable
javascript/css templates, or if we want to have these files be
next to the file they apply to.
If we go to a specific set of templates method then we would
change to:
{% autoescape off %}{% if scriptstyle %}{% include scriptstyle
%}{% else %}{% include "scriptstyle.html"%}{% endif %}{%
endautoescape %}
Regards, Dave
Regards, Dave
On Aug 7, 2011, at 8:35 AM, Kay Schenk wrote:
On 08/06/2011 09:03 PM, Dave Fisher wrote:
On Aug 4, 2011, at 12:16 PM, Kay Schenk wrote:
I just wanted to report that this script worked just
fine as near as I can tell.
Great. When I did the work for the www and download
project I used a different script which is still a stub
as there was a hand editing step to correct
inconsistent line endings.
The post about the script has shown up in several
places, but placing it as its own subject seemed
appropriate.
yes...it got buried! :)
Now back to investigating headers/footers.
I added a page to the wiki with some of my thoughts
today about headers and footers for the websites
including the MediaWiki and User Forums.
https://cwiki.apache.org/confluence/display/OOOUSERS/Website+Template
good! this needs regular updating as we iron out issues...I'll take a look
I am going to try a new template/skeleton.html
tomorrow.
Regards, Dave
OK, I'm going to try to start "migrating" some of the old
OO.o pages to the "www" area on Apache today. I won't
link them in to anything. This will just be for my
education at this point.
So, I am kind of wonder
Re: [www] OOo Website Conversion
On Aug 14, 2011, at 8:17 AM, Kay Schenk wrote:
>
>
> On 08/13/2011 09:58 PM, Dave Fisher wrote:
>> Hi -
>>
>> I have modified the template process.
>>
>> For html files the head and body content are extracted and then
>> placed into the template.
>
> super!
>
>>
>> The wrapping is good. There is still work to do with getting to a
>> single version of the css and javascript.
>
> I'm not sure what you mean by this??? Do you mean trying to incorporate the
> .css file in download w/ the .css in content/openofficeorg/css?
>
> Or...do you mean a referencing problem? That is -- it seems the top area for
> the web site is
>
> https://svn.apache.org/repos/asf/incubator/ooo/site/trunk/content/openofficeorg/
Referencing will be an issue given the path in the incubator and that each
subdomain is currently within a single domain as a subdirectory.
>
> Does this mean *all* styles should reside in --
>
> https://svn.apache.org/repos/asf/incubator/ooo/site/trunk/content/openofficeorg/css
>
> Really I don't know what you mean by your statement.
I think it is a reasonable goal for all common css and js to be in a single
place. But that is only a goal. Functionality is most important.
Regards,
Dave
>
>>
>> What is notable it that http://incubator.apache.org/openofficeorg/www
>> and http://incubator.apache.org/openofficeorg/download are now
>> connected and have good layout and function.
>>
>> Next step it work on the footer.
>>
>> On Aug 9, 2011, at 1:09 AM, Dave Fisher wrote:
>>
>>>
>>> On Aug 9, 2011, at 12:22 AM, Marcus (OOo) wrote:
>>
>>
>>
>>
>>>
When you look at
"http://incubator.apache.org/openofficeorg/download/index.html";
the sidenav is not really turned off. It's just without content
but the indent still remains. Is that what you wanted? If so, the
space is IMHO too much wasted as you can especially see here:
"http://incubator.apache.org/openofficeorg/download/other.html";
>>
>> Taken care of.
>>
>>
>>
And also here
"http://incubator.apache.org/openofficeorg/www/index.html"; we
still have a bit to do. :-P
>>>
>>> We do have a lot to do. It is not always a direct path and I am
>>> learning a lot! We will need to make some choices about page
>>> layouts. Where do we want to have the different types of pages? How
>>> much is special and how much fits a "cookie cutter" model?
>>
>> Getting close here as well.
>>
>> Regards, Dave
>>
>>
>>>
Thanks a lot for unifying the styles. :-)
>>>
>>> It is very much my pleasure!
>>>
>>> I am looking forward to your ideas.
>>>
>>> Regards, Dave
>>>
>>>
Marcus
>>> - header and footer framework
>
> For tomorrow.
>
>>> - online cms editing of html
>
> Confirmed the editing of html. There is syntax coloring in the
> CMS WebGUI.
>
>>> - scripting of Kenai html into CMS compatible - stripping
>>> of headers and extraction of javascript and css.
>
> To be discussed. It depends on how many sets of special page
> styles are really needed. Here is how it currently works:
>
> Here is the script for wrapping the html:
>
> sub html_page { my %args = @_; my %styleargs = @_; my $file =
> "content$args{path}"; my $template = $args{template};
> $args{breadcrumbs} = breadcrumbs($args{path});
>
> read_text_file $file, \%args;
>
> my $page_path = $file; $page_path =~ s/\.[^.]+$/.page/; if (-d
> $page_path) { for my $f (grep -f, glob "$page_path/*.mdtext")
> { $f =~ m!/([^/]+)\.mdtext$! or die "Bad filename: $f\n";
> $args{$1} = {}; read_text_file $f, $args{$1}; } }
>
> my $style_path = $file; $style_path =~ s/\.[^.]+$/.style/; if
> (-f $style_path) { read_text_file $style_path, \%styleargs;
> $args{scriptstyle} = $styleargs{content}; }
>
> return Template($template)->render(\%args), html => \%args;
> }
>
> Which interacts with templates/skeleton.html
>
> {% block title %}{{ headers.title }}{% endblock
> %}
>
> {% autoescape off %}{% if scriptstyle %}{{ scriptstyle }}{%
> else %}{% include "scriptstyle.html"%}{% endif %}{%
> endautoescape %}
>
> So you see there is a default location for css and javascript.
>
> The question is if there should be a set of selectable
> javascript/css templates, or if we want to have these files be
> next to the file they apply to.
>
> If we go to a specific set of templates method then we would
> change to:
>
> {% autoescape off %}{% if scriptstyle %}{% include scriptstyle
> %}{% else %}{% include "scriptstyle.html"%}{% endif %}{%
> endautoescape %}
>
> Regards, Dave
>
>
>>>
>>> Regards, Dave
>>>
>>> On Aug 7, 2011, at 8:35 AM, Kay Schenk wrote:
>>>
On 08/06/2011 09:03 PM, Dave Fisher wrote:
>
> On Aug 4, 2
Re: [www] OOo Website Conversion
On Aug 14, 2011, at 3:07 AM, Marcus (OOo) wrote:
> Am 08/14/2011 06:58 AM, schrieb Dave Fisher:
>> Hi -
>>
>> I have modified the template process.
>>
>> For html files the head and body content are extracted and then placed into
>> the template.
>>
>> The wrapping is good. There is still work to do with getting to a single
>> version of the css and javascript.
>>
>> What is notable it that http://incubator.apache.org/openofficeorg/www and
>> http://incubator.apache.org/openofficeorg/download are now connected and
>> have good layout and function.
>
> Looks great. Thanks a lot for taking care about the CSS stuff. :-)
>
>> Next step it work on the footer.
>
> Currently this is the text:
> "Copyright © 2011 The Apache Software Foundation, Licensed under the Apache
> License, Version 2.0.
> Apache and the Apache feather logos are trademarks of The Apache Software
> Foundation."
>
> I don't know if something is missing. However, 1-2 links more to respective
> Apache websites for details would be helpful.
Certainly something is missing. We will include terms of use. We must mention
that we are incubating. We should mention that one of the tasks is to clear up
copyright, licensing and any other IP issues.
We'll need to have the Apache Incubator logo somewhere.
Regards,
Dave
>
> Marcus
>
>
>
>> On Aug 9, 2011, at 1:09 AM, Dave Fisher wrote:
>>
>>>
>>> On Aug 9, 2011, at 12:22 AM, Marcus (OOo) wrote:
>>
>>
>>
>>
>>>
When you look at
"http://incubator.apache.org/openofficeorg/download/index.html"; the
sidenav is not really turned off. It's just without content but the indent
still remains. Is that what you wanted? If so, the space is IMHO too much
wasted as you can especially see here:
"http://incubator.apache.org/openofficeorg/download/other.html";
>>
>> Taken care of.
>>
>>
>>
And also here "http://incubator.apache.org/openofficeorg/www/index.html";
we still have a bit to do. :-P
>>>
>>> We do have a lot to do. It is not always a direct path and I am learning a
>>> lot! We will need to make some choices about page layouts. Where do we want
>>> to have the different types of pages? How much is special and how much fits
>>> a "cookie cutter" model?
>>
>> Getting close here as well.
>>
>> Regards,
>> Dave
>>
>>
>>>
Thanks a lot for unifying the styles. :-)
>>>
>>> It is very much my pleasure!
>>>
>>> I am looking forward to your ideas.
>>>
>>> Regards,
>>> Dave
>>>
>>>
Marcus
>>> - header and footer framework
>
> For tomorrow.
>
>>> - online cms editing of html
>
> Confirmed the editing of html. There is syntax coloring in the CMS WebGUI.
>
>>> - scripting of Kenai html into CMS compatible - stripping of headers
>>> and extraction of javascript and css.
>
> To be discussed. It depends on how many sets of special page styles are
> really needed. Here is how it currently works:
>
> Here is the script for wrapping the html:
>
> sub html_page {
>my %args = @_;
>my %styleargs = @_;
>my $file = "content$args{path}";
>my $template = $args{template};
>$args{breadcrumbs} = breadcrumbs($args{path});
>
>read_text_file $file, \%args;
>
>my $page_path = $file;
>$page_path =~ s/\.[^.]+$/.page/;
>if (-d $page_path) {
>for my $f (grep -f, glob "$page_path/*.mdtext") {
>$f =~ m!/([^/]+)\.mdtext$! or die "Bad filename: $f\n";
>$args{$1} = {};
>read_text_file $f, $args{$1};
>}
>}
>
>my $style_path = $file;
>$style_path =~ s/\.[^.]+$/.style/;
>if (-f $style_path) {
>read_text_file $style_path, \%styleargs;
>$args{scriptstyle} = $styleargs{content};
>}
>
>return Template($template)->render(\%args), html => \%args;
> }
>
> Which interacts with templates/skeleton.html
>
> {% block title %}{{ headers.title }}{% endblock %}
>
> {% autoescape off %}{% if scriptstyle %}{{ scriptstyle }}{% else %}{%
> include "scriptstyle.html"%}{% endif %}{% endautoescape %}
>
> So you see there is a default location for css and javascript.
>
> The question is if there should be a set of selectable javascript/css
> templates, or if we want to have these files be next to the file they
> apply to.
>
> If we go to a specific set of templates method then we would change to:
>
> {% autoescape off %}{% if scriptstyle %}{% include scriptstyle %}{% else
> %}{% include "scriptstyle.html"%}{% endif %}{% endautoescape %}
>
> Regards,
> Dave
>
>
>>>
>>> Regards,
>>> Dave
>>>
>>> On Aug 7, 2011, at 8:35 AM, Kay Schenk wrote:
>>>
On 08/06/2011 09:03 PM, Dave
Re: [www] OOo Website Conversion
On Sun, Aug 14, 2011 at 5:33 PM, Dave Fisher wrote:
>
> On Aug 14, 2011, at 3:07 AM, Marcus (OOo) wrote:
>
> > Am 08/14/2011 06:58 AM, schrieb Dave Fisher:
> >> Hi -
> >>
> >> I have modified the template process.
> >>
> >> For html files the head and body content are extracted and then placed
> into the template.
> >>
> >> The wrapping is good. There is still work to do with getting to a single
> version of the css and javascript.
> >>
> >> What is notable it that http://incubator.apache.org/openofficeorg/wwwand
> http://incubator.apache.org/openofficeorg/download are now connected and
> have good layout and function.
> >
> > Looks great. Thanks a lot for taking care about the CSS stuff. :-)
> >
> >> Next step it work on the footer.
> >
> > Currently this is the text:
> > "Copyright © 2011 The Apache Software Foundation, Licensed under the
> Apache License, Version 2.0.
> > Apache and the Apache feather logos are trademarks of The Apache Software
> Foundation."
> >
> > I don't know if something is missing. However, 1-2 links more to
> respective Apache websites for details would be helpful.
>
> Certainly something is missing. We will include terms of use. We must
> mention that we are incubating. We should mention that one of the tasks is
> to clear up copyright, licensing and any other IP issues.
>
> We'll need to have the Apache Incubator logo somewhere.
>
Assuming the transfer has now gone through, we also need to mention the
OpenOffice.org trademark and the Gulls graphic.
>
> Regards,
> Dave
>
> >
> > Marcus
> >
> >
> >
> >> On Aug 9, 2011, at 1:09 AM, Dave Fisher wrote:
> >>
> >>>
> >>> On Aug 9, 2011, at 12:22 AM, Marcus (OOo) wrote:
> >>
> >>
> >>
> >>
> >>>
> When you look at "
> http://incubator.apache.org/openofficeorg/download/index.html"; the sidenav
> is not really turned off. It's just without content but the indent still
> remains. Is that what you wanted? If so, the space is IMHO too much wasted
> as you can especially see here: "
> http://incubator.apache.org/openofficeorg/download/other.html";
> >>
> >> Taken care of.
> >>
> >>
> >>
>
> And also here "
> http://incubator.apache.org/openofficeorg/www/index.html"; we still have a
> bit to do. :-P
> >>>
> >>> We do have a lot to do. It is not always a direct path and I am
> learning a lot! We will need to make some choices about page layouts. Where
> do we want to have the different types of pages? How much is special and how
> much fits a "cookie cutter" model?
> >>
> >> Getting close here as well.
> >>
> >> Regards,
> >> Dave
> >>
> >>
> >>>
>
> Thanks a lot for unifying the styles. :-)
> >>>
> >>> It is very much my pleasure!
> >>>
> >>> I am looking forward to your ideas.
> >>>
> >>> Regards,
> >>> Dave
> >>>
> >>>
>
> Marcus
>
>
>
> >>> - header and footer framework
> >
> > For tomorrow.
> >
> >>> - online cms editing of html
> >
> > Confirmed the editing of html. There is syntax coloring in the CMS
> WebGUI.
> >
> >>> - scripting of Kenai html into CMS compatible - stripping of
> headers and extraction of javascript and css.
> >
> > To be discussed. It depends on how many sets of special page styles
> are really needed. Here is how it currently works:
> >
> > Here is the script for wrapping the html:
> >
> > sub html_page {
> >my %args = @_;
> >my %styleargs = @_;
> >my $file = "content$args{path}";
> >my $template = $args{template};
> >$args{breadcrumbs} = breadcrumbs($args{path});
> >
> >read_text_file $file, \%args;
> >
> >my $page_path = $file;
> >$page_path =~ s/\.[^.]+$/.page/;
> >if (-d $page_path) {
> >for my $f (grep -f, glob "$page_path/*.mdtext") {
> >$f =~ m!/([^/]+)\.mdtext$! or die "Bad filename: $f\n";
> >$args{$1} = {};
> >read_text_file $f, $args{$1};
> >}
> >}
> >
> >my $style_path = $file;
> >$style_path =~ s/\.[^.]+$/.style/;
> >if (-f $style_path) {
> >read_text_file $style_path, \%styleargs;
> >$args{scriptstyle} = $styleargs{content};
> >}
> >
> >return Template($template)->render(\%args), html => \%args;
> > }
> >
> > Which interacts with templates/skeleton.html
> >
> > {% block title %}{{ headers.title }}{% endblock %}
> >
> > {% autoescape off %}{% if scriptstyle %}{{ scriptstyle }}{% else %}{%
> include "scriptstyle.html"%}{% endif %}{% endautoescape %}
> >
> > So you see there is a default location for css and javascript.
> >
> > The question is if there should be a set of selectable javascript/css
> templates, or if we want to have these files be next to the file they apply
> to.
> >
> > If we go to a specific set of templates method then we would change
> to:
> >
> > {% autoescape off %}{% if scriptst
Re: [www] OOo Website Conversion
On Sun, Aug 14, 2011 at 9:30 AM, Dave Fisher wrote: > > On Aug 14, 2011, at 8:17 AM, Kay Schenk wrote: > > > > > > > On 08/13/2011 09:58 PM, Dave Fisher wrote: > >> Hi - > >> > >> I have modified the template process. > >> > >> For html files the head and body content are extracted and then > >> placed into the template. > > > > super! > Dave-- One quick question since you seem to be on a roll here! :) I guess I was thinking we would (for the time being) use the existing sidenav on ALL pages...can you get that to load into your test "download" area along with the headers/footers AND what you ported over to "www" (currently not linked). Thanks. > <-- snipped --> > > -- --- MzK "Those who love deeply never grow old; they may die of old age, but they die young." -- Sir Arthur Pinero
Re: [www] OOo Website Conversion
On Aug 16, 2011, at 8:38 AM, Kay Schenk wrote: > On Sun, Aug 14, 2011 at 9:30 AM, Dave Fisher wrote: > >> >> On Aug 14, 2011, at 8:17 AM, Kay Schenk wrote: >> >>> >>> >>> On 08/13/2011 09:58 PM, Dave Fisher wrote: Hi - I have modified the template process. For html files the head and body content are extracted and then placed into the template. >>> >>> super! >> > > Dave-- > > One quick question since you seem to be on a roll here! :) > > I guess I was thinking we would (for the time being) use the existing > sidenav on ALL pages...can you get that to load into your test "download" > area along with the headers/footers AND what you ported over to "www" > (currently not linked). Some of these pages in download and www do not fit well with side nav. I'll think about how to make sidenav optional with a default of being on. I think we need breadcrumbs and a high level top nav. I plan to look at contributing, support and development as the next projects Regards, Dave > > Thanks. > > >> <-- snipped --> >> >> > > > -- > --- > MzK > > "Those who love deeply never grow old; > they may die of old age, but they die young." >-- Sir Arthur Pinero
Re: [www] OOo Website Conversion
On 08/16/2011 09:02 AM, Dave Fisher wrote: On Aug 16, 2011, at 8:38 AM, Kay Schenk wrote: On Sun, Aug 14, 2011 at 9:30 AM, Dave Fisher wrote: On Aug 14, 2011, at 8:17 AM, Kay Schenk wrote: On 08/13/2011 09:58 PM, Dave Fisher wrote: Hi - I have modified the template process. For html files the head and body content are extracted and then placed into the template. super! Dave-- One quick question since you seem to be on a roll here! :) I guess I was thinking we would (for the time being) use the existing sidenav on ALL pages...can you get that to load into your test "download" area along with the headers/footers AND what you ported over to "www" (currently not linked). Some of these pages in download and www do not fit well with side nav. well...OK. I only suggested this since really I don't feel the need to continue the same style (with the tab navigation) for the incubator project, but we need SOME way to provide navigation to other areas of the incubator project. We could always change the "body" styling in some way so we do a consistent sidenav for all pages. Thoughts on this. I'll think about how to make sidenav optional with a default of being on. I think we need breadcrumbs and a high level top nav. hmmm... OK I plan to look at contributing, support and development as the next projects OK. Really you're doing a LOT here. I had intended to start bringing stuff over as well , but wanted to work on a more coprehensive migration plan first. This being said, I'm pretty sure we'll want to move all the "accepted" projects (except for "infrastructure") as they are. I'll take a look at what you're doing via svn and see if I can help in any way. Regards, Dave -- MzK "Those who love deeply never grow old; they may die of old age, but they die young." -- Sir Arthur Pinero
[www] OOo Website Conversion (was: Re: Moving OOo web: results of fetch-all-web.sh)
Hi -
Progress.
On Aug 8, 2011, at 8:38 AM, Kay Schenk wrote:
> On 08/08/2011 08:29 AM, Dave Fisher wrote:
>> Hi Kay,
>>
>> I was able to get HTML wrapped using the Apache CMS last night. I'm not
>> ready to commit anything yet. I'll summarize where I am and possible next
>> steps.
>>
>> In order to make progress the key was investigating the source for the {% %}
>> template tagging. This is found here:
>>
>> cms/build/lib/Dotiac/DTL/Tag
>>
>> I changed view.pm to include an html_page procedure
>>
>> In path.pm I added a pattern for html wrapping.
>>
>> our @patterns = (
>> [qr!\.mdtext$!, single_narrative => { template =>
>> "single_narrative.html" }],
>> [qr!\.html$!, html_page => { template => "html_page.html" }],
>> ) ;
>
> ah! good! So this can be parsed on a page by page basis? If so, super!
>
>
>>
>> The template html_page.html looks a lot like single_narrative.html but adds
>> an override to the content block.
>>
>> {% extends "skeleton.html" %}
>> {% block content %}{% autoescape off %}{{ content }}{% endautoescape %}{%
>> endblock %}
Now is this:
{% extends "skeleton.html" %}
{% block content %}{% autoescape off %}{{ content }}{% endautoescape %}{%
endblock %}
{$ endextends $}
>>
>> We keep a single skeleton which is good.
>
> This is great news! Thanks for your wonderful insights and work!
You are welcome. With a few tweaks things are committed and the process works!
>
>>
>> Next steps are
>>
>> - blocks for javascript and css insertion.
For testing purposes I split the www/index.html into an index.style and
shortened index.html.
I'm not sure if this is best or if the split needs to be done while processing
the view. This is a subject for tomorrow.
Also, this page needs a lot of work on styles to make it look like before.
Kenai stores content in places we may not have access to via the svn repos like
"branding"
>> - controlling sidenav. The current html_page.html is not very good for the
>> pages that Carl modified in the download directory.
For all html wrapped content I now turn off the sidenav. For mdtext the sidenav
remains.
>> - header and footer framework
For tomorrow.
>> - online cms editing of html
Confirmed the editing of html. There is syntax coloring in the CMS WebGUI.
>> - scripting of Kenai html into CMS compatible - stripping of headers and
>> extraction of javascript and css.
To be discussed. It depends on how many sets of special page styles are really
needed. Here is how it currently works:
Here is the script for wrapping the html:
sub html_page {
my %args = @_;
my %styleargs = @_;
my $file = "content$args{path}";
my $template = $args{template};
$args{breadcrumbs} = breadcrumbs($args{path});
read_text_file $file, \%args;
my $page_path = $file;
$page_path =~ s/\.[^.]+$/.page/;
if (-d $page_path) {
for my $f (grep -f, glob "$page_path/*.mdtext") {
$f =~ m!/([^/]+)\.mdtext$! or die "Bad filename: $f\n";
$args{$1} = {};
read_text_file $f, $args{$1};
}
}
my $style_path = $file;
$style_path =~ s/\.[^.]+$/.style/;
if (-f $style_path) {
read_text_file $style_path, \%styleargs;
$args{scriptstyle} = $styleargs{content};
}
return Template($template)->render(\%args), html => \%args;
}
Which interacts with templates/skeleton.html
{% block title %}{{ headers.title }}{% endblock %}
{% autoescape off %}{% if scriptstyle %}{{ scriptstyle }}{% else %}{% include
"scriptstyle.html"%}{% endif %}{% endautoescape %}
So you see there is a default location for css and javascript.
The question is if there should be a set of selectable javascript/css
templates, or if we want to have these files be next to the file they apply to.
If we go to a specific set of templates method then we would change to:
{% autoescape off %}{% if scriptstyle %}{% include scriptstyle %}{% else %}{%
include "scriptstyle.html"%}{% endif %}{% endautoescape %}
Regards,
Dave
>>
>> Regards,
>> Dave
>>
>> On Aug 7, 2011, at 8:35 AM, Kay Schenk wrote:
>>
>>>
>>>
>>> On 08/06/2011 09:03 PM, Dave Fisher wrote:
On Aug 4, 2011, at 12:16 PM, Kay Schenk wrote:
> I just wanted to report that this script worked just fine as near
> as I can tell.
Great. When I did the work for the www and download project I used a
different script which is still a stub as there was a hand editing
step to correct inconsistent line endings.
> The post about the script has shown up in several places, but
> placing it as its own subject seemed appropriate.
>>>
>>> yes...it got buried! :)
>>>
>
> Now back to investigating headers/footers.
I added a page to the wiki with some of my thoughts today about
headers and footers for the websites including the MediaWiki and User
Forums.
https://cwiki.apache.org/confluence/display/OOOUSERS/Website+Tem
