From: Michael Veeck <michael.veeck@gmx.net>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [RFC] new design for kerneljanitors.org?
Date: Sat, 16 Jul 2005 14:33:51 +0000 [thread overview]
Message-ID: <42D91ACF.5070304@gmx.net> (raw)
In-Reply-To: <42C1CDE1.9010308@gmx.net>
Hi everybody, I'm back with a new proposal for the
kerneljanitor-website. Highlights this time:
- looks exactly (99%) as the existing one, keeping the compact design
- 1% difference due to minor text-cleanups
- 100% XHTML 1.1, no more table-mess
- 100% CSS, making it more flexible than the previous one
Again it can be found at http://veeck.de/janitor/
maximilian attems schrieb:
> hello michael,
>
> On Wed, 29 Jun 2005, Michael Veeck wrote:
>
>
>>One might argue that a corporate design is long overdue for the various
>>linux-kernel projects ;-)
>
> well i'm not conviced by this premis.
> i like a lot the baby penguin for the kernelnewbies project.
> every project has his own choices.
Then you might like the penguin janitor ;-)
>>So while the heat in germany hinders me from doing sophisticated kernel
>>stuff, I gave the old kerneljanitor webpage a design based on the
>>kernel.org site (just took me 30 minutes).
>>
>>A first version can be found at http://veeck.dyndns.org/
>
>
> as domen pointed already out the current version is more compact.
> also aboves looks much more rudimentary and we don't have a nice kernel
> banner to display on the top that is worth for 99% of the kernel.org
> visits. :)
> btw. i'm quite happy to learn that kernel.org design is moving.
>
>
> current design was done by Randy Dunlap.
> it should validate as html 4.01. i agree that tables shouldn't be used
> as design elements (but div layers) and that it should move to xhtml.
> it's still on my todo list but without much priority.
> so if you would achieve same design but newer code working for browser
> mozilla Seamonkey >= 1.0 and ie >= 5.0 that would be great.
Well it is tested with Firefox 1.0.4, Opera8 and IE6. Other browsers are
not at my disposal.
Thanks for your input
Michael Veeck
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2005-07-16 14:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-28 22:23 [KJ] [RFC] new design for kerneljanitors.org? Michael Veeck
2005-06-29 6:55 ` Christophe Lucas
2005-06-29 10:40 ` Nico Golde
2005-06-29 12:40 ` Domen Puncer
2005-07-02 10:16 ` maximilian attems
2005-07-16 14:33 ` Michael Veeck [this message]
2005-07-16 15:42 ` randy_dunlap
2005-07-16 15:50 ` Michael Veeck
2005-07-16 16:29 ` randy_dunlap
2005-07-16 16:52 ` Michael Veeck
2005-07-16 17:12 ` randy_dunlap
2005-07-16 19:53 ` Lukas Sandström
2005-07-18 8:42 ` maximilian attems
2005-07-18 8:45 ` Carlo Perassi
2005-07-18 8:57 ` maximilian attems
2005-08-11 21:21 ` Michael Veeck
2005-08-12 10:07 ` Christophe Lucas
2005-08-12 10:51 ` Maximilian Attems
2005-08-12 13:41 ` Christophe Lucas
2005-08-12 18:04 ` Michael Veeck
2005-11-01 13:07 ` [KJ] [RFC] new design for kerneljanitors.org REV 2 Jerome Pinot
2005-11-01 13:43 ` Michael Veeck
2005-11-01 14:22 ` Jerome Pinot
2005-11-01 19:43 ` Michael Veeck
-- strict thread matches above, loose matches on Subject: below --
2005-06-29 6:41 [KJ] [RFC] new design for kerneljanitors.org? Michael Veeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42D91ACF.5070304@gmx.net \
--to=michael.veeck@gmx.net \
--cc=kernel-janitors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).