-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ref to UniBicocca #16
Comments
Hi, I tried to put the text "in collaboration with...DISCO and AlgoLab" in the header, under "Spreading the Ruby and Rails way in Italy" but the logo takes too much space. So, as first try, I put it in the right column, under the "mailing list panel" and above the "Golden sponsor": I do not know if it's the right place. The sponsors are pushed down in the page, in this way they have less visibility. This can be a problem? Other possible positions are: in the footer (adding a fourth column in first position) or in a "Credits" page, as I wrote in the mailing list. I can try these two solutions only tomorrow in the evening. Otherwise, if it's right the proposed solution I can do a pull request (I've already pushed the branch in my repository). bye, |
I've just seen the screen shot I posted in the previous comment. Maybe we can move the "university panel" at the bottom of the column, under the "Media Sponsor" group. In this way the sponsor gain visibility. |
Why not put the lodo etc... near (right) Milan 15 june 2012 ? it should fit without problems and have the right visibility. |
Yeah, I'll make the change tomorrow, this evening I have no time... |
also a reference to algo lab would be great On Fri, Feb 17, 2012 at 12:09 PM, Andrea Forni <
Ra |
Moved to rubydayit/conference_site#3. This issue can be closed. |
Add reference in the main page/header to University of Milano Bicocca, Dipartimento di Informatica Sistemistica e Comunicazione with title :"in collaboration with...DISCO and AlgoLab" http://www.algolab.eu/ and logo of Uni http://www.disco.unimib.it/res/customer/css/default.gif
The text was updated successfully, but these errors were encountered: