commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benedikt Ritter <brit...@apache.org>
Subject Re: [SITE] Towards a fresh new design
Date Tue, 23 Jul 2013 13:27:44 GMT
Hi Gary,

this is not a problem with fluido directly. It is the underlying bootstrap,
that wastes to much space on mobile phones. I've fixed this for my
committer page at ASF by modifying bootstrap [1]. AFAIK changing bootstrap
during packaging of fluido ist not possible/not wanted.
A possible solution seems to be to deactivate responsive design. I think
this is, why the Log4j2 page [2] is rendered full screen even on my iPhone
(can you confirm this?).

Benedikt

[1]
https://github.com/britter/britter-at-apache/commit/cc55d9f94d6c143c9b1f8b8fc3b7f77ed14031bb
[2] http://logging.apache.org/log4j/2.x/


2013/7/22 Gary Gregory <garydgregory@gmail.com>

> The skin has some bugs when I view (4) on my iPhone. Some menu items
> bleed out of the gray box and into whatever is right of it. Otherwise
> I like it better than what we have now.
>
> Gary
>
> On Jul 22, 2013, at 2:53, Benedikt Ritter <britter@apache.org> wrote:
>
> > Hi,
> >
> > I started a discussion about how make commons more attractive for new
> > comers a while ago [1]. Since then, I've created a twitter account
> > [2], cleaned up our ohloh profiles and requested git mirrors for all
> > proper components from Infra [3].
> >
> > Now I'd like to take the next step by giving our websites a fresh new
> > look. I'm planning to use the fluido skin for Maven [4] for this. Why?
> > It uses twitter bootstrap, which I personally find very appealing.
> > Secondly, there are not so many other good skins available
> > (suggestions are welcome!).
> >
> > Applying fluido and maybe some restructuring of the main site requires
> > some work, that I'd like to have under version control. I see two
> > options here:
> > 1. create a branch at
> https://repos.apache.org/repos/asf/commons/cms-site/branch
> > 2. manually create a git mirror and push it to my github account
> >
> > I favor 1. but I don't know whether a branch affects buildbot. I'd
> > like to start with the main site, before handling individual
> > components. After we have agreed on a design, we can go through all
> > components and change their design as well.
> >
> > If nobody objects I'd like to start working on this, asap.
> >
> > Regards,
> > Benedikt
> >
> > [1] http://markmail.org/message/tda7qqjnkwwzwvua
> > [2] http://twitter.com/ApacheCommons
> > [3] https://issues.apache.org/jira/browse/INFRA-6500
> > [4] http://maven.apache.org/skins/maven-fluido-skin/
> >
> > --
> > http://people.apache.org/~britter/
> > http://www.systemoutprintln.de/
> > http://twitter.com/BenediktRitter
> > http://github.com/britter
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>


-- 
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message