[theme-reviewers] Review Criteria: Menu Bar Display Aesthetics

[Edward Caissie]

@Matt - I don't see an issue with the idea of using 'overflow:hidden' per
se, although it might be a bit confusing for the end-user if they expect to
see more than what appears on the screen. Sometimes the UX is more important
than the UI.


Cais.

On Thu, Aug 19, 2010 at 2:51 PM, Matt Danner <matt at ithemes.com> wrote:

> Since this has come up, thought I would go ahead and ask... Is it
> acceptable to have overflow:hidden on the menu? This allows the theme
> to maintain its styling if designed for a small number of menu items,
> but doesn't break other elements if the number of pages is too large.
>
> Just a thought. Wanted to see what your thoughts are.
>
> On Thu, Aug 19, 2010 at 12:46 PM, Edward Caissie
> <edward.caissie at gmail.com> wrote:
> > I believe the aesthetic aaspect of the menu should not necessarily be an
> > issue for the Theme Reviewers unless it is "breaking" the theme's
> > navigation.
> >
> > IF the menu wraps, a common effect, with large numbers of pages then as
> long
> > as each of the items are usable within the theme structure it becomes an
> > aesthetics only issue and not one of review. Now, if the wrapping menu
> > causes other items in the theme to not be usable such as other menu items
> > then it becomes a navigation issue and a reviewers concern.
> >
> > This essentially can cause the theme to be unusable although this may be
> > possible to allow through provided the theme author has acknowledged this
> is
> > a known issue via a readme.txt file included with and preferably
> referenced
> > via the theme's description.
> >
> >
> > Cais.
> >
> > On Thu, Aug 19, 2010 at 11:57 AM, Chip Bennett <chip at chipbennett.net>
> wrote:
> >>
> >> Good morning, Theme Reviewers!
> >> Another discussion question: when we are reviewing Themes for
> >> aesthetic/display quality, one factor that seems to come up quite a bit
> is
> >> the Theme's design assumption regarding its use on a simple blog versus
> a
> >> page-driven web site. In the former case, providing room sufficient for
> only
> >> a small number of pages (e.g. "Home", "About", "Contact") may very
> easily
> >> break if a given site is more page-driven.
> >> I've been pointing this out in my current Theme reviews (e.g. the "Menu
> >> Bar" breaks into multiple rows with the given number of pages in the
> Theme
> >> Unit Test data), but, should we be?
> >> In other words, is it acceptable for a Theme to be designed to be used
> on
> >> a site with only a few static Pages? Or should we be requiring Theme
> >> developers to support page-based sites inherently in their design? (To
> wit:
> >> the Home/About/Contact construct seems to be an inherent assumption in a
> LOT
> >> of Theme screenshots and demo sites.)
> >> I don't think I have a preference one way or the other; more, I'm
> curious
> >> what everyone else thinks.
> >> Chip
> >> _______________________________________________
> >> theme-reviewers mailing list
> >> theme-reviewers at lists.wordpress.org
> >> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >>
> >
> >
> > _______________________________________________
> > theme-reviewers mailing list
> > theme-reviewers at lists.wordpress.org
> > http://lists.wordpress.org/mailman/listinfo/theme-reviewers
> >
> >
>
>
>
> --
> Matt Danner
> Front End Developer
> iThemes.com
>
> Follow me on Twitter - @mattdanner
> http://twitter.com/mattdanner
>
> or
>
> Follow our whole team - @ithemes
> http://twitter.com/corymiller303/ithemes-team
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20100819/b0c37516/attachment.htm>