My recomendation is to edit the homepage first, and then moe to the rest of the site. This means, isolate the homepage, and then replicate through projects and documentation for other webdevs to aim at it.
First step would be to, replace the ooo.css to the boot-aoo.css and incorporate the Javascript. The rest of the sites will still use ooo.css. The next step would be to get some kind of documentation and scripts to auto-migrate the CSS/JS and HTML core elements. Finally use a debugging mechanism to flag possible issues to the template. My final and unrelated suggestion is to re-arquitect the way the file structure has been handled. Example: css/ ... header.css ... menu.css ... content.css ... footer.css ... form.css This will provide a better nd more granular manipulation of the css. On Thu, Jul 17, 2014 at 11:20 PM, Kay Schenk <kay.sch...@gmail.com> wrote: > > > On 07/17/2014 03:30 PM, Emanuele wrote: > > Hi, > > > > I'm trying to understand a bit the way the CMS builds the site in order > > to see how to put everything together. > > I think I got the basics. At least I think I understood what file does > > what (mostly). > > > > I am now looking at "navtop". > > Do you mean "topnav"? I can't find any reference to "navtop". > > > If I got it right, the navtop.mdtext is parsed as markdown (and it > > generates an <ul>) and the result is put into the content block in > > navigator.html. > > markdown generates plain html without classes and/or other attributes. > > I'm not totally sure what you're asking but the classes for the current > "topnav" elements are defined in > > http://www.openoffice.org/css/ooo.css > > Given that I am not familiar with bootstrap, this may not be a good > answer. We can use different styling for the home page if needed by > editing the paths used by the cms and basically cause it to bypass the > templating used in the rest of the site, and do something different for > "index.html". Does this help? > > We haven't really discussed if we would just want to make changes to the > home page or the whole site. > > As an information item, all of our current pages are more or less > rendered off -- > > > http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/templates/skeleton.html?revision=1522610&view=markup > > Taking a closer look at this version -- > http://testing.elkarte.it/ooo/index_scroll.html > > we should look at how some of the underlying pages render if we moved > the placement of the top navigator items. My opinion -- regardless how > many elements from a newer design we incorporate into other pages, I > think the topnav element should be at the same place in all pages. > > > > > > > Bootstrap, on the contrary, requires to assign quite a bit of classes, > > because it relies on that to apply styles and attach javascript > > events/effects. > > So, the question is: is there any way to apply classes to the <ul> and > > <li> elements of navtop without having to use raw html? > > Yeah, I could use javascript, though it would be better to have > > everything in place in the html. > > > > Best regards, > > emanuele > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > > For additional commands, e-mail: dev-h...@openoffice.apache.org > > > > -- > ------------------------------------------------------------------------- > MzK > > "To be trusted is a greater compliment than being loved." > -- George MacDonald > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > -- Alexandro Colorado Apache OpenOffice Contributor 882C 4389 3C27 E8DF 41B9 5C4C 1DB7 9D1C 7F4C 2614
