Samer, I'm available to help make old content in html and new content in both html and mdtext be properly extracted into new design templates using the Apache CMS.
On Mar 31, 2013, at 12:12 PM, Samer Mansour wrote: > Dave, > > We can consider not using a single CSS or template for the entire site. > Rather we would partition the website and apply CSS and templates according > to their context or navigation depth. There is currently a structure to activate topnav, leftnav, and rightnav elements at only the topmost directory level. This is mostly, but not completely for NL sites. This was kept simple on purpose. The SSIs are in place to allow changes to the template without having to change every page on the site. This was termed a "sledgehammer change". I did this a few times and Joe S. improved the CMS and we did SSI pieces. I suggest that there be as few templates as possible. Is there a sitemap planned for this website redesign? I don't think there ought to be many more designs than. - Home page - NL Home page - Download page - Content page - API generated page All other pages are variations on Content pages and that CSS should be able to handle things. If future content can be in mdtext instead of html then it is easily possible to have a header in the mdtext choose the template. For HTML content we can embed the template choice in a header comment. Defaults can be Content page and English. Work will be needed in ooo-site/trunk/templates/ and ooo-site/trunk/lib/. I'll help with that. JanI has plans for NL translated pages - we can factor that in as well. > > Maybe a single CSS for colours, fonts sizes, tables, etc. eg. lets call > this standard.css > The secondary pages, like module info and volunteer list, would have a CSS > for layout information. eg secondary.css > Homepage and Download pages would have a different layout CSS but still > inherent the font and colors from the first CSS. eg home.css and > download.css > > We may also consider moving the API to openoffice.apache.org and giving it > its own css / program an exemption for those. > It looks like a lot of links are broken right now as well. That would be on > the list as well for fixing. Please discuss api location on the dev list. There was discussion in the past about having the last release's api on openoffice.org and the current trunk continuously integrated onto openoffice.apache.org. Another point to moving any content to openoffice.apache.org is that redirections will be needed for all the external links that exist to the current location. The following workflow would be needed: (1) Copy api from ooo-site/trunk/content/api to ooo/trunk/content/api/. Will probably require moving the template and SSI logic from ooo-site/trunk/template and lib to site/trunk/template and lib/ (2) Resolve missing resources and css. Assure proper leftnav (conflicts with project leftnav). (3) Make sure that programmers like Jürgen are happy with the results. (4) Add redirect to openoffice.org's httpd.conf (5) Remove api from ooo-site/trunk/content and ooo-site/trunk/templates Regards, Dave > > Samer > > On Fri, Mar 29, 2013 at 6:48 PM, Dave Fisher <[email protected]> wrote: > >> Hi - >> >> When the time comes to do the web site redesign, let me know and I'll help >> provide any guidance on how the current template is fit together. >> >> I'm the person who did the bulk of the work moving the old into the Apache >> CMS. Don't let the current html fool you the way things work extracts >> everything needed for the page. Fair warning this can include css files. >> This means that it might be difficult to go contain the whole of the >> re-design to a single css - side effects from these other css will take >> time. openoffice.org/api is particularly tricky and has its own css to >> style generated content. >> >> Regards, >> Dave >> >> On Mar 27, 2013, at 5:31 AM, Robin Fowler wrote: >> >>> Hi Samer, >>> >>> I'm fine implementing the design, and we can do it together that sounds >> great. But I don't think it's a good idea to start with a web design >> without knowing the logo. The logo is the strongest visual element in the >> whole branding and i think the website (and in fact the entire brand >> design) should be tailored to the appearance of it. My proposal is >> obviously tailored to my own logo design, but if we decide to use a >> different logo then i would like to optimise the design for it. >>> >>> One thing you don't want is to implement a design and then change >> things. The most efficient way of doing this is making a mockup, optimising >> it and then implementing it 1:1 in html/css. >>> >>> I'm afraid I'm not up to date with the current status and have no idea >> if any proposals have been chosen/dismissed yet. >>> >>> So yes I'm fine helping out but wouldn't want to do this before a >> decision has been made. >>> >>> Robin >>> >>> >>> On 27 Mar 2013, at 03:12, Samer Mansour <[email protected]> wrote: >>> >>>> Robin, >>>> >>>> Would you be interested working together to come up with a new website >>>> template (html/css)? We would prioritize and size the work together. >>>> >>>> I would like to get this started in parallel with selecting a logo. I >>>> really liked your proposal and I think we can make a strong visual >> identity >>>> for the homepage and secondary pages. >>>> >>>> I want to keep openoffice.org end-user focused >>>> So we may move some pages over to openoffice.apache.org that are more >>>> project/development specific and vice versa. >>>> >>>> I am not excluding others from helping, I'm simply asking if you can do >>>> this. >>>> You have made a very good website proposal. >>>> >>>> Please let me know if you are interested. We can exchange and IM >> outside >>>> this mailing list to collaborate. >>>> >>>> Samer Mansour >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
