You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jon Harper (JIRA)" <ji...@apache.org> on 2016/07/19 16:26:20 UTC
[jira] [Updated] (MSKINS-131) Enable the responsive features of
bootstrap 2.3.2
[ https://issues.apache.org/jira/browse/MSKINS-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jon Harper updated MSKINS-131:
------------------------------
Attachment: fluido-reponsive.patch
Patch adding bootstrap-responsive.css and using it in the pom.xml
> Enable the responsive features of bootstrap 2.3.2
> -------------------------------------------------
>
> Key: MSKINS-131
> URL: https://issues.apache.org/jira/browse/MSKINS-131
> Project: Maven Skins
> Issue Type: Improvement
> Components: Fluido Skin
> Affects Versions: fluido-1.5
> Environment: All
> Reporter: Jon Harper
> Priority: Minor
> Fix For: fluido-1.6
>
> Attachments: fluido-reponsive.patch
>
>
> Bootstrap 2.3.2 has opt-in support for responsive layouts. In 2016, mobile has grown a lot. I think it should be enabled.
> To enable it, we just have to download bootstrap-responsive.css from http://getbootstrap.com/2.3.2/ and add it to the page. See http://getbootstrap.com/2.3.2/scaffolding.html#responsive
> The following mail was sent to the mailing list:
> {quote}
> I tried enabling Bootstrap's 2 responsive mode on
> https://maven.apache.org and I thought that it was better than the
> current version. Please see a demo here: http://jonenst.github.io/maven-site/ .
> I also added preview images of the main the page using firefox
> "Responsive Design View".
> The only difference between the two types of images is the inclusion
> of the responsive css as per
> http://getbootstrap.com/2.3.2/scaffolding.html#responsive .
> Note that the responsive mode does significant changes only on
> displays of width 767 pixels or less. Above 767px, the changes are very
> minor (tiny adjustments to fonts, columns and gutters sizes).
> Did you try enabling the responsive mode? Was there something
> preventing you from using it ? The only drawback I see is that devices
> with 767 pixels have a bigger menu than needed, but:
> - the current mode already has some problems (text and images going
> outside of the menu, less size of the content).
> - there are almost no devices in the 610-767 range. (see
> http://mydevice.io/devices/ ). For 600px width, the menu still looks
> big but not as oversized as for 767 pixels and using it this way is an
> improvement.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)