From dev-return-27635-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Fri Oct 03 07:22:22 2008 Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 57862 invoked from network); 3 Oct 2008 07:22:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Oct 2008 07:22:21 -0000 Received: (qmail 16660 invoked by uid 500); 3 Oct 2008 07:22:20 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 16624 invoked by uid 500); 3 Oct 2008 07:22:20 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 16613 invoked by uid 99); 3 Oct 2008 07:22:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Oct 2008 00:22:20 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of pajbam@gmail.com designates 209.85.200.173 as permitted sender) Received: from [209.85.200.173] (HELO wf-out-1314.google.com) (209.85.200.173) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Oct 2008 07:21:18 +0000 Received: by wf-out-1314.google.com with SMTP id 27so1537999wfd.31 for ; Fri, 03 Oct 2008 00:21:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:in-reply-to:mime-version:content-type:references :x-google-sender-auth; bh=+GxELTmzYPNhLbO/+uliy/mKDKXuQirRO+O7E3CXvVo=; b=CZnShc4W5vnbszTIjy+ox5atic7RXGzyZbUhpvBJmYylZzTl+PnQe/pTflDdMIKcgS a1WXPPrKC+hl64MyMKh52UeOUTQZrgC7ENdwnaQdGL05rRrbH15ua4YNEVxGv2PUMQhS bn2IVt3A1VJ/4VWAKlRgGSBVPxeMBnNt5NxZk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version :content-type:references:x-google-sender-auth; b=j1cgNcvvfl2tzNWU779YNPZHPEPGzoZ6QsFRwIac2NBDBNdpr0eiGadDdG+Nt5l3hL lVnUfrWZKayVo+0HbMXlWfb44Xs1esUr1S2DDUlbVHrbRRwI9FObpkiNnd5tSETQ1Ckl UPEo97/UU/b+h1ul//EB1CrgbhOL6ZT9DZ12Y= Received: by 10.142.192.11 with SMTP id p11mr220951wff.276.1223018503881; Fri, 03 Oct 2008 00:21:43 -0700 (PDT) Received: by 10.143.6.6 with HTTP; Fri, 3 Oct 2008 00:21:43 -0700 (PDT) Message-ID: <98d8c0860810030021id570c1te15683883a66fbc4@mail.gmail.com> Date: Fri, 3 Oct 2008 09:21:43 +0200 From: "Pierre-Arnaud Marcelot" Sender: pajbam@gmail.com To: "Apache Directory Developers List" Subject: Re: Corporate Layout for Studio documentation? In-Reply-To: <48E523F8.7090300@otego.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_24217_28956004.1223018503872" References: <48E523F8.7090300@otego.com> X-Google-Sender-Auth: 80344ae35c9ccbc1 X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_24217_28956004.1223018503872 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Thu, Oct 2, 2008 at 9:41 PM, Felix Knecht wrote: > Hi all Hi Felix, > I fiddled about using customized skins for maven site generation for the > studio documentation to see how it could look > alike using the same layout as the project page. I saw your commits these last days on your sandbox, and was wondering what this skin project was about. I was thinking to a skin for the Studio RCP app or a skin for the generated Maven website. It was the second option. > Here's the result [1]. > I know it's not everything working perfect and some large tables on the > right of the navigation can screw up the layout. > This looks great, even if it's not perfect yet. It looks way better than the standard Maven template. Everything seems more integrated to the project with this one. > The question is just: > Do you think it's worth to have such a Corporate Layout throughout all the > documentation we produce (project site and > maven docs) and investigate some more time in it to make it perfect or is > it just a waist of time? > > WDOT? I think this is a more integrated solution. Having the same look between the usual website and these generated docs is great. I really like the idea. I'm curious to know how you integrate it in the build. Any hints on that ? Thanks, Pierre-Arnaud ------=_Part_24217_28956004.1223018503872 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
On Thu, Oct 2, 2008 at 9:41 PM, Felix Knecht <felix@otego.com> wrote:
Hi all

Hi Felix,
 
I fiddled about using customized skins for maven site generation for the studio documentation to see how it could look
alike using the same layout as the project page.

I saw your commits these last days on your sandbox, and was wondering what this skin project was about.
I was thinking to a skin for the Studio RCP app or a skin for the generated Maven website.
It was the second option.
 
Here's the result [1].
I know it's not everything working perfect and some large tables on the right of the navigation can screw up the layout.

This looks great, even if it's not perfect yet.
It looks way better than the standard Maven template.
Everything seems more integrated to the project with this one.
 
The question is just:
Do you think it's worth to have such a Corporate Layout throughout all the documentation we produce (project site and
maven docs) and investigate some more time in it to make it perfect or is it just a waist of time?

WDOT?

I think this is a more integrated solution.
Having the same look between the usual website and these generated docs is great.
I really like the idea.

I'm curious to know how you integrate it in the build. Any hints on that ?

Thanks,
Pierre-Arnaud
------=_Part_24217_28956004.1223018503872--