Hello Dave, I don't know how the website is organized yet, its going to take me some time to learn how it works currently.
Question: What does NL and SSI stand for. Do we currently maintain a site map diagram somewhere I can start from? Otherwise I'll start documenting a plan on the cwiki and keep feed back there. I'll need to confirm with dev list for satisfying their requirements as well, I did not know there needed to be the two versions of the API. Rob, I would target a subset of the pages according to google analytics traffic. Samer On Mon, Apr 1, 2013 at 7:54 AM, Milosh Vujnovic <[email protected]>wrote: > A comment on this if I may... I would disagree using multiple stylesheets, > which is highly A) unproductive and B) not recommended for page speed at > all. > I would suggest using creating mockups in PSD (clean look), then > converting them to HTML5/CSS3 using one of popular responsive frameworks - > Boilerplate for example which is a long-time favorite of mine. > > I'm not sure about comments on using Apache CMS vs. single css.... why not > start using different CMS? > Can somebody please let me know where I can find more info on Apache CMS? > > Having both worked on hi-profile commercial Wordpress themes, I would > suggest using Wordpress. > But of course, it cannot be perfect solution for everything so I would > like to listen to suggestions from other colleagues. > > Best, > Milosh > > > > On 4/1/2013 2:59 AM, Rob Weir wrote: > >> On Sun, Mar 31, 2013 at 3:12 PM, Samer Mansour <[email protected]> >> 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. >>> >>> 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. >>> >>> >> I think success in this area will be greatly enhanced if we make it a >> non-goal to encompass the entire openoffice.org website as it is >> today. I'd highly recommend focusing on a core website, with good >> up-to-date content, a good modern look, SEO optimized and with a >> well-defined method for localization. It can probably be done with 25 >> pages per language. >> >> Of course, we can also preserve, for historical or archival reasons, >> everything else. But l think we can take a data-driven approach to >> identify the pages that users actually use most, and focus the core >> website on that. >> >> -Rob >> >> 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: >>>>> marketing-unsubscribe@**openoffice.apache.org<[email protected]> >>>>> For additional commands, e-mail: marketing-help@openoffice.** >>>>> apache.org <[email protected]> >>>>> >>>>> >>>> >>>> ------------------------------**------------------------------** >>>> --------- >>>> To unsubscribe, e-mail: >>>> marketing-unsubscribe@**openoffice.apache.org<[email protected]> >>>> For additional commands, e-mail: >>>> marketing-help@openoffice.**apache.org<[email protected]> >>>> >>>> >>>> >> ------------------------------**------------------------------**--------- >> To unsubscribe, e-mail: >> marketing-unsubscribe@**openoffice.apache.org<[email protected]> >> For additional commands, e-mail: >> marketing-help@openoffice.**apache.org<[email protected]> >> >> >
