From: Takashi Iwai <tiwai@suse.de>
To: Juhana Sadeharju <kouhia@nic.funet.fi>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Updating www.alsa-project.org?
Date: Tue, 12 Feb 2002 11:58:43 +0100 [thread overview]
Message-ID: <s5hofiv55lo.wl@alsa2.suse.de> (raw)
In-Reply-To: <20020208144208Z38455-696+7957@nic.funet.fi>
Hi,
At Fri, 8 Feb 2002 16:42:03 +0200,
Juhana Sadeharju wrote:
>
> Hello. I found out that the current www.alsa-project.org pages
> are not as good as they should be. They are next to nothing
> for non-developers (such as vendors) who yet don't know what
> Alsa is. Information is in wrong importantness order, and there
> actually is not a clear explanation what is the Alsa. A good page
> don't start with a ChangeLog of sorts!
Agreed that a short introduction comes at the first place.
And a direct link to the card matrix from the top page would be nice.
Then everybody can see whether his card is supported.
(It's one of the greatest importance for normal users, I guess.)
But I like to see a couple of the latest news (at least version
update, etc.) on the front page at the same time, so that I can know
what happened in these days at the first look.
> I don't want write all the changes we need to do for the
> webpages. I even cannot do that because I don't have php3
> system. So, would somebody copy existing pages to the temporary
> directory "www.alsa-project.org/new/" where we all together will
> incrementally rewrite the web pages? Thanks.
>
> My suggestions are following:
>
> The main page would contain the contents table (on left) and should
> describe (on right) clearly what is the Alsa project and what are
> the contact addresses. Don't expect people to join the mailing lists
> for contacting purposes. No other information.
The contact address to the web master would be fine.
> I would rearrange the content table as shown here; the most important
> information would come first.
> Press
> Vendor Call
> Search
> News
> Soundcards
> Download
> Documentation
> Mailing-Lists
> Bug Reporting (perhaps should be elsewhere)
> Applications
> Links
Hmm, on what stand point was this list created?
from the users side, Press and Vendor Calls are not so interesting.
Their interest would be to get the latest info, the current status of
their cards, download and instructions.
And I now realized that from this viewpoint, we lack the on-line doc
for installation, too..
> I deleted the "new API" because it goes to Documentation
> page. I'm also considering Development page which would contain
> the devel materials. It looks like the devel material is now
> distributed around the webpages.
That's good. Links to API, CVS info, and on-line docs can be sorted
in the "development" page.
> If Development page would be added it would contain CVS source
> access, documentation for non-user API, devel mailing list info,
> bug reporting, ChangeLog of sorts, and link to SourceForge
> (which is now badly hidden under the main title (should be removed
> from there)).
I like bug reporting being on the top.
Otherwise people will send all bug reports to the address of web
admin - that's quite bad for us.
> The vertical align of the contents table should be changed:
> valign="middle" --> valign="top"
> Then readers have greater changes to access the other pages
> without the use of the scrollbar everytime.
>
> I have not yet written the texts for the main page (or the other
> pages) but if this rewriting gets started, I will continue.
>
> Suggestions? ...and I don't want to hear the webpage is good
> enough now. It is worst of the kind --- think about vendors
> who are looking if Alsa is good enough for them.
looks like you really want to rebuild the page mainly for hardware
vendors? ;)
Anyway, I think it would be really good to have other web
administrators. Jaroslav is obviously overloaded to update/fix the
web page frequently.
ciao,
Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel
next prev parent reply other threads:[~2002-02-12 10:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 14:42 Updating www.alsa-project.org? Juhana Sadeharju
2002-02-08 16:16 ` Kevin Conder
2002-02-11 20:45 ` Juhana Sadeharju
2002-02-12 11:17 ` Steve Harris
2002-02-12 10:58 ` Takashi Iwai [this message]
2002-02-12 14:22 ` Juhana Sadeharju
2002-02-12 15:58 ` Takashi Iwai
2002-02-12 16:53 ` Kai Vehmanen
[not found] <E16aXbe-0001xY-00@usw-sf-list1.sourceforge.net>
2002-02-12 9:34 ` Juhana Sadeharju
2002-02-12 16:05 ` Kevin Conder
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=s5hofiv55lo.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=kouhia@nic.funet.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.