public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Eric W. Brown <eric@saugus.net>
To: xconq7@sources.redhat.com
Subject: Re: New Proposed Xconq Web Site Online
Date: Wed, 29 Sep 2004 00:41:00 -0000	[thread overview]
Message-ID: <D85CF81E-11AD-11D9-B87C-000393439120@saugus.net> (raw)

> Done. Do you think the search box looks okay or should it go elsewhere?

I don't personally have any solid ideas about where the search box 
should logically go.  I guess it makes some sort of sense that the 
documentation, forums, bug reports, old articles section, and searching 
should all be somewhat near each other as they are somewhat related 
(assuming the search facility covers all of those other things).  The 
download section should be very prominent, perhaps in the upper right 
corner.  Some of the links in the modules section are a little 
non-intuitive (for starters, when I see "Modules" WRT Xconq I'm 
expecting game modules).  How does the Search option there differ from 
the search box on the front?  How does the stories archive differ from 
the old articles section on the front?  Why is the games library under 
documentation and not modules?  Why does the Home link appear when 
you're already home?

Are there any usability or UI gurus who read this list?  It's not my 
primary field so take my comments on it with a grain of salt...

> [snip] - I'm as multi-cultural as the next guy, but I'm afraid the
> Espertinos are out of luck :)

Pity; in some seriousness the more I look into it the more it does seem 
that there is some sort of an overlap between people interested in 
strategy games and people interested in international communications 
via neutral languages.  It certainly seems possible to do, too; the 
PHP-Nuke site at http://www.uk-2003.net/ is one example that does it 
(pulled up quickly courtesy of Google).  I'm sure that for this 
particular site many of the languages that are already supported will 
have smaller audiences.

> This may be because you are seeing the story's header. Does clicking 
> the
> "Read More" link help? Also noted is Eli's input about the Xconq logo.

I didn't really mean the length of the stories themselves, just how the 
portions that were displayed on the front page appeared.

> Assuming that it's not the logo size (and it probably is as Eli
> suggested) then this should be fixed (some tweaking may be required).

Is it possible to preserve the larger logo and still make it work?  
Perhaps a layout like:

+-------------+              +--+----------+
|             |              |  |          |
+--+-------+--+      or      +--+-------+--+
|  |       |  |              |  |       |  |
|  |       |  |              |  |       |  |
+--+-------+--+              +--+-------+--+

would work.  Please excuse my cheesy ASCII art (hopefully it'll hit the 
mailing list intact).

> Absolutely. It's really easy to do. The Xconq site currently does. 
> Point
> ...
> are Xconq related RSS feeds, by all means, do tell!

Excellent!  AFAIK, this will be the first.

> You could have written and said, "Coop, that is the ugliest color 
> scheme
> I have ever seen," and I would have about squealed that you gave such
> honest feedback and changed them immediately.

While I certainly won't say that, I might argue toward using fewer 
colors (perhaps just one) for the sidebar boxes' borders.  Either that 
or color them based upon some logical scheme (perhaps with the download 
and/or documentation boxes more obvious than the others).  This is 
really another area where a UI expert's opinions would be good.

> You can try this at home! Simply send a "one liner" that says, "Coop,
> that is the ugliest color scheme I have ever seen" and see what 
> happens!

There's unfortunately been a lot of competition for the ugliest color 
scheme I've ever seen...  I'll spare you the stories, though.

> Thanks!

You're welcome.  Thanks for your work on the site.

             reply	other threads:[~2004-09-29  0:23 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-29  0:41 Eric W. Brown [this message]
2004-09-29 18:08 ` Jim Kingdon
  -- strict thread matches above, loose matches on Subject: below --
2004-10-06  2:02 Feneric Brown
2004-10-01 18:35 Feneric Brown
2004-10-02  2:01 ` Eric McDonald
2004-10-01 18:23 Feneric Brown
2004-10-01  5:40 Feneric Brown
2004-10-01  6:10 ` Jim Kingdon
2004-10-02  2:14   ` Eric McDonald
2004-10-02  2:51     ` mskala
2004-10-02  3:04       ` Eric McDonald
2004-10-03 17:48     ` Jim Kingdon
2004-10-03 18:36       ` Eric McDonald
2004-10-03 18:49         ` Jim Kingdon
2004-10-03 23:55           ` Eric McDonald
2004-10-01  8:07 ` Lincoln Peters
2004-10-01 18:07 ` Eric McDonald
2004-09-29 19:26 Feneric Brown
2004-09-30  0:36 ` Eric McDonald
2004-09-30 23:49 ` Jim Kingdon
2004-09-29 19:17 Eric W. Brown
2004-09-29  0:23 Feneric Brown
2004-09-28 21:34 Feneric Brown
2004-09-28 22:14 ` Elijah Meeks
2004-09-28 23:47 ` D. Cooper Stevenson
2004-09-29 15:00 ` Jim Kingdon
2004-09-29 18:16   ` Eric McDonald
2004-09-30 16:59     ` Jim Kingdon
2004-09-29 18:24   ` Eric McDonald
2004-09-30 17:07     ` Jim Kingdon
2004-09-27 18:44 D. Cooper Stevenson
2004-09-27 18:54 ` Elijah Meeks
2004-09-28  2:40   ` D. Cooper Stevenson
2004-09-28  3:25 ` Eric McDonald

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=D85CF81E-11AD-11D9-B87C-000393439120@saugus.net \
    --to=eric@saugus.net \
    --cc=xconq7@sources.redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).