On Fri, Apr 5, 2013 at 8:01 AM, Milos Vujnovic <[email protected]>wrote:
> Hi Dave, > > my answers and comments are below. > > Thanks, > Milosh > > > > On 04/05/2013 04:28 AM, Dave Fisher wrote: > >> First an editorial comment. >> >> Why the Business emphasis on the front page? >> > > To my knowledge, one of the biggest demographics that are using OpenOffice > are businesses and students. > Let me know if you have any suggestions and I'll implement them into the > mockups. > > If I made a mistake about the demographics, I apologize as I wasn't > following all the email conversations due business obligations. > > Of course, if students are the largest audience I'll base the design > around that idea. > On the marketing aspect, design is first targeted with the largest > audience, then the smaller audience is mentioned and divided on the other > areas of the main design. > > > I like the idea of having people on the homepage. That is a proven technique. Our user base is quite diverse, so any one image is going to omit many categories of users. Maybe that could be an image slider, rotating multiple images? > >> Apache HTTPD Server with Apache Subversion and a custom CMS that allows >> publishing in many ways including Apache Maven and Apache Forrest. Apache >> Infrastructure is maintained by people involved with these and most other >> Apache projects. >> > > Thank you for explaining this. I think we're better off preparing the HTML > and then OpenOffice devs can implement it into Apache CMS or any other > custom system. > I'll have this in mind while working on other mockups although usually > there are no technical limitations or specific requirements for actual > designs. > > > >> Boilerplate html5 would be good. We just need to divide it up between >> template/frame components and the body. The CMS includes custom perl code >> which can do most anything in page construction. >> > > Great, sounds good. > Can you tell me where I can find more information about that perl code? > I'm interested on what it offers in page construction process, it sounds > very interesting. > > Here's a basic overview of the website anatomy. Start with a plain page like our license page: http://www.openoffice.org/license.html That's how it displays to users. But the source file that we edit is more basic: https://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/content/license.html Other parts of the page, like the footer, the navigator at top, the header and logo, the "We're on Pinterest" announcement, etc., are stored in separate source files and processed as Server Side Includes. You can see the global site templates here: https://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/templates/ And the perl script here: https://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/lib/ Note that the template can be overriden, so some parts of the website have an additional side panel, e.g., the Product pages: http://www.openoffice.org/product/index.html I think it would be fine to concentrate initially on the information design and the general website approach. I think what you've shown so far is much cleaner and appealing then what we have now. This is great! However, you might want to keep these technical considerations in mind. In the end we need humanly-editable, standards-based web pages that don't require proprietary tools to maintain. Beyond the server side includes we can't rely on server side processing, LAMP, etc. We'll also want to think of the pages in a modular way, so that common pieces like navigators, can be processed as Server Side Includes. Also, we'll want to think about what we put on the home page, but also what the look & feel would be for other plain pages, like the license page linked to above. Regards, -Rob > Best, > Milosh > > > > >> >> Regards, >> Dave >> >> /* >>> *//*Re: PSD and then convert to HTML with a responsive framework or use >>> Wordpress*/ >>> Yes actually that was one plan, PSD > HTML > Wordpress, but as I pointed >>> out above, we're not confined with Wordpress. >>> >>> -- >>> >>> To other collaborators - please feel free to comment out everything. >>> >>> If there are any copywriters involved, it would be great - I noticed >>> large "gap" inside current OpenOffice website - content is disorganized, >>> main points and features are not properly explained and placed (this is >>> extremely crucial to optin rates), and other details as well. If there are >>> content writers out there, I would like to hear their thoughts on this. I >>> can lend marketing perspective on it and we can work something out. >>> >>> Best, >>> Milosh >>> >>> >>> On 4/5/2013 12:40 AM, Andrea Pescetti wrote: >>> >>>> Milosh Vujnovic wrote: >>>> >>>>> http://techcolossus.com/**openoffice/OpenOffice-V01-**Milosh.jpg<http://techcolossus.com/openoffice/OpenOffice-V01-Milosh.jpg> >>>>> >>>> >>>> Quite nice! I remember that you had suggested two options, i.e., PSD >>>> and then convert to HTML with a responsive framework or use Wordpress. >>>> >>>> The first one may be architecturally feasible (the "Apache CMS" is not >>>> a real CMS, but a simple infrastructure to automate some inclusion of >>>> common elements and allow markdown syntax); on the other hand, Wordpress >>>> would be rather problematic, since we don't have a PHP-enabled >>>> infrastructure at the moment and storing pages in a database does not fit >>>> with the current workflow. I hope this attempt is not assuming that we can >>>> use Wordpress, or any LAMP CMS for that matter. >>>> >>>> Regards, >>>> Andrea. >>>> >>>> ------------------------------**------------------------------** >>>> --------- >>>> 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]> >> >> >
