From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: linux-hotplug website
Date: Tue, 16 Jan 2001 18:46:11 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-97967206216377@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-97944536007741@msgid-missing>
OK, it's up ... and in CVS.
Folk with comments about the site, feel free to chime in!
Organization, content, and so on.
- Dave
----- Original Message -----
From: Greg KH <greg@kroah.com>
To: David Brownell <david-b@pacbell.net>
Cc: <linux-hotplug-devel@lists.sourceforge.net>
Sent: Monday, January 15, 2001 10:12 PM
Subject: Re: linux-hotplug website
> On Sat, Jan 13, 2001 at 03:29:19PM -0800, David Brownell wrote:
> > Great! How to deal with pages after this first one? I'd
> > suggest some simple framework like I did for jPhoto:
> >
> > - Change "look" of (most of) site in "index.php"
> > (penguins, navbar, colors, etc)
> >
> > - Add pages (maybe "input.xml") to navbar by "toc.xml",
> >
> > - TOC turns into navbar; content becomes page content;
> > headers and footers are easy (layout in index.php)
> >
> > No frames. I'm sure there are better ways to organize a
> > small-to-midsize website, but that might be a reasonable
> > way to start things. Alternative suggestions?
>
> This sounds good. I like the jphoto layout. Even works well for lynx.
>
> If you want to knock this up. Or put it into cvs like I think was done
> for the linux-usb site, feel free.
>
> thanks,
>
> greg k-h
>
> --
> greg@(kroah|wirex).com
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2001-01-16 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-13 23:29 linux-hotplug website David Brownell
2001-01-16 6:12 ` Greg KH
2001-01-16 18:46 ` David Brownell [this message]
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=marc-linux-hotplug-97967206216377@msgid-missing \
--to=david-b@pacbell.net \
--cc=linux-hotplug@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).