openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcus <>
Subject Re: Help Wanted
Date Sun, 04 Sep 2016 22:00:09 GMT
Am 09/04/2016 11:25 PM, schrieb Andrea Pescetti:
> Eric Bastarache wrote:
>> My name is Eric Bastarache and I have experience in both web design
>> and development, and I am interested in contributing to improving the
>> look of the website(s) for OpenOffice.

welcome to our project. Knowledge in design *and* dev is not seen often 
here on the mailing list. This sounds promising.

> Welcome! Both the web and the code areas of OpenOffice require a bit of
> patience; we can guide you through all details (probably Marcus, who is
> the most prolific contributor to the website, will step in) but I'll
> give you some basic information on how the OpenOffice site differs from
> an ordinary site.
> First, it's all static HTML and markdown. Yes, no CMS, no preprocessing,
> no PHP, nothing. We do have some limited preprocessing in the form of
> server-side includes for some common DIVs, but that's all.

AFAIK we have decided in the past to keep all the content from the old 
Sun/Oracle times and to live with content and links that can get 
outdated over the time. Instead of migrating all stuff into a more 
modern and fancy website system which would be too much work.

 > JavaScript is used extensively to cope with server-side restrictions.

JS is used mostly in the download area (incl. the localized ones) to 
create the offered download links automatially. This depends on the AOO 
version which is currently out, the user's platform and language.

The remaining JS usage is only a bit here and there on the other webpages.

This was also done to offer the same look & feel for the other language 
areas but with localized content.

> The site is built through SVN commits. You can checkout the site (a few
> GBytes) with
> $ svn co
> As for building it locally, it uses an ASF (Apache Software Foundation)
> thing that is known as "the CMS" but has little to do with any CMS you
> would consider.

The large size consists mostly of 2 things:

- The website is localized (more or less all pages) in a lot of
   languages which multiplies the content and therefore also the size.
- A lot of files of zip, short movies, bigger graphics and PDFs are
   stored in SVN but not really available on the website.

> CSS: We are not using any CSS frameworks at the moment; not even JS
> frameworks despite the quite active use of JavaScript. Adopting one,
> though, wouldn't be an obstacle, since the site is built from static
> content anyway (so one would either use SASS and "watch" the files with
> Compass, or compile the CSS in any other way before committing).

We focus on a fast page load. Therefore no big JS and CSS frameworks. Of 
course this could be changed when the loading is still fast. However, 
the knowledge is not really existing to get the most of Angular.js, 
Node.js or others.

> Are you prepared to work with this constraints? Then we'd love to get
> some help and we can continue the discussion! If you have expertise with
> more modern web systems, we could still use your help somehow, so don't
> be scared in case.

Yes, it would be great if this plain vanilla approach and the limited 
server support doesn't scare you.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message