Sure - here is the plan:
In views.pm prior to rendering.
# default navbars and mdtext from templates folder.
my templates_folder = "templates";
if (-d $templates_folder) {
for my $f (grep -f, glob "$templates_folder/*.mdtext") {
$f =~ m!/([^/]+)\.mdtext$! or die "Bad filename: $f\n";
$args{$1} = {};
read_text_file $f, $args{$1};
}
}
# folder specific overrides
templates_folder = templatesfolder($args{path});
if (-d $templates_folder) {
for my $f (grep -f, glob "$templates_folder/*.mdtext") {
$f =~ m!/([^/]+)\.mdtext$! or die "Bad filename: $f\n";
$args{$1} = {};
read_text_file $f, $args{$1};
}
}
Assuming that one of the files is named "sidenav.mdtext"
In the skeleton.html:
{% if sidenav.content %}<div id="sidenav">{% filter markdown %}{{
sidenav.content }}{% endfilter %}</div>{% endif %}
There is no longer a need to have {% include "sidenav.mdtext" %} and
skeleton.html is simplified.
So you can see there is only one "to do" - writing a templatesfolder sub based
on breadcrumbs.
Regards,
Dave
On Jan 1, 2012, at 12:38 PM, Joe Schaefer wrote:
> Be sure to look over
>
> http://www.apache.org/dev/cmsref.html#navigation
>
>
> for ideas on how to organize per-dir navigation templates.
>
>
>
>> ________________________________
>> From: Dave Fisher <[email protected]>
>> To: "[email protected] Incubator" <[email protected]>
>> Sent: Sunday, January 1, 2012 3:12 PM
>> Subject: [WWW] Folder Level Navigation Bar Improvements
>>
>> This is a heads up on plans for implementing improvements to the website
>> navigation bars.
>>
>> The websites - both the podling and ooo-site will be enhanced to allow top,
>> left side and right side navigation bars at the folder level. Here are three
>> directions this effort can go.
>>
>> (1) Adding a left (or right) side navigation to the api focus area. I'll
>> discuss this in more detail below.
>>
>> (2) NLC project overrides to top navigation. The Swedish site is a good
>> first candidate as there is trouble with it - http://www.openoffice.org/sv/
>>
>> (3) Reorganizing the podling site. It would be good to add current API docs
>> and start thinking about a larger organization.
>>
>> All of the Kenai projects on the legacy had side navigation. This can be
>> recovered by altering your hosts file. I've examined this for API. Several
>> of the urls were already problematic. Here is an annotated version of
>> leftsidenav.mdtext (likely - templates/api/leftsidenav.mdtext)
>>
>> ? These pages are out of date.
>>> These pages were missing.
>>
>> # Developer's Guide
>>
>> - [Content
>> Table](http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/OpenOffice.org_Developers_Guide)
>> - [IDL
>> reference](http://www.openoffice.org/api/docs/common/ref/com/sun/star/module-ix.html)
>>> - [IDL Design
>>> Guide](http://www.openoffice.org/api/DevelopersGuide/Appendix/IDLDesignGuide/IDLDesignGuide.xhtml)
>>> - [IDL Docu
>>> Guide](http://www.openoffice.org/api/DevelopersGuide/Appendix/IDLDocumentationGuide/IDLDocumentationGuide.xhtml)
>>
>> # API
>>
>> ? - [Module structure](http://www.openoffice.org/api/modules.html)
>>
>> # SDK
>>
>> - [Examples](http://www.openoffice.org/api/SDK/example_collection.html)
>> - [Java UNO
>> Reference](http://www.openoffice.org/api/docs/java/ref/overview-summary.html)
>> - [C++ UNO
>> Reference](http://www.openoffice.org/api/docs/cpp/ref/names/index.html)
>> - [Download](http://www.openoffice.org/download/sdk/)
>>
>> # Tips 'n' Tricks
>>
>> - [FAQ](/api/faq.html)
>> - [Internal OO
>> Spots](http://www.openoffice.org/api/TipsAndTricks/internal.html)
>> - [External
>> Resources](http://www.openoffice.org/api/TipsAndTricks/external.html)
>>
>> # Miscellaneous
>>
>> - [Developer Projects](http://wiki.services.openoffice.org/wiki/API/To-Dos)
>> ? - [Mailing List Rules](http://www.openoffice.org/api/listrules.html)
>>> - [News Letter Archive](http://www.openoffice.org/api/NewsLetter/)
>>
>> Let me know what changes to make to this list. Feel free to update ooo-site.
>>
>> Regards,
>> Dave
>>