logging-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Scott Deboy <scott.de...@gmail.com>
Subject Re: Updating the logging services web site
Date Mon, 27 Feb 2012 18:25:49 GMT
I also hit the annoying issue during the conversion to use site-plugin
where we could no longer use images with links - the 'start Chainsaw' link
went from a very visible graphic to a regular underlined link...not great.
Maybe it's time to use something different..we don't have that many pages..

On Mon, Feb 27, 2012 at 7:14 AM, Ivan Habunek <ivan.habunek@gmail.com>wrote:

> I'm using a custom skin based on Twitter's Bootstrap on the log4php
> site. It's similar to Fluido, but using a different layout.
> Unfortunately, a custom skin does not allow you to modify the way
> XDOC/APT are translated to HTML so it's not a solution to this
> problem.
>
> I will attempt to make the site-plugin do my bidding once again this
> week. :-) It would be nicer to have the site in XDOC than HTML.
>
> Regards,
> Ivan
>
> On 27 February 2012 16:01, Ralph Goers <rgoers@apache.org> wrote:
> > Have you tried using a different skin? I'm using Fluido on Log4j2. I
> have no idea if that will help, but it may show you how to create your own
> that does what you want.
> >
> > Ralph
> >
> > On Feb 27, 2012, at 1:16 AM, Ivan Habunek <ivan.habunek@gmail.com>
> wrote:
> >
> >> I will rant a bit now. Apologies in advance.
> >>
> >> The Maven site-plugin (or whatever sub-component is responsible for
> >> the xdoc conversion) is making it almost impossible to create any site
> >> layout except the one they envisioned. Several examples when
> >> converting xdoc to html:
> >> * Any header element (h1,h2,...) will be encased in a <div
> >> class="section">. This breaks the layout for my web example, amongst
> >> other things.
> >> * Replaces <strong> with <b>,  <em> with <i> and <code>
with <tt>. Why?
> >> * Always puts class="bodyTable" to all <table>s. Annoying, not too
> harmful.
> >> * Replaces <pre class="prettyprint">...</pre> with <div
> >> class="prettyprint><pre>...</pre></div>. This breaks the
> >> prettyprint-ing of code.
> >> * Xdoc doesn't support HTML entities such as &nbsp; (again, annoying
> >> but not unsolvable)
> >>
> >> Apart from that, the apt format is almost unusable with any styling
> >> except the default. The main problem is that you can't assign classes
> >> to html elements. In other words, tables can't be formatted (requires
> >> the "table" class on <table>), code can't be pretty-printed (requires
> >> "prettyprint" class on <pre>), etc.
> >>
> >> So I use liberal amounts of Javascript to fix these things, which is
> >> not optimal. The log4php pages pretty bad when using noscript.
> >>
> >> </rant>
> >>
> >> I considered just using plain HTML for the logging site, and avoid the
> >> site-plugin. But this would be a pain if the number of pages ever
> >> grows to more than 2-3.
> >>
> >> Do you guys know of any alternatives for generating the web?
> >>
> >> Regards,
> >> Ivan
> >>
> >>
> >> On 27 February 2012 03:56, Ron Grabowski <rongrabowski@yahoo.com>
> wrote:
> >>> I like it!
> >>>
> >>> ________________________________
> >>> From: Ivan Habunek <ivan.habunek@gmail.com>
> >>> To: Logging General <general@logging.apache.org>
> >>> Sent: Sunday, February 26, 2012 4:05 PM
> >>> Subject: Updating the logging services web site
> >>>
> >>> Hi all,
> >>>
> >>> I would like to take some time to make the front page of the logging
> >>> service project a bit more user friendly, informative and nicer
> >>> looking.
> >>>
> >>> The main function of this page is to direct the user to each of the
> >>> logging projects. I have made a quick mockup of the general design I
> >>> had in mind (again using Bootstrap since I'm not a graphic designer).
> >>> There are only 3 pages so far, the main page, charter and team list.
> >>> You can see them here (charter & team pages are in the "about"
> >>> dropdown menu in the top bar):
> >>> http://people.apache.org/~ihabunek/logging/
> >>>
> >>> I would like to gather everybody's opinion of what else should be
> >>> included on the front page.
> >>>
> >>> In the new layout, I have dropped the logging services logo in favour
> >>> of the apache feather logo. They are quite similar, and, to my eyes,
> >>> the plain feather logo just looks nicer and cleaner.
> >>>
> >>> IMO, the log4j companions may be better suited on the log4j site so I
> >>> have not included them on the front page for now.
> >>>
> >>> So far, I gather that we need at least:
> >>> - a short description of the logging services project to put in the
> >>> big box on the front page
> >>> - perhaps a longer description of the project (an 'about' page)
> >>> - a short description of each sub project to put on the front page
> >>>
> >>> Also we should determine if any other content should be moved from the
> >>> current site. I have located several orphan pages which exist, but are
> >>> not linked to anywhere:
> >>> http://logging.apache.org/charter.html (migrated)
> >>> http://logging.apache.org/catalog.html
> >>> http://logging.apache.org/guidelines.html
> >>>
> >>> Please let me know what you think.
> >>>
> >>> Best regards,
> >>> Ivan
> >>>
> >>>
>

Mime
View raw message