Wow, that was a lot, but very informative (I have at least 5 markers for deeper analysis)...but it seems that the top-menu is part of the fixed design, even the product page uses it. But the product page shows a nice way of adding another menu system, which I will use.
Give me a day or two, and I will have that updated. As Alexandro pointed out, the site is not big or with big content, that is on purpose, I wanted to establish a "bare bottom" from where we can build. If there are other comments, or suggestions, please let me know, and I will include it in the update. rob: I hope it is ok, that I bother you to update the site again later this week ? On 31 October 2012 22:06, jan iversen <[email protected]> wrote: > Thanks for a swift answer, I will have a look at it, and send you a new > version...I want to adhere to standards !! > > I might rebel from time to time, but then I try to get the standard > changed instead of violating it. > > Jan. > > > On 31 October 2012 21:44, Rob Weir <[email protected]> wrote: > >> On Wed, Oct 31, 2012 at 4:26 PM, jan iversen <[email protected]> >> wrote: >> > Someday I will learn how the templates work. I looked at one wiki page, >> > that explained to use sort of variables, where the merged part should >> go. >> > How a template can merge into a full html, well thats pure magic. >> > >> > I to not want a special top or bottom....but I do want different menus, >> > since l10n has different topics. So if the template mingles with header >> and >> > body until the menu part, and again on the bottom (apache logo etc.) I >> will >> > be more than happy to use the template. >> > >> >> I have not looked into it, but this part of the website seems to >> handle a local look and feel, along with the site-wide parts: >> >> http://www.openoffice.org/product/index.html >> >> Maybe reading through the way it was done here might help: >> >> >> https://svn.apache.org/repos/asf/incubator/ooo/ooo-site/trunk/content/product/ >> >> It looks like they did it entirely as Markdown Text. But that is a >> minor detail. >> >> The real magic happens here, I think, where the site templates are >> defined: >> https://svn.apache.org/repos/asf/incubator/ooo/ooo-site/trunk/templates/ >> >> Note especially: >> >> https://svn.apache.org/repos/asf/incubator/ooo/ooo-site/trunk/templates/product/ssi.mdtext >> >> Ah, and that then points back to: >> >> https://svn.apache.org/repos/asf/incubator/ooo/ooo-site/trunk/content/product/leftnav.mdtext >> >> I'd recommend poking around. Or, if you think the look and feel of >> the "product" part of the website is good, maybe even just copy that >> and change the content of the left navigator to reflect the links that >> you want to highlight? >> >> -Rob >> >> >> >> >> > jan >> > >> > On 31 October 2012 19:42, Rob Weir <[email protected]> wrote: >> > >> >> On Wed, Oct 31, 2012 at 2:14 PM, jan iversen <[email protected]> >> >> wrote: >> >> > Rob: I did not quite understand the part about google analytics, >> should I >> >> > change something ?? >> >> > >> >> >> >> I'd like to hear what Dave thinks on this. He set up the site-wide >> >> template originally. >> >> >> >> > I checked in SVN, and saw that both ooo/index.html and >> >> ooo/l10n/index.html >> >> > was committed with the complete html, I had expected the SVN part to >> be >> >> the >> >> > text that goes into the template? >> >> > >> >> >> >> Generally we check in complete HTML pages, with <html>, <head> and >> >> <body>. The template is then applied it does its magic, which >> >> apparently merges elements in the <head>, applies navigation >> >> breadcrumbs, the constant license footer, consistent branding on the >> >> header, etc. I don't fully understand how it works, but most content >> >> authors can just ignore it. It works that well that most can just >> >> ignore. >> >> >> >> But it looks like you want to adjust the template. We'll see what >> >> Dave thinks on this. Maybe we need to pipeline things so your changes >> >> are applied and then the site template is applied. (It kind of looks >> >> like this is happening now). >> >> >> >> > I do not like to copy the top/bottom into every page, which is why I >> >> used >> >> > the snip thing. >> >> > >> >> >> >> Right. But I think what we're seeing now is a fight between the >> >> site-wide rules and the local ones. >> >> >> >> -Rob >> >> >> >> >> >> > Jan. >> >> > >> >> > On 31 October 2012 19:10, Rob Weir <[email protected]> wrote: >> >> > >> >> >> On Wed, Oct 31, 2012 at 2:05 PM, Alexandro Colorado <[email protected]> >> >> wrote: >> >> >> > On 10/31/12, Rob Weir <[email protected]> wrote: >> >> >> >> http://www.openoffice.org/l10n-new/ >> >> >> > >> >> >> > why do we have a different directory, wouldnt it be just better to >> >> have >> >> >> > >> >> >> > http://www.openoffice.org/l10n/new.html >> >> >> > >> >> >> > Doesnt make sense to have two Localization projects/folders. >> >> >> > >> >> >> >> >> >> Long term, it does not. For review it is perfectly fine. Once >> we've >> >> >> debugged it and are agreed on the new site, then of course we >> replace >> >> >> the old directory with this one. >> >> >> >> >> >> -Rob >> >> >> >> >> >> >> >> >> >> >> This is based on a contribution from Jan. >> >> >> >> >> >> >> >> You can look at the source is Subversion: >> >> >> >> >> >> >> >> >> >> https://svn.apache.org/repos/asf/incubator/ooo/ooo-site/trunk/content/l10n-new/ >> >> >> >> >> >> >> >> It looks like Jan is trying some clever work customizing the >> website >> >> >> >> template and server-side includes. But it looks like it is >> >> >> >> conflicting with (or is being applied in duplicate to) the >> site-wide >> >> >> >> template. >> >> >> >> >> >> >> >> Dave might have some ideas here. But in general I think we want >> to >> >> >> >> avoid having duplicate copies of site-wide items, like Google >> >> >> >> Analytics declarations. >> >> >> >> >> >> >> >> -Rob >> >> >> >> >> >> >> > >> >> >> > >> >> >> > -- >> >> >> > Alexandro Colorado >> >> >> > PPMC Apache OpenOffice >> >> >> > http://es.openoffice.org >> >> >> >> >> >> > >
