I think the talk of scrolling and hover menus is a giant red-herring.
The form factor of the pages needs to be malleable and determined at least
in part by the device requesting the information.
We should not be trying to build a website from the toolbar menu down.
We shouldn't be writing a new homepage, we should be fixing a broken site.
Please, please, please, look at the list of content areas in the site and
prioritize them first. Then set about fixing the most important areas
first. It is fairly trivial wrap well executed content areas into an
attractive homepage or global nav and it is helpful to know how far the
areas of value have come in terms of improvement before we start
illustrating the front door for the site.
To make this clearer...
...I pointed out that event handling on the current site is badly broken,
to which Daniel replied, 'how so'?
Here's how so....
Office hours is the communities most recurring event. You can find them
on the calendar here <http://jenkins-ci.org/content/event-calendar>. But
you cannot get any information about them, unless you go here
<https://wiki.jenkins-ci.org/display/JENKINS/Office+Hours>. From a site
visitor's perspective, unless you were already familiar with our office
hours, you would have no idea what that was, assuming you were even lucky
enough to find the link hidden in the pull down menu. If you are looking
for it, you can find events, but when you click on the goofy Google month
page, you get no information about what the events you see on the calendar
actually are. Even if you click into an office hour link you get absolutely
no information about what an 'office hour' even is, let alone what is going
to be discussed.
....should I go to an office hour, or any other event on the events page?
I have no idea.
This is true of every event in the site.
If there is going to be a big event, there is probably a blog post about
it. But that blog post looks like every other blog post, so if I am looking
for an event in particular (because I want to go and meet people in the
community, or just know what is going on), do I know I should be reading
through the blog posts to weed out the events?
Let's say we wanted out site to have a community focus...
....so we didn't just want a single webmaster scheduling events, but we
wanted community members to come and register their own events. How would
they do that? Are they going to know that to really register an event, they
will need to make other pages and blog posts promoting that event and
maintain that information separately?
This is a super fixable technical problem. Been fixed 1000 times over.
But it isn't fixed by a new nav menu or by a new homepage. And we are not
taking advantages of the well known fixes that exist.
...again, this isn't to say events *is *the most important content area in
the site and needs immediate attention, but I would say most areas of the
site are poorly handled, much like our events. Since it is unlikely we can
fix it all for the amount of investment we have to give it, I think we
should pick an area we are doing poorly and start doing it well.
...rinse... repeat.
I would start with the plugins and rather than events or blogs or doc
(their shortcomings are less glaring and their upside is smaller).
On Fri, Oct 9, 2015 at 6:52 AM, James Nord <[email protected]> wrote:
>
>
> On Friday, October 9, 2015 at 12:50:00 PM UTC+2, Daniel Beck wrote:
>>
>>
>> On 09.10.2015, at 12:43, Robert Sandell <[email protected]> wrote:
>>
>> > That could work, but I'm personally not fond of drop down menus as it
>> tends to be a suboptimal experience on touch devices.
>>
>> Check out how centos.org looks on your phone (or your browser at 770 or
>> fewer pixels wide). Would that work?
>>
>>
> scrolling is so last decade. swiping is the new scrolling and to be
> critical on a mobile that web site is way to "blah blah blah"... "all that
> centos7 junk junk before I get to the news section (a lot of scrolling!)
> :-)
> What is CentOS anyway - as that site doesn't tell me :-P
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/EMbE3a4u8nA/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/a192a678-7fdc-4f92-8955-f54ba8adfe40%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/a192a678-7fdc-4f92-8955-f54ba8adfe40%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CAOcHHXzfry7kQtNK38bz97U9o%3DBBQVMtoCkRTBQynS1uojON2A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
