Hello everyone,
I would like to invite you to take a look the preview [1] of MediaWiki Homepage. Your opinion, contribution and help are very welcome.
Thank you.
Best regards,
[1] https://www.mediawiki.org/wiki/MediaWiki/Homepage_redesign/Preview
Brena Monteiro +55 27 98109 0123 @monteirobrena http://twitter.com/monteirobrena Reflexões Brenianas http://monteirobrena.wordpress.com
Most of the visitors to mediawiki.org just want to download the software. I don't see any way to do that in the proposed redesign.
Ryan Kaldari
On Mon, Feb 24, 2014 at 12:55 PM, Brena Monteiro monteirobrena@gmail.comwrote:
Hello everyone,
I would like to invite you to take a look the preview [1] of MediaWiki Homepage. Your opinion, contribution and help are very welcome.
Thank you.
Best regards,
[1] https://www.mediawiki.org/wiki/MediaWiki/Homepage_redesign/Preview
Brena Monteiro +55 27 98109 0123 @monteirobrena http://twitter.com/monteirobrena Reflexões Brenianas http://monteirobrena.wordpress.com
Design mailing list Design@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/design
On 02/24/2014 01:04 PM, Ryan Kaldari wrote:
Most of the visitors to mediawiki.org http://mediawiki.org just want to download the software. I don't see any way to do that in the proposed redesign.
This is the design we are after:
https://www.mediawiki.org/wiki/File:MediaWiki_Homepage_Mockup_Graphic_With_H...
The big picture needs to be cut and be converted in a panoramic image.
Then the "Get MediaWiki" label needs to be converted in a propoer button styled by mediawiki.ui... if you can help us to make the CSS work:
https://www.mediawiki.org/wiki/Talk:MediaWiki/Homepage_redesign/Preview#medi...
Ryan Kaldari
On Mon, Feb 24, 2014 at 12:55 PM, Brena Monteiro <monteirobrena@gmail.com mailto:monteirobrena@gmail.com> wrote:
Hello everyone, I would like to invite you to take a look the preview [1] of MediaWiki Homepage. Your opinion, contribution and help are very welcome. Thank you. Best regards, [1] https://www.mediawiki.org/wiki/MediaWiki/Homepage_redesign/Preview
'Get MediaWiki'? We've already got that in the sidebar. We have a mainpage to go beyond what's in the sidebar. What are the current releases? What's the status? Is there any important security information we need to know about? This stuff is important, and not everyone subscribes to the release lists (and even if they do, we can't expect people to rely on them). The mainpage would be the obvious place to look for updates.
Also some other random thoughts -
What's the Publish/Discuss/Translate/etc blocks for? They look like navigation but don't seem to go anywhere or correspond to anything. They're also not consistent - for instance 'Translate' is an active verb probably referring to TWN (I guess? TWN isn't exactly specific to mw; they handle translations for a lot of other projects too), and 'On the go' is a random statement that I don't know what it's referring to at all. I mean, 'Ready for mobile devices and tablets' certainly isn't true of MediaWiki. It can be made to work for them, but it can be made to do just about anything.
I also still haven't seen an answer to what that big picture is actually for. So what's it for?
Images being used to illustrate links should also link to the target as opposed to the image (such as the documentation, support, etc), because people are more likely to click on the image than the small text caption. You will need to find PD or other non-SA licensed images to do this, however, because you will lose the attribution for the images.
Bugzilla should have a prominent link. Sysadmins and other users who found bugs are not necessarily looking to 'get involved'. They found bugs and want to report them or find fixes. They're looking for a bug thing. Where is that?
On 24/02/14 21:06, Quim Gil wrote:
On 02/24/2014 01:04 PM, Ryan Kaldari wrote:
Most of the visitors to mediawiki.org http://mediawiki.org just want to download the software. I don't see any way to do that in the proposed redesign.
This is the design we are after:
https://www.mediawiki.org/wiki/File:MediaWiki_Homepage_Mockup_Graphic_With_H...
The big picture needs to be cut and be converted in a panoramic image.
Then the "Get MediaWiki" label needs to be converted in a propoer button styled by mediawiki.ui... if you can help us to make the CSS work:
https://www.mediawiki.org/wiki/Talk:MediaWiki/Homepage_redesign/Preview#medi...
Ryan Kaldari
On Mon, Feb 24, 2014 at 12:55 PM, Brena Monteiro <monteirobrena@gmail.com mailto:monteirobrena@gmail.com> wrote:
Hello everyone, I would like to invite you to take a look the preview [1] of MediaWiki Homepage. Your opinion, contribution and help are very welcome. Thank you. Best regards, [1] https://www.mediawiki.org/wiki/MediaWiki/Homepage_redesign/Preview
On Mon, Feb 24, 2014 at 1:54 PM, Isarra Yos zhorishna@gmail.com wrote:
What are the current releases? What's the status? Is there any important security information we need to know about?
+1 -- make some space for the current version numbers (bonus points for the links to the change logs). I've seen lots of sites just integrate the versions directly into the button text if we wanted to do that.
Also; think about if we want to put up a banner saying "Users of X.YY.Z need to upgrade immediately because of big security bug"; where that would go and what it would look like.
Bugzilla should have a prominent link. Sysadmins and other users who found
bugs are not necessarily looking to 'get involved'. They found bugs and want to report them or find fixes. They're looking for a bug thing. Where is that?
I sort of agree, I think this can be on the sidebar though instead of on the main page. (Personally I start to get annoyed if it takes me more than three clicks to get to the bug tracker; but I don't usually expect prominent links.)
Matthew Walker, 24/02/2014 23:38:
Bugzilla should have a prominent link. Sysadmins and other users who found bugs are not necessarily looking to 'get involved'. They found bugs and want to report them or find fixes. They're looking for a bug thing. Where is that?I sort of agree, I think this can be on the sidebar though instead of on the main page. (Personally I start to get annoyed if it takes me more than three clicks to get to the bug tracker; but I don't usually expect prominent links.)
I do too, bug tracker must be reachable in one click from the front page of every software project. It's the first link of the third box in the sidebar, which is perfect if one uses monobook but makes the life of Vector users harder (as always). I don't feel like making the sidebar messy just to fit Vector's idiosyncracies, so unless someone fixes https://bugzilla.wikimedia.org/show_bug.cgi?id=25394 * a link from main page makes sense.
Nemo
(*) Or kills the hideous hideous hideous collapsing altogether, even better. https://bugzilla.wikimedia.org/39035
On 02/24/2014 01:54 PM, Isarra Yos wrote:
'Get MediaWiki'? We've already got that in the sidebar. We have a mainpage to go beyond what's in the sidebar. What are the current releases? What's the status? Is there any important security information we need to know about? This stuff is important, and not everyone subscribes to the release lists (and even if they do, we can't expect people to rely on them). The mainpage would be the obvious place to look for updates.
Based on https://www.mediawiki.org/wiki/MediaWiki/Homepage_redesign/Design_Document , we have been betting for a simple "Get MediaWiki" button linking to /Download, but we are happy to discuss better approaches.
How much extra details do we want to provide in this homepage targeted mainly to new adopters?
Should we also add the version number of the last estable release, linking to e.g. https://www.mediawiki.org/wiki/MediaWiki_1.22 ?
Should we really go further into the other two releases we are manintaining, security notices, and so on? Or should we keep channeling users to https://www.mediawiki.org/wiki/Download , improving that page to answer these questions about previous / security releases faster?
Your feedback and your proposed implementations are welcome.
Also some other random thoughts -
What's the Publish/Discuss/Translate/etc blocks for? They look like navigation but don't seem to go anywhere or correspond to anything.
They attempt to summarize the best features that MediaWiki can offer. Indeed, there are no detailed product descriptions to link to, but this is because we don't have them. I would say this is better than nothing. Currently you either know what MediaWiki plus selected extensions can offer, or you guess it by becoming a Wikipedia power user, or you need to connect many pages in mediawiki.org.
They're also not consistent
One of the reasons for moving our prototyping to a wiki page is to welcome edits improving our the current texts.
- for instance 'Translate' is an active verb
probably referring to TWN (I guess? TWN isn't exactly specific to mw; they handle translations for a lot of other projects too),
No, it refers to the fact that you can translate you wiki content in your wiki (using the Translate extension). You can publish, discuss, and translate content.
and 'On the go' is a random statement that I don't know what it's referring to at all. I mean, 'Ready for mobile devices and tablets' certainly isn't true of MediaWiki. It can be made to work for them, but it can be made to do just about anything.
We are betting on MobileFrontend here. It provides a mobile view, possibility to edit, upload... It does look like one of the MediaWiki strengths to me.
I also still haven't seen an answer to what that big picture is actually for. So what's it for?
With the design in the mockup we are betting on a big wide image with a slogan on top. The current image is the best image we have found so far, coupled with the best slogan we came up with. If you have better images or better slogans they are welcome.
Images being used to illustrate links should also link to the target as opposed to the image (such as the documentation, support, etc), because people are more likely to click on the image than the small text caption. You will need to find PD or other non-SA licensed images to do this, however, because you will lose the attribution for the images.
Yes, we need to solve this problem. It is being discussed at https://www.mediawiki.org/wiki/Talk:MediaWiki/Homepage_redesign/Preview#Clic...
Bugzilla should have a prominent link. Sysadmins and other users who found bugs are not necessarily looking to 'get involved'. They found bugs and want to report them or find fixes. They're looking for a bug thing. Where is that?
"Support" links to https://www.mediawiki.org/wiki/Project:Support_desk , which is where many MediaWiki sysadmins go when they have/find problems. Bugzilla is not visibly featured there, and it probably should be.
Is this enough? Do we need a direct reference to bug reporting in the homepage, apart from the quite hidden "Bug tracker" link in the sidebar?
[1] https://www.mediawiki.org/wiki/MediaWiki/Homepage_redesign/Preview
On 24/02/14 23:14, Quim Gil wrote:
On 02/24/2014 01:54 PM, Isarra Yos wrote:
'Get MediaWiki'? We've already got that in the sidebar. We have a mainpage to go beyond what's in the sidebar. What are the current releases? What's the status? Is there any important security information we need to know about? This stuff is important, and not everyone subscribes to the release lists (and even if they do, we can't expect people to rely on them). The mainpage would be the obvious place to look for updates.
Based on https://www.mediawiki.org/wiki/MediaWiki/Homepage_redesign/Design_Document , we have been betting for a simple "Get MediaWiki" button linking to /Download, but we are happy to discuss better approaches.
How much extra details do we want to provide in this homepage targeted mainly to new adopters?
Why would it be targeted mainly to new adopters? They're only one of the groups who would be using this.
Should we also add the version number of the last estable release, linking to e.g. https://www.mediawiki.org/wiki/MediaWiki_1.22 ?
Should we really go further into the other two releases we are manintaining, security notices, and so on? Or should we keep channeling users to https://www.mediawiki.org/wiki/Download , improving that page to answer these questions about previous / security releases faster?
Your feedback and your proposed implementations are welcome.
All of the current/supported ones should be listed, with either EOL, release dates, or both for each, and anything about new security releases should probably be either bold or emphasised some other way. You could put it all on the button, but that'd be a bit odd. Currently there's a button with the specifics under it; perhaps that's the way to go?
Also some other random thoughts -
What's the Publish/Discuss/Translate/etc blocks for? They look like navigation but don't seem to go anywhere or correspond to anything.
They attempt to summarize the best features that MediaWiki can offer. Indeed, there are no detailed product descriptions to link to, but this is because we don't have them. I would say this is better than nothing. Currently you either know what MediaWiki plus selected extensions can offer, or you guess it by becoming a Wikipedia power user, or you need to connect many pages in mediawiki.org.
Then they should say that. They should say what they are, they should explain the distinctions between core and extensions. They should show how modular and capable it is without trying to fit some template, because that just doesn't work here.
And other features - it's open source, it's created with collaboration between projects (TWN anyone?), etc. These are actually rather important things.
They're also not consistent
One of the reasons for moving our prototyping to a wiki page is to welcome edits improving our the current texts.
- for instance 'Translate' is an active verb
probably referring to TWN (I guess? TWN isn't exactly specific to mw; they handle translations for a lot of other projects too),
No, it refers to the fact that you can translate you wiki content in your wiki (using the Translate extension). You can publish, discuss, and translate content.
That is definitely something that should be made clearer, then.
and 'On the go' is a random statement that I don't know what it's referring to at all. I mean, 'Ready for mobile devices and tablets' certainly isn't true of MediaWiki. It can be made to work for them, but it can be made to do just about anything.
We are betting on MobileFrontend here. It provides a mobile view, possibility to edit, upload... It does look like one of the MediaWiki strengths to me.
MobileFrontend is an arse to setup and a lot of it is either specifically coded to suit Wikipedia, or it makes assumptions, such as the skin, that are often not viable for other projects at all.
It exists, which is certainly something, but like VE it's far from ready for advertising in this form.
I also still haven't seen an answer to what that big picture is actually for. So what's it for?
With the design in the mockup we are betting on a big wide image with a slogan on top. The current image is the best image we have found so far, coupled with the best slogan we came up with. If you have better images or better slogans they are welcome.
But WHY? What purpose does it serve?
Images being used to illustrate links should also link to the target as opposed to the image (such as the documentation, support, etc), because people are more likely to click on the image than the small text caption. You will need to find PD or other non-SA licensed images to do this, however, because you will lose the attribution for the images.
Yes, we need to solve this problem. It is being discussed at https://www.mediawiki.org/wiki/Talk:MediaWiki/Homepage_redesign/Preview#Clic...
Bugzilla should have a prominent link. Sysadmins and other users who found bugs are not necessarily looking to 'get involved'. They found bugs and want to report them or find fixes. They're looking for a bug thing. Where is that?
"Support" links to https://www.mediawiki.org/wiki/Project:Support_desk , which is where many MediaWiki sysadmins go when they have/find problems. Bugzilla is not visibly featured there, and it probably should be.
Is this enough? Do we need a direct reference to bug reporting in the homepage, apart from the quite hidden "Bug tracker" link in the sidebar?
What bawolff said here.
Dear all, I have a little suggestion to the home page redesign, it looks really great but should we also add in a translation bar and the sister projects bar at the bottom? BTW, I am Gabriel Lee, 13 from Hong Kong. Gabriel
2014-02-26 8:12 GMT+08:00 Isarra Yos zhorishna@gmail.com:
On 24/02/14 23:14, Quim Gil wrote:
On 02/24/2014 01:54 PM, Isarra Yos wrote:
'Get MediaWiki'? We've already got that in the sidebar. We have a mainpage to go beyond what's in the sidebar. What are the current releases? What's the status? Is there any important security information we need to know about? This stuff is important, and not everyone subscribes to the release lists (and even if they do, we can't expect people to rely on them). The mainpage would be the obvious place to look for updates.
Based on https://www.mediawiki.org/wiki/MediaWiki/Homepage_ redesign/Design_Document , we have been betting for a simple "Get MediaWiki" button linking to /Download, but we are happy to discuss better approaches.
How much extra details do we want to provide in this homepage targeted mainly to new adopters?
Why would it be targeted mainly to new adopters? They're only one of the groups who would be using this.
Should we also add the version number of the last estable release, linking to e.g. https://www.mediawiki.org/wiki/MediaWiki_1.22 ?
Should we really go further into the other two releases we are manintaining, security notices, and so on? Or should we keep channeling users to https://www.mediawiki.org/wiki/Download , improving that page to answer these questions about previous / security releases faster?
Your feedback and your proposed implementations are welcome.
All of the current/supported ones should be listed, with either EOL, release dates, or both for each, and anything about new security releases should probably be either bold or emphasised some other way. You could put it all on the button, but that'd be a bit odd. Currently there's a button with the specifics under it; perhaps that's the way to go?
Also some other random thoughts -
What's the Publish/Discuss/Translate/etc blocks for? They look like navigation but don't seem to go anywhere or correspond to anything.
They attempt to summarize the best features that MediaWiki can offer. Indeed, there are no detailed product descriptions to link to, but this is because we don't have them. I would say this is better than nothing. Currently you either know what MediaWiki plus selected extensions can offer, or you guess it by becoming a Wikipedia power user, or you need to connect many pages in mediawiki.org.
Then they should say that. They should say what they are, they should explain the distinctions between core and extensions. They should show how modular and capable it is without trying to fit some template, because that just doesn't work here.
And other features - it's open source, it's created with collaboration between projects (TWN anyone?), etc. These are actually rather important things.
They're also not consistent
One of the reasons for moving our prototyping to a wiki page is to welcome edits improving our the current texts.
- for instance 'Translate' is an active verb
probably referring to TWN (I guess? TWN isn't exactly specific to mw; they handle translations for a lot of other projects too),
No, it refers to the fact that you can translate you wiki content in your wiki (using the Translate extension). You can publish, discuss, and translate content.
That is definitely something that should be made clearer, then.
and 'On the
go' is a random statement that I don't know what it's referring to at all. I mean, 'Ready for mobile devices and tablets' certainly isn't true of MediaWiki. It can be made to work for them, but it can be made to do just about anything.
We are betting on MobileFrontend here. It provides a mobile view, possibility to edit, upload... It does look like one of the MediaWiki strengths to me.
MobileFrontend is an arse to setup and a lot of it is either specifically coded to suit Wikipedia, or it makes assumptions, such as the skin, that are often not viable for other projects at all.
It exists, which is certainly something, but like VE it's far from ready for advertising in this form.
I also still haven't seen an answer to what that big picture is actually
for. So what's it for?
With the design in the mockup we are betting on a big wide image with a slogan on top. The current image is the best image we have found so far, coupled with the best slogan we came up with. If you have better images or better slogans they are welcome.
But WHY? What purpose does it serve?
Images being used to illustrate links should also link to the target as
opposed to the image (such as the documentation, support, etc), because people are more likely to click on the image than the small text caption. You will need to find PD or other non-SA licensed images to do this, however, because you will lose the attribution for the images.
Yes, we need to solve this problem. It is being discussed at https://www.mediawiki.org/wiki/Talk:MediaWiki/Homepage_ redesign/Preview#Clickable_images_in_gallery
Bugzilla should have a prominent link. Sysadmins and other users who
found bugs are not necessarily looking to 'get involved'. They found bugs and want to report them or find fixes. They're looking for a bug thing. Where is that?
"Support" links to https://www.mediawiki.org/wiki/Project:Support_desk , which is where many MediaWiki sysadmins go when they have/find problems. Bugzilla is not visibly featured there, and it probably should be.
Is this enough? Do we need a direct reference to bug reporting in the homepage, apart from the quite hidden "Bug tracker" link in the sidebar?
What bawolff said here.
Design mailing list Design@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/design
Gabriel Chi Hong Lee, 26/02/2014 12:26:
Dear all, I have a little suggestion to the home page redesign, it looks really great but should we also add in a translation bar and the sister projects bar at the bottom? BTW, I am Gabriel Lee, 13 from Hong Kong.
Hi! Sure, you're right, we should: just edit the proposal. :)
Nemo
Sister projects bar that I understand.
Translation bar? What does that do?
On Wed, 26 Feb 2014, at 22:26, Gabriel Chi Hong Lee wrote:
Dear all, I have a little suggestion to the home page redesign, it looks really great but should we also add in a translation bar and the sister projects bar at the bottom? BTW, I am Gabriel Lee, 13 from Hong Kong. Gabriel
On 02/26/2014 03:26 AM, Gabriel Chi Hong Lee wrote:
I have a little suggestion to the home page redesign, it looks really great but should we also add in a translation bar and the sister projects bar at the bottom? BTW, I am Gabriel Lee, 13 from Hong Kong.
Thank you Gabriel for the reminder.
I filed https://bugzilla.wikimedia.org/show_bug.cgi?id=61695 hoping to be able to avoid that big box with language links in the homepage. But you are right, it needs to be there while we miss a better solution.
MobileFrontend is an arse to setup and a lot of it is either specifically
coded to suit Wikipedia, or it makes assumptions, such as the skin, that are often not viable for other projects at all.
This comment greatly surprised me. MobileFrontend was previously very difficult to set up but should now be very trivial. When did you last try?
I'm not sure what you mean about assumptions and how this would effect the homepage redesign. If the redesign is designed responsively it will just work. MobileFrontend is its own skin so it's not making assumptions - it knows what skin it is running in...
On 26/02/14 17:04, Jon Robson wrote:
MobileFrontend is an arse to setup and a lot of it is either
specifically coded to suit Wikipedia, or it makes assumptions, such as the skin, that are often not viable for other projects at all.
This comment greatly surprised me. MobileFrontend was previously very difficult to set up but should now be very trivial. When did you last try?
I'm not sure what you mean about assumptions and how this would effect the homepage redesign. If the redesign is designed responsively it will just work. MobileFrontend is its own skin so it's not making assumptions - it knows what skin it is running in...
Set it up sometime in 2013, been running into problems ever since, mostly with caching. As I recall we wound up having to direct mobile users to just use an app that just made sure the mobile version was called.
But it may be an issue with the documentation, then, especially this - https://www.mediawiki.org/wiki/Extension:MobileFrontend/Configuring_browser_...
* It's unclear what you mean by 'front-end caching' - what all does this cover? Is it just squid/varnish-type things, or does it include the file cache as well? Many projects do use at least that. * The example varnish configuration appears to be missing. Can this be fixed?
I don't mean that MF poses problems with the homepage, I mean these are issues for third-party users, and that the way it's listed on the homepage is very misleading because it implies it's part of core and works out of the box. (The skin-specific problems may have been fixed in the master/current, but as a general rule third-party users will not be using the current version. They'll be using something marked as stable for their mw version.)
MF may well be on its way to being good for most everyone running a wiki of similar format to wikipedia, but it ain't there yet, and that's also just MF, not MediaWiki out of the box, hence my comments.
-I
On Mon, Feb 24, 2014 at 1:06 PM, Quim Gil qgil@wikimedia.org wrote:
Then the "Get MediaWiki" label needs to be converted in a propoer button styled by mediawiki.ui... if you can help us to make the CSS work:
I responded on the talk page.
https://www.mediawiki.org/wiki/Talk:MediaWiki/Homepage_redesign/Preview#medi...
On Mon, 2014-02-24 at 13:06 -0800, Quim Gil wrote:
This is the design we are after: https://www.mediawiki.org/wiki/File:MediaWiki_Homepage_Mockup_Graphic_With_H...
The bottom section confused me. On the left there is one video about something. Likely something new or interesting if they only put this one video there, plus there's no link to more videos. Wondering how to judge if it's relevant to me (whatever persona I want to be today). Probably I really first need to read the small description at the video's bottom.
In the middle there is a huge WMF icon. It's prominently placed and huge. Feels a bit unbalanced.
And on the right there's another list of links. "News" if I interpret the last line correctly, though I'm pretty used to headings *on top*.
andre
[Disclaimer: IANAD.]
*Jared Zimmerman * \ Director of User Experience \ Wikimedia Foundation
M : +1 415 609 4043 | : @JaredZimmermanhttps://twitter.com/JaredZimmerman
On Tue, Feb 25, 2014 at 8:49 AM, Andre Klapper aklapper@wikimedia.orgwrote:
On Mon, 2014-02-24 at 13:06 -0800, Quim Gil wrote:
This is the design we are after:
https://www.mediawiki.org/wiki/File:MediaWiki_Homepage_Mockup_Graphic_With_H...
The bottom section confused me. On the left there is one video about something. Likely something new or interesting if they only put this one video there, plus there's no link to more videos. Wondering how to judge if it's relevant to me (whatever persona I want to be today). Probably I really first need to read the small description at the video's bottom.
In the middle there is a huge WMF icon. It's prominently placed and huge. Feels a bit unbalanced.
And on the right there's another list of links. "News" if I interpret the last line correctly, though I'm pretty used to headings *on top*.
andre
[Disclaimer: IANAD.]
Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/
Design mailing list Design@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/design
Hey everyone, can we please move feedback to the talk page, Brena shouldn't have to go to 3 places to figure out next steps. Thanks!
*Jared Zimmerman * \ Director of User Experience \ Wikimedia Foundation
M : +1 415 609 4043 | : @JaredZimmermanhttps://twitter.com/JaredZimmerman
On Tue, Feb 25, 2014 at 8:49 AM, Andre Klapper aklapper@wikimedia.orgwrote:
On Mon, 2014-02-24 at 13:06 -0800, Quim Gil wrote:
This is the design we are after:
https://www.mediawiki.org/wiki/File:MediaWiki_Homepage_Mockup_Graphic_With_H...
The bottom section confused me. On the left there is one video about something. Likely something new or interesting if they only put this one video there, plus there's no link to more videos. Wondering how to judge if it's relevant to me (whatever persona I want to be today). Probably I really first need to read the small description at the video's bottom.
In the middle there is a huge WMF icon. It's prominently placed and huge. Feels a bit unbalanced.
And on the right there's another list of links. "News" if I interpret the last line correctly, though I'm pretty used to headings *on top*.
andre
[Disclaimer: IANAD.]
Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/
Design mailing list Design@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/design