Deploying more of the introduction page

This commit is contained in:
Angelos Chalaris 2016-11-11 16:35:58 +02:00
parent 9e688837af
commit 686a5559ee
5 changed files with 87 additions and 8 deletions

View file

@ -815,7 +815,7 @@ th:first-child, td:first-child {
display: block;
border: 1px solid #bdbdbd;
box-shadow: 0 2px 4px rgba(0, 0, 0, 0.1), 0 2px 3px rgba(0, 0, 0, 0.15);
margin-bottom: 4px; }
margin-bottom: 10px; }
td {
display: block;

File diff suppressed because one or more lines are too long

View file

@ -429,4 +429,5 @@
- Slightly tweaked the `margin`s and stuff of `p` and `hX` elements.
- Added file size comparison between toolkits.
- Updated `table` `border-radius`es.
- Deployed live demo with fixes etc.
- Deployed live demo with fixes etc.
- Added a module list and browser support to the `index` page.

View file

@ -81,7 +81,7 @@
<h2>Minimal<small>Size matters!</small></h2><br>
<i class="fa fa-compress fa-4x" aria-hidden="true"></i>
<br><br>
<p><strong>mini.css</strong> aims to provide as much functionality as possible in about 5KB gzipped. This very small footprint means that your websites and web applications will load faster, while still looking great utilising the modern components we provide!</p>
<p><strong>mini.css</strong> aims to provide as much functionality as possible in about 5KB gzipped. This very small footprint means that your websites and web applications will load faster, while still looking great utilising the modern components we provide!</p><br>
</div>
</div>
<div class="col-sm-12 col-md card fluid box-centered">
@ -89,7 +89,7 @@
<h2>Reponsive<small>Think mobile!</small></h2><br>
<i class="fa fa-mobile fa-4x" aria-hidden="true"></i>
<br><br>
<p><strong>mini.css</strong> is crafted with both desktops and mobile devices in mind. All of its components are well-tested on different devices and will respond to any changes in the viewport, allowing for an experience tailored to each user's device!</p>
<p><strong>mini.css</strong> is crafted with both desktops and mobile devices in mind. All of its components are well-tested on different devices and will respond to any changes in the viewport, allowing for an experience tailored to each user's device!</p><br>
</div>
</div>
<div class="col-sm-12 col-md card fluid box-centered">
@ -97,12 +97,12 @@
<h2>Style-agnostic<small>Infinitely customizable!</small></h2><br>
<i class="fa fa-paint-brush fa-4x" aria-hidden="true"></i>
<br><br>
<p><strong>mini.css</strong> provides you with a customizable flavor system, allowing you to be a designer without all the hard work. This way you can create your own custom design and personalize your websites any way you want!</p>
<p><strong>mini.css</strong> provides you with a customizable flavor system, allowing you to be a designer without all the hard work. This way you can create your own custom design and personalize your websites any way you want!</p><br>
</div>
</div>
</div>
<div class="row">
<div class="col-sm">
<div class="col-sm-12">
<h2>Quick overview</h2>
<p>Take a couple of minutes to learn how <strong>mini.css</strong> differs from all those other UI toolkits (Bootstrap, Semantic UI etc).</p>
<hr>
@ -156,7 +156,85 @@
</tbody>
</table><br>
<p><mark class="secondary" style="font-size: 1.4em; padding: 3px 10px;">!</mark>&nbsp;The above comparison takes into account only the CSS files of each framework. <strong>mini.css</strong>'s size is an approximation due to the nature of its flavor system. The calculated results were produced using <a href="http://refresh-sf.com/">Refresh-SF</a>.</p>
<br>
</div>
<div class="col-sm-12 col-md">
<h3>Module list</h3>
<ul>
<li><strong>Core</strong> - Resets, typography rules and fixes</li>
<li><strong>Grid</strong> - Powerful, responsive flexbox-based grid</li>
<li><strong>Navigation</strong> - Common elements for navigation</li>
<li><strong>Input Control</strong> - Forms, buttons and inputs</li>
<li><strong>Table</strong> - Modern, responsive tables</li>
<li><strong>Card</strong> - Sleek, modern content containers</li>
<li><strong>Tab</strong> - Responsive tabs and accordions</li>
<li><strong>Contextual</strong> - Contextual highlights and alerts</li>
<li><strong>Progress</strong> - Modern progress bars and loaders</li>
<li><strong>Utility</strong> - Utility and helper classes</li>
</ul>
</div>
<div class="col-sm-12 col-md">
<h3>Why does <strong>mini.css</strong> have so few modules?</h3>
<p>Modules are what makes toolkits so powerful, by giving developers the essential components they need to structure and style their websites. <strong>mini.css</strong> simplifies the crafting and learning process for new developers by providing a handful of very powerful modules that can do many different things. This way, new developers will only have to learn a few different HTML structures and patterns, while having the ability to build a lot of interesting things with them. For example, cards can be used for almost any type of layout and can be customized to do exactly what the developer wants. Tabs, on the other hand, are very responsive on mobile, collapsing to a stack below a certain width, but they can also be forced into a stack, allowing accordions and collapses to be built using the same building block as tabs.</p>
</div>
</div>
<div class="col-sm-12">
<table>
<caption>Browser support</caption>
<thead>
<tr>
<th>Browser</th>
<th>Not supported</th>
<th>Partially supported</th>
<th>Fully supported</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Browser">Internet Explorer</td>
<td data-label="Not supported">8-</td>
<td data-label="Partially supported">9 - 10</td>
<td data-label="Fully supported">11+</td>
</tr>
<tr>
<td data-label="Browser">Edge</td>
<td data-label="Not supported">n/a</td>
<td data-label="Partially supported">n/a</td>
<td data-label="Fully supported">12+</td>
</tr>
<tr>
<td data-label="Browser">Firefox</td>
<td data-label="Not supported">21-</td>
<td data-label="Partially supported">22-27</td>
<td data-label="Fully supported">28+</td>
</tr>
<tr>
<td data-label="Browser">Chrome</td>
<td data-label="Not supported">20-</td>
<td data-label="Partially supported">n/a</td>
<td data-label="Fully supported">21+</td>
</tr>
<tr>
<td data-label="Browser">Safari</td>
<td data-label="Not supported">6-</td>
<td data-label="Partially supported">n/a</td>
<td data-label="Fully supported">6.1+</td>
</tr>
<tr>
<td data-label="Browser">Opera</td>
<td data-label="Not supported">11.5-</td>
<td data-label="Partially supported">12.1-16</td>
<td data-label="Fully supported">17+</td>
</tr>
<tr>
<td data-label="Browser">Android Browser</td>
<td data-label="Not supported">4.3-</td>
<td data-label="Partially supported">n/a</td>
<td data-label="Fully supported">4.4+</td>
</tr>
</tbody>
</table><br>
<p><mark class="secondary" style="font-size: 1.4em; padding: 3px 10px;">!</mark>&nbsp;Due to the way <strong>mini.css</strong> is crafted, some legacy browsers are not supported anymore and some others are partially supported. This could be a dealbreaker for some developers, however most legacy browsers will display a less feature-rich and modern website. Apart from the above table, note that some mobile browsers like Opera Mini, IE Mobile and UC Browser for Android are officially supported, but some features may not display or behave properly due to the browsers themselves.</p>
</div>
</div></main>
<!-- End of page content-->

View file

@ -276,7 +276,7 @@ $table-row-padding: 6px; // Padding for <tr> - both views
$table-column-padding: 10px; // Padding for <td> and <th> - desktop view
$table-head-back-color: #eceff1; // Background color for <th>
$table-mobile-breakpoint: 768px; // Breakpoint for <table> mobile view
$table-mobile-card-spacing: 4px; // Space between <tr> cards - mobile view
$table-mobile-card-spacing: 10px; // Space between <tr> cards - mobile view
$table-mobile-card-label: 'data-label'; // Attribute used to replace column headers
// in mobile view [1]
$table-mobile-label-font-weight:$bold-font-weight; // Font weight for mobile headers