From 0afb5277add03c4b4a044808882cb6ed3e8741c1 Mon Sep 17 00:00:00 2001 From: Angelos Chalaris Date: Mon, 22 May 2017 17:05:40 +0300 Subject: [PATCH] Documentation update Pretty sizeable documentation update, improving layout, typos etc. Also added the Codepen Project to the templates page, a small note to star the project in the front page and two more examples in the drawer component documentation to make sure that everything is properly documented. --- .npmignore | 1 + docs/card.html | 50 +++++++------- docs/contextual.html | 34 +++++----- docs/core.html | 22 +++--- docs/customization/card.html | 15 ++-- docs/customization/contextual.html | 26 ++++--- docs/customization/core.html | 19 +++--- docs/customization/grid.html | 15 ++-- docs/customization/index.html | 18 ++--- docs/customization/input_control.html | 23 +++---- docs/customization/navigation.html | 27 ++++---- docs/customization/progress.html | 19 +++--- docs/customization/tab.html | 13 ++-- docs/customization/table.html | 15 ++-- docs/customization/utility.html | 26 ++++--- docs/flavors.html | 22 +++--- docs/grid.html | 83 +++++++++++------------ docs/index.html | 25 ++++--- docs/input_control.html | 64 +++++++++--------- docs/modules.html | 24 +++---- docs/navigation.html | 76 ++++++++++++++------- docs/progress.html | 40 +++++------ docs/project_thumbnail.png | Bin 0 -> 19199 bytes docs/quick_reference.html | 94 +++++++++++++------------- docs/tab.html | 36 +++++----- docs/table.html | 38 +++++------ docs/templates.html | 27 ++++---- docs/utility.html | 56 +++++++-------- docs/v2/DEVLOG.md | 13 +++- 29 files changed, 476 insertions(+), 445 deletions(-) create mode 100644 docs/project_thumbnail.png diff --git a/.npmignore b/.npmignore index 715b2dc..cd44198 100644 --- a/.npmignore +++ b/.npmignore @@ -1,6 +1,7 @@ docs/v1 docs/v2 docs/page_thumb.png +docs/project_thumbnail.png prepros-6\.config docs/browser-logos docs/mini-logo.svg diff --git a/docs/card.html b/docs/card.html index 812295c..26a9687 100644 --- a/docs/card.html +++ b/docs/card.html @@ -81,8 +81,8 @@

Card

-

The card module provides you with modern, responsive, general-purpose containers for your page's contents. They are very easy to use and their structure is really simple and versatile. Layouts will respond to smaller screens, realigning the cards in a manner that makes your page mobile-friendly.

-

All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.


+

The card module provides you with modern, responsive, general-purpose containers for your page's contents. They are very easy to use and their structure is really simple and versatile. Layouts will respond to smaller screens, realigning the cards in a manner that makes your page mobile-friendly.

+

All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.


@@ -90,11 +90,11 @@

Quick overview

-

The main content of a website or web app needs to be easy to access and well organized no matter the nature of the content itself. The card module seeks to help deal with this problem, by utilizing the Flexbox Layout in order to provide general-purpose containers that help you present the information you want in the best possible way. Cards are designed in a very modern way, self-aligning and structuring their content based on your needs, while also being fully responsive to changes and compatible with the versatile grid module to deliver the best experience on any device.


+

The main content of a website or web app needs to be easy to access and well organized no matter the nature of the content itself. The card module seeks to help deal with this problem, by utilizing the Flexbox Layout in order to provide general-purpose containers that help you present the information you want in the best possible way. Cards are designed in a very modern way, self-aligning and structuring their content based on your needs, while also being fully responsive to changes and compatible with the versatile grid module to deliver the best experience on any device.


Quick start

-

To use the card module, simply include the link to the flavor you are using and start writing your HTML page as usual. Remember that the card module is heavily dependent on the grid module, so you might want to first familiarize with its basic layout. One suggestion we will make is to add the following line inside your HTML page's <head> to utilize the viewport meta tag:

+

To use the card module, simply include the link to the flavor you are using and start writing your HTML page as usual. Remember that the card module is heavily dependent on the grid module, so you might want to first familiarize with its basic layout. One suggestion we will make is to add the following line inside your HTML page's <head> to utilize the viewport meta tag:

<meta name="viewport" content="width=device-width, initial-scale=1">

@@ -117,13 +117,13 @@
-

To start using cards in your layout, you need to be somewhat familiar with the grid module, so if you aren't, take a minute to read how its basic layout works. The basic syntax for cards is composed of three components, presented below in the order they should be added to the DOM tree:

-
    +

    To start using cards in your layout, you need to be somewhat familiar with the grid module, so if you aren't, take a minute to read how its basic layout works. The basic syntax for cards is composed of three components, presented below in the order they should be added to the DOM tree:

    +
    1. At the outermost level of the card layout syntax is a .row, which serves as a wrapper for all the cards inside it.
    2. Inside the .row, cards are defined as <div> elements of the .card class.
    3. Finally, inside the .cards, you can define sections using the .section class to wrap your content.
    -

    Note that cards will respond to screen changes, realigning themselves as necessary to fit on the page.

    +

    Note that cards will respond to screen changes, realigning themselves as necessary to fit on the page.

    Sample code

    <div class="row">
   <div class="card">
@@ -143,7 +143,7 @@

Notes

- 
<div class="card">
@@ -167,14 +167,14 @@
   </div>
   <p>Content not in a section!</p>
 </div>
-

Don't: Avoid using cards with content inside them that is not wrapped in sections. Try to use a single .section to wrap the content inside these to avoid unexpected behavior.

+

Don't: Avoid using cards with content inside them that is not wrapped in sections. Try to use a single .section to wrap the content inside these to avoid unexpected behavior.

<div class="card">
   <h3 class="section">Card Title</h3>
   <p class="section">Card content...</p>
 </div>
-

Do: You can use the .section class for things other than <div> elements (e.g. <h1>-<h6>, <p>, <button>).

+

Do: You can use the .section class for things other than <div> elements (e.g. <h1>-<h6>, <p>, <button>).

<div class="row">
@@ -185,7 +185,7 @@
   <div class="card">
   </div>
 </div>
-

Don't: If you want to place multiple cards side by side, add them all inside the same .row. Placing cards inside different rows or not inside rows at all can result in unexpected behavior.

+

Don't: If you want to place multiple cards side by side, add them all inside the same .row. Placing cards inside different rows or not inside rows at all can result in unexpected behavior. 

<div class="card">
@@ -201,7 +201,7 @@
         </div>
     </div>
 </div>
-

Do: You can place .row elements inside .card elements, if you want. you should normally also make those rows into card .sections, but for this specific case you might want to make an exception sometimes.

+

Do: You can place .row elements inside .card elements, if you want. you should normally also make those rows into card .sections, but for this specific case you might want to make an exception sometimes.

<div class="card row">
@@ -209,7 +209,7 @@
 <!-- or -->
 <div class="card col-sm">
 </div>
-

Don't: You should not have elements that are both cards and rows or columns at the same time.

+

Don't: You should not have elements that are both cards and rows or columns at the same time.

@@ -232,7 +232,7 @@
-

You can do a lot more with card sections apart from filling them with textual content. First off, you can add media sections to your cards, applying the styles of .section and .media to an <img> element or a video element of your choice (e.g. using a <iframe> element in the same manner). If you want a section to have more space around it, use the .double-padded class. There are also two section color variations: .dark and .darker.

+

You can do a lot more with card sections apart from filling them with textual content. First off, you can add media sections to your cards, applying the styles of .section and .media to an <img> element or a video element of your choice (e.g. using a <iframe> element in the same manner). If you want a section to have more space around it, use the .double-padded class. There are also two section color variations: .dark and .darker.

Sample code

<div class="card">
   <img src="..." class="section media">
@@ -244,7 +244,7 @@

Notes

-
-

Apart from the normal-sized cards (320px wide), there are also two different fixed-width card styles, which can be applied using the .small and .large classes respectively. Fluid cards are available via the .fluid class, but they require one extra step in the card structure, between the .row and .card step, which is to insert either a .col-SCR_SZ, replacing SCR_SZ with one of the available screen size names (sm for smaller screens, md for medium-sized screens or lg for larger screens) or a .col-SCR_SZ-COL_WD to specify columns with fixed width, replacing SCR_SZ with one of the available screen size names and COL_WD with a number from 1 to 12 specifying the width of the column.

+

Apart from the normal-sized cards (320px wide), there are also two different fixed-width card styles, which can be applied using the .small and .large classes respectively. Fluid cards are available via the .fluid class, but they require one extra step in the card structure, between the .row and .card step, which is to insert either a .col-SCR_SZ, replacing SCR_SZ with one of the available screen size names (sm for smaller screens, md for medium-sized screens or lg for larger screens) or a .col-SCR_SZ-COL_WD to specify columns with fixed width, replacing SCR_SZ with one of the available screen size names and COL_WD with a number from 1 to 12 specifying the width of the column.

Sample code

<div class="card small">
   <div class="section">
@@ -297,7 +297,7 @@

Notes

- 
<div class="row">
@@ -323,7 +323,7 @@
     </div>
   </div>
 </div>
-

Don't: Avoid using .fluid cards without wrapping them in columns. Try to use a single .col-sm to wrap the card inside it, otherwise there might be unexpected behavior.

+

Don't: Avoid using .fluid cards without wrapping them in columns. Try to use a single .col-sm to wrap the card inside it, otherwise there might be unexpected behavior.

@@ -345,7 +345,7 @@
-

Cards can also be used to display important information or error messages to users. You can use the .warning class to display a yellow warning card or, if you need to display an error message to your users, you can use the .error class to display a red error card.

+

Cards can also be used to display important information or error messages to users. You can use the .warning class to display a yellow warning card or, if you need to display an error message to your users, you can use the .error class to display a red error card.

Sample code

<div class="card warning">
   <div class="section">
@@ -362,7 +362,7 @@

Notes

-
@@ -380,10 +380,10 @@
-

If you want to learn more about mini.css's modules, go back to the modules page and choose another module to see its documentation.

+

If you want to learn more about mini.css's modules, go back to the modules page and choose another module to see its documentation.

- + diff --git a/docs/contextual.html b/docs/contextual.html index fc801f9..d0547aa 100644 --- a/docs/contextual.html +++ b/docs/contextual.html @@ -84,8 +84,8 @@

Contextual

-

The contextual module provides you with simple tags, marks and highlights for your pages, allowing you to easily emphasize parts of your text. Contextual toasts and tooltips are also provided, aiming to help deliver important information to users. HTML5 elements and simple rules are used in order to make important messages and pieces of content stand out easily.

-

All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.


+

The contextual module provides you with simple tags, marks and highlights for your pages, allowing you to easily emphasize parts of your text. Contextual toasts and tooltips are also provided, aiming to help deliver important information to users. HTML5 elements and simple rules are used in order to make important messages and pieces of content stand out easily.

+

All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.


@@ -93,11 +93,11 @@

Quick overview

-

Almost every website present on the web has some sort of content that needs highlighting in one way or another. The contextual module provides you with simple semantic text highlighting that utilises the <mark> HTML element. Apart from that, this module contains styles and definitions for a simple .toast container, that you can use to display toast messages on your websites and web apps. Toasts mimic the native application notifications of certain devices, making them mobile friendly. Finally, a simple accessible .tooltip implementation is included. All components in this module are fully accessible, so that's another thing not to worry about.


+

Almost every website present on the web has some sort of content that needs highlighting in one way or another. The contextual module provides you with simple semantic text highlighting that utilises the <mark> HTML element. Apart from that, this module contains styles and definitions for a simple .toast container, that you can use to display toast messages on your websites and web apps. Toasts mimic the native application notifications of certain devices, making them mobile friendly. Finally, a simple accessible .tooltip implementation is included. All components in this module are fully accessible, so that's another thing not to worry about.


Quick start

-

To use the contextual module, simply include the link to the flavor you are using and start writing your HTML page as usual. One suggestion we will make is to add the following line inside your HTML page's <head> to utilize the viewport meta tag:

+

To use the contextual module, simply include the link to the flavor you are using and start writing your HTML page as usual. One suggestion we will make is to add the following line inside your HTML page's <head> to utilize the viewport meta tag:

<meta name="viewport" content="width=device-width, initial-scale=1">

@@ -117,7 +117,7 @@
-

To add simple highlights in your text, you can use the <mark> HTML element. These highlights come pre-styled to use the default primary color, but if you would rather use another color for your highlight you can easily add the .secondary or .tertiary class to a <mark> element. For longer pieces of text that need highlighting, consider adding the .inline-block class to make them stand out even more. Finally, you can create contextual tags, using the .tag class.

+

To add simple highlights in your text, you can use the <mark> HTML element. These highlights come pre-styled to use the default primary color, but if you would rather use another color for your highlight you can easily add the .secondary or .tertiary class to a <mark> element. For longer pieces of text that need highlighting, consider adding the .inline-block class to make them stand out even more. Finally, you can create contextual tags, using the .tag class.

Sample code

<mark>primary</mark>
 <mark class="secondary">secondary</mark>
@@ -128,7 +128,7 @@

Notes

- 
<mark class="secondary tertiary">no, no</mark>
 <!-- or -->
 <mark class="inline-block tag">oh, no</mark>
-

Don't: Avoid combining two contextual color classes or a .tag and an .inline-block, as these combinations might result in unexpected behavior.

+

Don't: Avoid combining two contextual color classes or a .tag and an .inline-block, as these combinations might result in unexpected behavior.

<mark class="inline-block">some
   <mark class="secondary">text</mark>
 </mark>
-

Do: You can only nest a <mark> inside another if the outer one is of the .inline-block class. You can color the inner <mark> using any of the contextual color classes or even make it a .tag. Be careful, however, to not make the inner <mark> an .inline-block as well.

+

Do: You can only nest a <mark> inside another if the outer one is of the .inline-block class. You can color the inner <mark> using any of the contextual color classes or even make it a .tag. Be careful, however, to not make the inner <mark> an .inline-block as well.

<mark>some
   <mark class="secondary">text</mark>
 </mark>
-

Don't: Avoid using nested <mark> elements, unless the outer <mark> element is an .inline-block.

+

Don't: Avoid using nested <mark> elements, unless the outer <mark> element is an .inline-block.

@@ -175,7 +175,7 @@
-

Toasts aim to help bridge the gap between web and native applications on mobile devices, by displaying native-looking toast messages. To create a toast, wrap some text inside a <span> element with the .toast class. Toasts appear at the bottom of the screen on top of everything else. If you want to create smaller or larger toast messasges, you can add the .small or .large classes respectively.

+

Toasts aim to help bridge the gap between web and native applications on mobile devices, by displaying native-looking toast messages. To create a toast, wrap some text inside a <span> element with the .toast class. Toasts appear at the bottom of the screen on top of everything else. If you want to create smaller or larger toast messasges, you can add the .small or .large classes respectively.

Sample code

<span class="toast">This is a normal toast message!</span>
 <span class="toast small">This is a large toast message!</span>
@@ -191,7 +191,7 @@
               

                 

                   
<span class="toast small large">Not a good toast</span>

-                  
Don't: Avoid combining two toast size variants, as this might cause unexpected behavior.

+                  
Don't: Avoid combining two toast size variants, as this might cause unexpected behavior.
@@ -210,7 +210,7 @@
-

Tooltips can be used to convey context-sensitive information when the user hovers over some text. To create a tooltip, simply wrap the text you want users to hover over in an element with the .tooltip class (our choice is usually a <span> element, but your needs may differ) and add an aria-label in that element, setting its value to the content of your tooltip. Tooltips display at the top of the hovered text by default, so if you want to show them below the text, add the .bottom class to them.

+

Tooltips can be used to convey context-sensitive information when the user hovers over some text. To create a tooltip, simply wrap the text you want users to hover over in an element with the .tooltip class (our choice is usually a <span> element, but your needs may differ) and add an aria-label in that element, setting its value to the content of your tooltip. Tooltips display at the top of the hovered text by default, so if you want to show them below the text, add the .bottom class to them.

Sample code

<span class="tooltip" aria-label="This is a tooltip">Hover over this text to see a tooltip!</span>
 <span class="tooltip bottom" aria-label="This is a tooltip">Hover over this text to see a reverse tooltip!</span>
@@ -218,10 +218,10 @@

Notes

-
@@ -229,10 +229,10 @@
-

If you want to learn more about mini.css's modules, go back to the modules page and choose another module to see its documentation.

+

If you want to learn more about mini.css's modules, go back to the modules page and choose another module to see its documentation.

- + diff --git a/docs/core.html b/docs/core.html index 0729fc7..6002251 100644 --- a/docs/core.html +++ b/docs/core.html @@ -81,8 +81,8 @@

Core

-

The core module contains basic reset and fix rules, based on Normalize.css v5.0.0, along with lots of custom typography rules. Most textual HTML5 elements are styled by this module, so you can start writing your pages immediately without worrying about font families, weights, sizes, line heights, paddings and the like.

-

All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.


+

The core module contains basic reset and fix rules, based on Normalize.css v5.0.0, along with lots of custom typography rules. Most textual HTML5 elements are styled by this module, so you can start writing your pages immediately without worrying about font families, weights, sizes, line heights, paddings and the like.

+

All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.


@@ -90,11 +90,11 @@

Quick overview

-

Before applying any typography and styling rules, some resets need to be applied to make sure that different elements display consistently on all browsers. The core module utilizes the ruleset of Normalize.css v5.0.0 to apply those much needed resets and fixes. However, to keep the framework small, we removed some rules that only help with legacy browser support and also tweaked a lot of the rules around to use customizable variables so no duplicate rules are applied, taking up unnecessary space. The typography rules in core deal with a page's basics, like fonts and styling of headings and paragraphs, horizontal rules, colors, margins, padding etc.


+

Before applying any typography and styling rules, some resets need to be applied to make sure that different elements display consistently on all browsers. The core module utilizes the ruleset of Normalize.css v5.0.0 to apply those much needed resets and fixes. However, to keep the framework small, we removed some rules that only help with legacy browser support and also tweaked a lot of the rules around to use customizable variables so no duplicate rules are applied, taking up unnecessary space. The typography rules in core deal with a page's basics, like fonts and styling of headings and paragraphs, horizontal rules, colors, margins, padding etc.


Quick start

-

To use the core module, simply include the link to the flavor you are using and start writing your HTML page as usual. One suggestion we will make is to add the following line inside your HTML page's <head> to utilize the viewport meta tag:

+

To use the core module, simply include the link to the flavor you are using and start writing your HTML page as usual. One suggestion we will make is to add the following line inside your HTML page's <head> to utilize the viewport meta tag:

<meta name="viewport" content="width=device-width, initial-scale=1">

@@ -107,7 +107,7 @@

Typography

-

For the basic typography rules we did the following, along with other things presented below:

+

For the basic typography rules we did the following, along with other things presented below:

  • We use a native font stack to figure out the best font for your device.
  • We set the colors to background: #f8f8f8; and color: #212121;.
    • @@ -133,7 +133,7 @@
    Heading 6Subheading
-

All six of the HTML headings (<h1> - <h6>) are styled with simple rules, providing a clean base for your pages' headings. Apart from the headings themselves, complementary rules are provided for <small> elements inside headings, allowing you to define subheadings or explanatory text for those headings. These subheadings are stylized to display below the headings in smaller, lighter type.

+

All six of the HTML headings (<h1> - <h6>) are styled with simple rules, providing a clean base for your pages' headings. Apart from the headings themselves, complementary rules are provided for <small> elements inside headings, allowing you to define subheadings or explanatory text for those headings. These subheadings are stylized to display below the headings in smaller, lighter type.

Sample code

<h1>Heading 1<small>Subheading</small></h1>
 <h2>Heading 2<small>Subheading</small></h2>
@@ -161,7 +161,7 @@
-

The most common HTML5 elements must be things like <p>aragraphs, bold (<strong>) & italics (<em>) text, links (<a>), horizontal rules (<hr>) and <small> text. These, along with a few others, are styled by default using clean, modern design to make your pages look cool and stand out from the rest of the internet.

+

The most common HTML5 elements must be things like <p>aragraphs, bold (<strong>) & italics (<em>) text, links (<a>), horizontal rules (<hr>) and <small> text. These, along with a few others, are styled by default using clean, modern design to make your pages look cool and stand out from the rest of the internet.

Sample code

<p>This is a paragraph with some <strong>bold text</strong> and some <em>italics text</em>.</p>
 <a href="#">This is a link.</a>
@@ -200,7 +200,7 @@
-

Lists are also very commonly used in websites and apps. We tweaked a few margins and paddings to save some space and make them align properly with the rest of the common HTML elements that we use, but both unordered lists (<ul>) and ordered lists (<ol>) are minimally pre-styled to make things a little bit easier for you.

+

Lists are also very commonly used in websites and apps. We tweaked a few margins and paddings to save some space and make them align properly with the rest of the common HTML elements that we use, but both unordered lists (<ul>) and ordered lists (<ol>) are minimally pre-styled to make things a little bit easier for you.

Sample code

<ul>
   <li>Apple</li>
@@ -227,7 +227,7 @@
 		                
image
Image caption
-

Image elements (<img>) are responsive by default, without the need for any special classes or anything else. We made sure they will scale down as necessary to display properly on smaller devices, while keeping their original aspect ratio, but they will never scale up above their original size.

On a side note, if you want to add captions to images, you can use a <figcaption> element, while wrapping both the image and it inside a <figure>.

+

Image elements (<img>) are responsive by default, without the need for any special classes or anything else. We made sure they will scale down as necessary to display properly on smaller devices, while keeping their original aspect ratio, but they will never scale up above their original size.

On a side note, if you want to add captions to images, you can use a <figcaption> element, while wrapping both the image and it inside a <figure>.

Sample code

<figure>
   <img src="...">
@@ -240,10 +240,10 @@
-

If you want to learn more about mini.css's modules, go back to the modules page and choose another module to see its documentation.

+

If you want to learn more about mini.css's modules, go back to the modules page and choose another module to see its documentation.

- + diff --git a/docs/customization/card.html b/docs/customization/card.html index 3536ebd..f31eea5 100644 --- a/docs/customization/card.html +++ b/docs/customization/card.html @@ -80,8 +80,7 @@

Card

-

The card module provides you with modern, responsive, general-purpose containers for your page's contents. They are very easy to use and their structure is really simple and versatile. Layouts will respond to smaller screens, realigning the cards in a manner that makes your page mobile-friendly.

-

All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.


+

The card module provides you with modern, responsive, general-purpose containers for your page's contents. They are very easy to use and their structure is really simple and versatile. Layouts will respond to smaller screens, realigning the cards in a manner that makes your page mobile-friendly.


@@ -89,11 +88,11 @@

Quick overview

-

The main content of a website or web app needs to be easy to access and well organized no matter the nature of the content itself. The card module seeks to help deal with this problem, by utilizing the Flexbox Layout in order to provide general-purpose containers that help you present the information you want in the best possible way. Cards are designed in a very modern way, self-aligning and structuring their content based on your needs, while also being fully responsive to changes and compatible with the versatile grid module to deliver the best experience on any device.


+

The main content of a website or web app needs to be easy to access and well organized no matter the nature of the content itself. The card module seeks to help deal with this problem, by utilizing the Flexbox Layout in order to provide general-purpose containers that help you present the information you want in the best possible way. Cards are designed in a very modern way, self-aligning and structuring their content based on your needs, while also being fully responsive to changes and compatible with the versatile grid module to deliver the best experience on any device.


Quick start

-

To customize the card module, duplicate an existing flavor file (we suggest you use the mini-default.scss flavor file) and use this page's variable tables and mixins as a reference to change only the values you need. Remember to compile your flavor file (not the module's partial file) using a Sass preprocessor (we highly recommend using sass-autocompile if you are working with Atom).


+

To customize the card module, duplicate an existing flavor file (we suggest you use the mini-default.scss flavor file) and use this page's variable tables and mixins as a reference to change only the values you need. Remember to compile your flavor file (not the module's partial file) using a Sass preprocessor (we highly recommend using sass-autocompile if you are working with Atom).


@@ -104,7 +103,7 @@

Cards & sections

-

The card module's card system uses a few custom classes to create cards and sections, along with a variety of variables to customize their look and feel.


+

The card module's card system uses a few custom classes to create cards and sections, along with a variety of variables to customize their look and feel.


@@ -175,7 +174,7 @@

Card mixins

-

The card module contains a couple of mixins for customizing card styles, along with two more for creating custom section styles.


+

The card module contains a couple of mixins for customizing card styles, along with two more for creating custom section styles.


Variables
@@ -315,10 +314,10 @@
-

If you want to learn more about customizing mini.css, go back to the customization page or choose a module from the top menu to see its documentation.

+

If you want to learn more about customizing mini.css, go back to the customization page or choose a module from the top menu to see its documentation.

- + diff --git a/docs/customization/contextual.html b/docs/customization/contextual.html index d917208..e16e03e 100644 --- a/docs/customization/contextual.html +++ b/docs/customization/contextual.html @@ -79,8 +79,7 @@

Contextual

-

The contextual module provides you with simple tags, marks and highlights for your pages, allowing you to easily emphasize parts of your text. Contextual toasts and tooltips are also provided, aiming to help deliver important information to users. HTML5 elements and simple rules are used in order to make important messages and pieces of content stand out easily.

-

All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.


+

The contextual module provides you with simple tags, marks and highlights for your pages, allowing you to easily emphasize parts of your text. Contextual toasts and tooltips are also provided, aiming to help deliver important information to users. HTML5 elements and simple rules are used in order to make important messages and pieces of content stand out easily.


@@ -88,11 +87,11 @@

Quick overview

-

Almost every website present on the web has some sort of content that needs highlighting in one way or another. The contextual module provides you with simple semantic text highlighting that utilises the <mark> HTML element. Apart from that, this module contains styles and definitions for a simple .toast container, that you can use to display toast messages on your websites and web apps. Toasts mimic the native application notifications of certain devices, making them mobile friendly. Finally, a simple accessible .tooltip implementation is included. All components in this module are fully accessible, so that's another thing not to worry about.


+

Almost every website present on the web has some sort of content that needs highlighting in one way or another. The contextual module provides you with simple semantic text highlighting that utilises the <mark> HTML element. Apart from that, this module contains styles and definitions for a simple .toast container, that you can use to display toast messages on your websites and web apps. Toasts mimic the native application notifications of certain devices, making them mobile friendly. Finally, a simple accessible .tooltip implementation is included. All components in this module are fully accessible, so that's another thing not to worry about.


Quick start

-

To customize the contextual module, duplicate an existing flavor file (we suggest you use the mini-default.scss flavor file) and use this page's variable tables and mixins as a reference to change only the values you need. Remember to compile your flavor file (not the module's partial file) using a Sass preprocessor (we highly recommend using sass-autocompile if you are working with Atom).


+

To customize the contextual module, duplicate an existing flavor file (we suggest you use the mini-default.scss flavor file) and use this page's variable tables and mixins as a reference to change only the values you need. Remember to compile your flavor file (not the module's partial file) using a Sass preprocessor (we highly recommend using sass-autocompile if you are working with Atom).


@@ -103,7 +102,7 @@

Text highlighting

-

The contextual module's styling of <mark> elements is highly customizable.


+

The contextual module's styling of <mark> elements is highly customizable.


Card mixin definitions
@@ -162,7 +161,7 @@

Toasts

-

The contextual module's contains custom classes and styles for defining toast messages.


+

The contextual module's contains custom classes and styles for defining toast messages.


Variables
@@ -213,7 +212,7 @@

Tooltips

-

The contextual module's contains a flag to enable or disable tooltips, custom classes for creating them and other variables for style customization.


+

The contextual module's contains a flag to enable or disable tooltips, custom classes for creating them and other variables for style customization.


Variables
@@ -261,7 +260,7 @@

Notes:

-
    +
    1. The values used in the tooltip components will only be used if $include-tooltip is set to true.
@@ -274,7 +273,7 @@

Text highlighting mixins

-

The contextual module contains a couple of mixins for adding custom styles to <mark> elements (color and style variants).


+

The contextual module contains a couple of mixins for adding custom styles to <mark> elements (color and style variants).


Variables
@@ -358,13 +357,12 @@ -

Toast mixins

-

The contextual module contains a couple of mixins for adding custom styles to toasts (color and style variants).


+

The contextual module contains a couple of mixins for adding custom styles to toasts (color and style variants).


Mixin definitions
@@ -445,7 +443,7 @@

Tooltip mixins

-

The contextual module contains a couple of mixins for adding custom styles to tooltips (color and style variants).


+

The contextual module contains a couple of mixins for adding custom styles to tooltips (color and style variants).


Mixin definitions
@@ -523,10 +521,10 @@
-

If you want to learn more about customizing mini.css, go back to the customization page or choose a module from the top menu to see its documentation.

+

If you want to learn more about customizing mini.css, go back to the customization page or choose a module from the top menu to see its documentation.

- + diff --git a/docs/customization/core.html b/docs/customization/core.html index 1f5beda..f9bcc86 100644 --- a/docs/customization/core.html +++ b/docs/customization/core.html @@ -79,8 +79,7 @@

Core

-

The core module contains basic reset and fix rules, based on Normalize.css v5.0.0, along with lots of custom typography rules. Most textual HTML5 elements are styled by this module, so you can start writing your pages immediately without worrying about font families, weights, sizes, line heights, paddings and the like.

-

All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.


+

The core module contains basic reset and fix rules, based on Normalize.css v5.0.0, along with lots of custom typography rules. Most textual HTML5 elements are styled by this module, so you can start writing your pages immediately without worrying about font families, weights, sizes, line heights, paddings and the like.


@@ -88,11 +87,11 @@

Quick overview

-

Before applying any typography and styling rules, some resets need to be applied to make sure that different elements display consistently on all browsers. The core module utilizes the ruleset of Normalize.css v5.0.0 to apply those much needed resets and fixes. However, to keep the framework small, we removed some rules that only help with legacy browser support and also tweaked a lot of the rules around to use customizable variables so no duplicate rules are applied, taking up unnecessary space. The typography rules in core deal with a page's basics, like fonts and styling of headings and paragraphs, horizontal rules, colors, margins, padding etc.


+

Before applying any typography and styling rules, some resets need to be applied to make sure that different elements display consistently on all browsers. The core module utilizes the ruleset of Normalize.css v5.0.0 to apply those much needed resets and fixes. However, to keep the framework small, we removed some rules that only help with legacy browser support and also tweaked a lot of the rules around to use customizable variables so no duplicate rules are applied, taking up unnecessary space. The typography rules in core deal with a page's basics, like fonts and styling of headings and paragraphs, horizontal rules, colors, margins, padding etc.


Quick start

-

To customize the core module, duplicate an existing flavor file (we suggest you use the mini-default.scss flavor file) and use this page's variable tables and mixins as a reference to change only the values you need. Remember to compile your flavor file (not the module's partial file) using a Sass preprocessor (we highly recommend using sass-autocompile if you are working with Atom).


+

To customize the core module, duplicate an existing flavor file (we suggest you use the mini-default.scss flavor file) and use this page's variable tables and mixins as a reference to change only the values you need. Remember to compile your flavor file (not the module's partial file) using a Sass preprocessor (we highly recommend using sass-autocompile if you are working with Atom).


@@ -103,7 +102,7 @@

Typography & headings

-

The core module's typography rules are quite extensive and deal with background and foreground colors, used fonts, sizing and line height, along with heading, link and paragraph styling.


+

The core module's typography rules are quite extensive and deal with background and foreground colors, used fonts, sizing and line height, along with heading, link and paragraph styling.


Mixin definitions
@@ -267,7 +266,7 @@

Notes:

-
    +
    1. The value of $base-font-size will only be applied if $apply-defaults-to-all is set to true.
    2. The values of $fluid-type-start-breakpoint, $fluid-type-end-breakpoint, $fluid-type-small-type and $fluid-type-large-type will only be applied if $use-fluid-typography is set to true.
    3. The values of $heading-smalltext-b-font-size and $heading-smalltext-b-top-margin will only be applied if $make-heading-smalltext-block is set to true.
      4. @@ -283,7 +282,7 @@

      Common elements & fixes

      -

      The core module contains a plethora of styles for horizontal rules, lists and code elements, as well as a few optional display fixes for certain other elements.


      +

      The core module contains a plethora of styles for horizontal rules, lists and code elements, as well as a few optional display fixes for certain other elements.


Variables
@@ -503,7 +502,7 @@

Notes:

-
    +
    1. The value of $horizontal-rule-border-style will only be applied if $horizontal-rule-fancy-style is set to false.
    2. The value of $horizontal-rule-fancy-gradient will only be applied if $horizontal-rule-fancy-style is set to true.
    3. The value of $code-font-family will only be applied if $use-default-code-fonts is set to false.
      4. @@ -517,10 +516,10 @@
      -

      If you want to learn more about customizing mini.css, go back to the customization page or choose a module from the top menu to see its documentation.

      +

      If you want to learn more about customizing mini.css, go back to the customization page or choose a module from the top menu to see its documentation.

- + diff --git a/docs/customization/grid.html b/docs/customization/grid.html index 7e65c37..9a92618 100644 --- a/docs/customization/grid.html +++ b/docs/customization/grid.html @@ -81,8 +81,7 @@

Grid

-

The grid module provides you with a modern, responsive grid system based on the Flexible Layout Module (commonly known as flexbox). The structure of the grid is simple and logical, allowing you to quickly build your pages from scratch. Setting the layout for a page is easy and will behave the way you want them to on mobile devices and smaller screens.

-

All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.


+

The grid module provides you with a modern, responsive grid system based on the Flexible Layout Module (commonly known as flexbox). The structure of the grid is simple and logical, allowing you to quickly build your pages from scratch. Setting the layout for a page is easy and will behave the way you want them to on mobile devices and smaller screens.


@@ -90,11 +89,11 @@

Quick overview

-

Easy page layout is one of the main advantages of using a CSS framework over writing your own styles. The grid module utilizes the Flexbox Layout to provide you with a modern and responsive layout grid system for all your needs. Rules in the grid module help you create basic fluid containers for your grid and allow you to design layouts that work well on all screen sizes using a simple row and column structure. The grid system contains definitions for both fluid columns that resize according to their siblings and columns with preset sizes on different screen sizes, as well as rules that allow you to offset or move certain columns to the first or last place on the grid's row on different devices, helping you present the page in a different layout without duplicating any content. All of the rules in the module are built around accessibility, so screen readers can easily read you pages.


+

Easy page layout is one of the main advantages of using a CSS framework over writing your own styles. The grid module utilizes the Flexbox Layout to provide you with a modern and responsive layout grid system for all your needs. Rules in the grid module help you create basic fluid containers for your grid and allow you to design layouts that work well on all screen sizes using a simple row and column structure. The grid system contains definitions for both fluid columns that resize according to their siblings and columns with preset sizes on different screen sizes, as well as rules that allow you to offset or move certain columns to the first or last place on the grid's row on different devices, helping you present the page in a different layout without duplicating any content. All of the rules in the module are built around accessibility, so screen readers can easily read you pages.


Quick start

-

To customize the grid module, duplicate an existing flavor file (we suggest you use the mini-default.scss flavor file) and use this page's variable tables and mixins as a reference to change only the values you need. Remember to compile your flavor file (not the module's partial file) using a Sass preprocessor (we highly recommend using sass-autocompile if you are working with Atom).


+

To customize the grid module, duplicate an existing flavor file (we suggest you use the mini-default.scss flavor file) and use this page's variable tables and mixins as a reference to change only the values you need. Remember to compile your flavor file (not the module's partial file) using a Sass preprocessor (we highly recommend using sass-autocompile if you are working with Atom).


@@ -105,7 +104,7 @@

Classes & breakpoints

-

The grid module's systems are based on custom-named classes for containers, rows and columns, as well as reordering and ofsetting classes, breakpoints and padding.


+

The grid module's systems are based on custom-named classes for containers, rows and columns, as well as reordering and ofsetting classes, breakpoints and padding.


Variables
@@ -197,7 +196,7 @@

Notes:

-
    +
    1. The values of $grid-extra-small-prefix and $grid-small-breakpoint will only be used if $use-four-step-grid is set to true.
    2. The value of $grid-row-parent-layout-prefix will only be used if $include-parent-layout is set to true.
    @@ -208,10 +207,10 @@
    -

    If you want to learn more about customizing mini.css, go back to the customization page or choose a module from the top menu to see its documentation.

    +

    If you want to learn more about customizing mini.css, go back to the customization page or choose a module from the top menu to see its documentation.

- + diff --git a/docs/customization/index.html b/docs/customization/index.html index 2a3a0cb..b5a5c05 100644 --- a/docs/customization/index.html +++ b/docs/customization/index.html @@ -78,13 +78,13 @@

Customization

-

mini.css is built in such a way that customization is really simple. You could try out one of the pre-defined flavors, if you want, in order to get used to the framework and build something quickly and easily. However, many projects require custom styles and color palettes, which is when you need to get your hands dirty and start creating your own flavor by customizing an existing one and using mixins and variables to create your own, unique style for your brand or product. This page, along with the rest of the Customization section is aimed at developers who want to tweak the code provided with mini.css to create their own flavors for their projects, as well as active maintainers of the framework and people who just want to understand the inner workings of the codebase.

-

Use the menu to quickly jump to the documentation of any module that you want to check out. We strongly recommend, however, that you read the general information provided in this page before you start exploring the modules' code, especially if you are not familiar with the way mini.css is structured.


+

mini.css is built in such a way that customization is really simple. You could try out one of the pre-defined flavors, if you want, in order to get used to the framework and build something quickly and easily. However, many projects require custom styles and color palettes, which is when you need to get your hands dirty and start creating your own flavor by customizing an existing one and using mixins and variables to create your own, unique style for your brand or product. This page, along with the rest of the Customization section is aimed at developers who want to tweak the code provided with mini.css to create their own flavors for their projects, as well as active maintainers of the framework and people who just want to understand the inner workings of the codebase.

+

Use the menu to quickly jump to the documentation of any module that you want to check out. We strongly recommend, however, that you read the general information provided in this page before you start exploring the modules' code, especially if you are not familiar with the way mini.css is structured.



Introduction & basics

-

mini.css is written using Sass, a very popular CSS preprocessor. We use Sass to do four things:

+

mini.css is written using Sass, a very popular CSS preprocessor. We use Sass to do four things:

  • Make the code modular
  • Create variables that can be changed on the fly
    • @@ -96,30 +96,30 @@

    Modules & file structure

    -

    At the heart of mini.css are modules - groups of classes and styles that aim to solve one set of needs. There are 10 modules in mini.css, which have been already written for you. All of the modules are built using partial files, named _module_name.scss and placed in the src/mini folder. You can edit any of the modules' code and/or add your own modules, following the same structure. The only thing you need to remember to do, in order to add your module to your flavor, is to add an @import statement after all the required variable declarations towards the bottom of your flavor file and it will be compiled along with the rest of mini.css. Similarly, to disable a module, just comment out its @import statement from the flavor file.


    +

    At the heart of mini.css are modules - groups of classes and styles that aim to solve one set of needs. There are 10 modules in mini.css, which have been already written for you. All of the modules are built using partial files, named _module_name.scss and placed in the src/mini folder. You can edit any of the modules' code and/or add your own modules, following the same structure. The only thing you need to remember to do, in order to add your module to your flavor, is to add an @import statement after all the required variable declarations towards the bottom of your flavor file and it will be compiled along with the rest of mini.css. Similarly, to disable a module, just comment out its @import statement from the flavor file.


    Variables

    -

    Everything in mini.css is based on Sass variables. We try to make our variable names as descriptive as possible, usually using names like $block-element-property-name, but some things might vary a little bit. Changing the values of variables should be reasonably easy, simply navigate to the src/flavors/flavor-name.scss file for a pre-defined flavor and you will see a list of variables that you can tweak. Change the values as you see fit and your finalized stylesheet will reflect the changes you have made. We did our best to make everything as customizable as possible, so that different people can build entirely different flavors using the same building blocks.


    +

    Everything in mini.css is based on Sass variables. We try to make our variable names as descriptive as possible, usually using names like $block-element-property-name, but some things might vary a little bit. Changing the values of variables should be reasonably easy, simply navigate to the src/flavors/flavor-name.scss file for a pre-defined flavor and you will see a list of variables that you can tweak. Change the values as you see fit and your finalized stylesheet will reflect the changes you have made. We did our best to make everything as customizable as possible, so that different people can build entirely different flavors using the same building blocks.


    Code optimization

    -

    Building mini.css was no small task. Making it lightweight and customizable made things even harder, because these two things don't go well together most of the time. What we did was put more of the load on the preprocessor, instead of the final file. In order to accomplish this, we optimized as much of the code as possible, using conditions, flags and other tricks, so that compiling a flavor file might take one second longer, but loading won't. If you add any code to a flavor yourself, remember not only to make it customizable, but also to optimize it as best as possible.


    +

    Building mini.css was no small task. Making it lightweight and customizable made things even harder, because these two things don't go well together most of the time. What we did was put more of the load on the preprocessor, instead of the final file. In order to accomplish this, we optimized as much of the code as possible, using conditions, flags and other tricks, so that compiling a flavor file might take one second longer, but loading won't. If you add any code to a flavor yourself, remember not only to make it customizable, but also to optimize it as best as possible.


    Mixins

    -

    A lot of elements and components can be styled in many ways and most of the time we want a few styles to be available, without having to rewrite everything. We utilized the @mixin directive of Sass wherever we could to make it possible for you to easily create styles for pre-existing components and elements without having to tweak the base code for said elements or components. Each module's mixins can be found in the corresponding _module_name_mixins.scss file in the src/mini folder. To use a mixin, simply @import its file and then @include the mixin itself, passing values to at least its mandatory parameters. We recommend you write mixins wherever possible, if you create any new modules for mini.css.


    +

    A lot of elements and components can be styled in many ways and most of the time we want a few styles to be available, without having to rewrite everything. We utilized the @mixin directive of Sass wherever we could to make it possible for you to easily create styles for pre-existing components and elements without having to tweak the base code for said elements or components. Each module's mixins can be found in the corresponding _module_name_mixins.scss file in the src/mini folder. To use a mixin, simply @import its file and then @include the mixin itself, passing values to at least its mandatory parameters. We recommend you write mixins wherever possible, if you create any new modules for mini.css.


    -

    To read more about the inner workings of mini.css, please choose a module from the menu to view its documentation.

    +

    To read more about the inner workings of mini.css, please choose a module from the menu to view its documentation.

- + diff --git a/docs/customization/input_control.html b/docs/customization/input_control.html index 11aee25..9e751f4 100644 --- a/docs/customization/input_control.html +++ b/docs/customization/input_control.html @@ -80,8 +80,7 @@

Input Control

-

The input_control module contains rules that affect forms, input elements, buttons, checkboxes and radio buttons. All of these elements' styles are predefined, allowing you to create modern, responsive forms quickly. Layout alternatives are also provided if you want your forms to look a certain way.

-

All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.


+

The input_control module contains rules that affect forms, input elements, buttons, checkboxes and radio buttons. All of these elements' styles are predefined, allowing you to create modern, responsive forms quickly. Layout alternatives are also provided if you want your forms to look a certain way.


@@ -89,11 +88,11 @@

Quick overview

-

The presentation of forms, input fields, buttons and other interactive elements is always very important for any website or app. The input_control module provides you with much needed styling improvements for all of these elements, while keeping everything simple to use and understand, as well as combine with the other modules. Forms and input elements have a clean, modern design, while some elements like checkoxes and radio buttons get a much needed facelift. Buttons have also been stylized to look the same in all browsers, while keeping their design clean and allowing for a few color and size variants. Grouping inputs and labels or buttons is also part of this module and, as always, responsiveness is an important feature. Finally, all of the components are accessible, with a few minor caveats, that are discussed in their respective section in this page.


+

The presentation of forms, input fields, buttons and other interactive elements is always very important for any website or app. The input_control module provides you with much needed styling improvements for all of these elements, while keeping everything simple to use and understand, as well as combine with the other modules. Forms and input elements have a clean, modern design, while some elements like checkoxes and radio buttons get a much needed facelift. Buttons have also been stylized to look the same in all browsers, while keeping their design clean and allowing for a few color and size variants. Grouping inputs and labels or buttons is also part of this module and, as always, responsiveness is an important feature. Finally, all of the components are accessible, with a few minor caveats, that are discussed in their respective section in this page.


Quick start

-

To customize the input_control module, duplicate an existing flavor file (we suggest you use the mini-default.scss flavor file) and use this page's variable tables and mixins as a reference to change only the values you need. Remember to compile your flavor file (not the module's partial file) using a Sass preprocessor (we highly recommend using sass-autocompile if you are working with Atom).


+

To customize the input_control module, duplicate an existing flavor file (we suggest you use the mini-default.scss flavor file) and use this page's variable tables and mixins as a reference to change only the values you need. Remember to compile your flavor file (not the module's partial file) using a Sass preprocessor (we highly recommend using sass-autocompile if you are working with Atom).


@@ -104,7 +103,7 @@

Forms & input

-

The input_control module's forms and input fields can be easily customized to use different sizes and colors, as well as different class names for groupping.


+

The input_control module's forms and input fields can be easily customized to use different sizes and colors, as well as different class names for groupping.


Variables
@@ -252,7 +251,7 @@

Notes:

-
    +
    1. The values of $input-group-fluid-name and $input-group-mobile-breakpoint will only be used if $include-fluid-input-group is set to true.
@@ -265,7 +264,7 @@

Checkboxes & radio buttons

-

The input_control module's checkbox and radio button elements are based on custom rules and depend on the use of <label> elements and input groups to be stylized and properly displayed.


+

The input_control module's checkbox and radio button elements are based on custom rules and depend on the use of <label> elements and input groups to be stylized and properly displayed.


Variables
@@ -313,7 +312,7 @@

Notes:

-
    +
    1. It is highly recommended to stick to one unit type for the definitions of checkbox/radio elements (our suggestion is px).
@@ -326,7 +325,7 @@

Button & button groups

-

The input_control module's button elements are highly customizable, along with the button groups that can be used in combination with them.


+

The input_control module's button elements are highly customizable, along with the button groups that can be used in combination with them.


Variables
@@ -409,7 +408,7 @@

Button mixins

-

The input_control module contains a couple of mixins for adding custom styles to button elements (color and style variants).


+

The input_control module contains a couple of mixins for adding custom styles to button elements (color and style variants).


Variables
@@ -495,10 +494,10 @@
-

If you want to learn more about customizing mini.css, go back to the customization page or choose a module from the top menu to see its documentation.

+

If you want to learn more about customizing mini.css, go back to the customization page or choose a module from the top menu to see its documentation.

- + diff --git a/docs/customization/navigation.html b/docs/customization/navigation.html index eb9a625..8bc0109 100644 --- a/docs/customization/navigation.html +++ b/docs/customization/navigation.html @@ -79,8 +79,7 @@
@@ -88,11 +87,11 @@

Quick overview

-

Menus and navigation are some of the most important elements for any website or web app and their design and ease-of-use are key factors that can determine a page's bounce rates. The navigation module takes a step back from the complicated menu and navigation design paradigms of the modern web, using HTML5 elements (i.e. header, nav and footer) for basic navigation, while providing fully accessibility for screen readers. Apart from the simple horizontal navigation (headers) and vertical menus (sidebars), we opted to add a responsive slide-in drawer menu that works well with any page layout. Finally, footers are also part of the navigation module, as they can often provide the user with useful information and/or links that are very important to enhancing their experience.


+

Menus and navigation are some of the most important elements for any website or web app and their design and ease-of-use are key factors that can determine a page's bounce rates. The navigation module takes a step back from the complicated menu and navigation design paradigms of the modern web, using HTML5 elements (i.e. header, nav and footer) for basic navigation, while providing fully accessibility for screen readers. Apart from the simple horizontal navigation (headers) and vertical menus (sidebars), we opted to add a responsive slide-in drawer menu that works well with any page layout. Finally, footers are also part of the navigation module, as they can often provide the user with useful information and/or links that are very important to enhancing their experience.


Quick start

-

To customize the navigation module, duplicate an existing flavor file (we suggest you use the mini-default.scss flavor file) and use this page's variable tables and mixins as a reference to change only the values you need. Remember to compile your flavor file (not the module's partial file) using a Sass preprocessor (we highly recommend using sass-autocompile if you are working with Atom).


+

To customize the navigation module, duplicate an existing flavor file (we suggest you use the mini-default.scss flavor file) and use this page's variable tables and mixins as a reference to change only the values you need. Remember to compile your flavor file (not the module's partial file) using a Sass preprocessor (we highly recommend using sass-autocompile if you are working with Atom).


@@ -103,7 +102,7 @@

Header

-

The navigation module contains definitions for styling the <header> element, along with its contents (logo and links).


+

The navigation module contains definitions for styling the <header> element, along with its contents (logo and links).


Mixin definitions
@@ -179,7 +178,7 @@

Notes:

-
    +
    1. The value of $header-sticky-name will only be used if $include-header-sticky is set to true.
@@ -192,7 +191,7 @@

Navigation bar

-

The navigation module contains definitions for styling <nav> elements, along with the links they contain.


+

The navigation module contains definitions for styling <nav> elements, along with the links they contain.


Variables
@@ -264,7 +263,7 @@

Notes:

-
    +
@@ -277,7 +276,7 @@

Drawer

-

The navigation module contains custom classes and definitions for creating and styling a responsive drawer component.


+

The navigation module contains custom classes and definitions for creating and styling a responsive drawer component.


Variables
@@ -365,7 +364,7 @@

Notes:

-
    +
    1. The values of $drawer-normal-height should be the calculated value of the screen height minus the total height of the <header> element for best results.
@@ -378,7 +377,7 @@

Footer

-

The navigation module contains various definitions for customizing the appearance of the <footer> element.


+

The navigation module contains various definitions for customizing the appearance of the <footer> element.


Variables
@@ -426,7 +425,7 @@

Notes:

-
    +
@@ -436,10 +435,10 @@
-

If you want to learn more about customizing mini.css, go back to the customization page or choose a module from the top menu to see its documentation.

+

If you want to learn more about customizing mini.css, go back to the customization page or choose a module from the top menu to see its documentation.

- + diff --git a/docs/customization/progress.html b/docs/customization/progress.html index 004cbde..2c4c8fc 100644 --- a/docs/customization/progress.html +++ b/docs/customization/progress.html @@ -81,8 +81,7 @@

Progress

-

The progress module gives you full control over the presentation of progress and loading on your pages. Apart from progress bars and color variants for them, spinner elements are provided to help communicate that something is loading.

-

All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.


+

The progress module gives you full control over the presentation of progress and loading on your pages. Apart from progress bars and color variants for them, spinner elements are provided to help communicate that something is loading.


@@ -90,11 +89,11 @@

Quick overview

-

Progress indicators are very common UI elements for almost any website and web app, as they help communicate vital information such as the fact that a process is being executed in the background, informing the user that they should wait for it to complete before proceeding. The progress module provides you with two essential tools to communicate this information: the <progress> HTML element, which is pre-styled and compatible with modern browsers to help you communicate information about the percentage of a task and the .spinner-donut class that allows you to create an animated spinner that communicates that something is loading currently and will continue doing so for an indefinite amount of time. Both elements come with their own color and size variants and are fully accessible.


+

Progress indicators are very common UI elements for almost any website and web app, as they help communicate vital information such as the fact that a process is being executed in the background, informing the user that they should wait for it to complete before proceeding. The progress module provides you with two essential tools to communicate this information: the <progress> HTML element, which is pre-styled and compatible with modern browsers to help you communicate information about the percentage of a task and the .spinner-donut class that allows you to create an animated spinner that communicates that something is loading currently and will continue doing so for an indefinite amount of time. Both elements come with their own color and size variants and are fully accessible.


Quick start

-

To customize the progress module, duplicate an existing flavor file (we suggest you use the mini-default.scss flavor file) and use this page's variable tables and mixins as a reference to change only the values you need. Remember to compile your flavor file (not the module's partial file) using a Sass preprocessor (we highly recommend using sass-autocompile if you are working with Atom).


+

To customize the progress module, duplicate an existing flavor file (we suggest you use the mini-default.scss flavor file) and use this page's variable tables and mixins as a reference to change only the values you need. Remember to compile your flavor file (not the module's partial file) using a Sass preprocessor (we highly recommend using sass-autocompile if you are working with Atom).


@@ -105,7 +104,7 @@

Progress bar

-

The progress module's styling of <progress> elements is highly customizable.


+

The progress module's styling of <progress> elements is highly customizable.


Variables
@@ -160,7 +159,7 @@

Donut spinner

-

The progress module's donut spinner uses a custom class and a few variables for custmization.


+

The progress module's donut spinner uses a custom class and a few variables for custmization.


Variables
@@ -199,7 +198,7 @@

Progress bar mixins

-

The progress module contains a couple of mixins for adding custom styles to <progress> elements (color and style variants), as well as a mixin for creating inline progress bars.


+

The progress module contains a couple of mixins for adding custom styles to <progress> elements (color and style variants), as well as a mixin for creating inline progress bars.


Variables
@@ -311,7 +310,7 @@

Donut spinner mixins

-

The progress module contains a couple of mixins for adding custom styles to donut spinners (color and style variants).


+

The progress module contains a couple of mixins for adding custom styles to donut spinners (color and style variants).


Mixin definitions
@@ -381,10 +380,10 @@
-

If you want to learn more about customizing mini.css, go back to the customization page or choose a module from the top menu to see its documentation.

+

If you want to learn more about customizing mini.css, go back to the customization page or choose a module from the top menu to see its documentation.

- + diff --git a/docs/customization/tab.html b/docs/customization/tab.html index eb8477e..b3e442e 100644 --- a/docs/customization/tab.html +++ b/docs/customization/tab.html @@ -79,8 +79,7 @@

Tab

-

The tab module aims to combine multiple components and design paradigms, like collapses, accordions, carousels and tabs, into one general-purpose component. Tabs are very simple in structure, responsive on mobile and they allow for layout customization so that you can turn them into accordions or collapses whenever you want.

-

All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.


+

The tab module aims to combine multiple components and design paradigms, like collapses, accordions, carousels and tabs, into one general-purpose component. Tabs are very simple in structure, responsive on mobile and they allow for layout customization so that you can turn them into accordions or collapses whenever you want.


@@ -88,11 +87,11 @@

Quick overview

-

Spoilers, collapses, accordions, tabs, carousels have been a staple of modern design for quite a long time. All of these elements are implemented using the tab module's single generic container. The tab container replaces all of these design paradigms with one component that is very flexible and responsive in order to let you present your website or app's content any way you like. Tabbed navigation is very easy to implement, while collapse, accordion and carousel components use the stacked architecture of tabs. As usual, the tab container is responsive and accessible, allowing you to deliver your content properly to all devices and users.


+

Spoilers, collapses, accordions, tabs, carousels have been a staple of modern design for quite a long time. All of these elements are implemented using the tab module's single generic container. The tab container replaces all of these design paradigms with one component that is very flexible and responsive in order to let you present your website or app's content any way you like. Tabbed navigation is very easy to implement, while collapse, accordion and carousel components use the stacked architecture of tabs. As usual, the tab container is responsive and accessible, allowing you to deliver your content properly to all devices and users.


Quick start

-

To customize the tab module, duplicate an existing flavor file (we suggest you use the mini-default.scss flavor file) and use this page's variable tables and mixins as a reference to change only the values you need. Remember to compile your flavor file (not the module's partial file) using a Sass preprocessor (we highly recommend using sass-autocompile if you are working with Atom).


+

To customize the tab module, duplicate an existing flavor file (we suggest you use the mini-default.scss flavor file) and use this page's variable tables and mixins as a reference to change only the values you need. Remember to compile your flavor file (not the module's partial file) using a Sass preprocessor (we highly recommend using sass-autocompile if you are working with Atom).


@@ -103,7 +102,7 @@

Tab styling

-

The tab module contains definitions for tab styling, using custom classes and structures.


+

The tab module contains definitions for tab styling, using custom classes and structures.


Mixin definitions
@@ -187,10 +186,10 @@
-

If you want to learn more about customizing mini.css, go back to the customization page or choose a module from the top menu to see its documentation.

+

If you want to learn more about customizing mini.css, go back to the customization page or choose a module from the top menu to see its documentation.

- + diff --git a/docs/customization/table.html b/docs/customization/table.html index 43dcdb6..2cadd04 100644 --- a/docs/customization/table.html +++ b/docs/customization/table.html @@ -79,8 +79,7 @@

Table

-

The table module provides styling and responsiveness for tables. Simple rules and accessible design paradigms have been used to make creating tables quick and easy. Large tables will collapse to cards when on smaller devices or, if you don't want that, they can be locked into their default, desktop view.

-

All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.


+

The table module provides styling and responsiveness for tables. Simple rules and accessible design paradigms have been used to make creating tables quick and easy. Large tables will collapse to cards when on smaller devices or, if you don't want that, they can be locked into their default, desktop view.


@@ -88,11 +87,11 @@

Quick overview

-

Presenting information the right way is very important, especially so when dealing with large amounts of data. The table module reinvents tabular data presentation, using modern styling and responsiveness to help make tables fun again for all users no matter the device size. Tables can be either vertical or horizontal, both collapsing to a card view on smaller devices, so that they are easier to view properly. Horizontal tables are also flexible, allowing you to take as little space as possible, while still providing your users with a pleasant way to view their data. Finally, like in most CSS frameworks nowadays, you can stripe your tables to make reading them slightly less tiresome for your users' eyes. Note that all of the table variants are fully accessible.


+

Presenting information the right way is very important, especially so when dealing with large amounts of data. The table module reinvents tabular data presentation, using modern styling and responsiveness to help make tables fun again for all users no matter the device size. Tables can be either vertical or horizontal, both collapsing to a card view on smaller devices, so that they are easier to view properly. Horizontal tables are also flexible, allowing you to take as little space as possible, while still providing your users with a pleasant way to view their data. Finally, like in most CSS frameworks nowadays, you can stripe your tables to make reading them slightly less tiresome for your users' eyes. Note that all of the table variants are fully accessible.


Quick start

-

To customize the table module, duplicate an existing flavor file (we suggest you use the mini-default.scss flavor file) and use this page's variable tables and mixins as a reference to change only the values you need. Remember to compile your flavor file (not the module's partial file) using a Sass preprocessor (we highly recommend using sass-autocompile if you are working with Atom).


+

To customize the table module, duplicate an existing flavor file (we suggest you use the mini-default.scss flavor file) and use this page's variable tables and mixins as a reference to change only the values you need. Remember to compile your flavor file (not the module's partial file) using a Sass preprocessor (we highly recommend using sass-autocompile if you are working with Atom).


@@ -103,7 +102,7 @@

Table styling

-

The table module contains definitions for tables and table variants.


+

The table module contains definitions for tables and table variants.


Variables
@@ -203,7 +202,7 @@

Notes:

-
    +
    1. The values of $table-horizontal-name and $table-horizontal-breakpoint will only be used if $include-horizontal-table is set to true.
@@ -213,10 +212,10 @@
-

If you want to learn more about customizing mini.css, go back to the customization page or choose a module from the top menu to see its documentation.

+

If you want to learn more about customizing mini.css, go back to the customization page or choose a module from the top menu to see its documentation.

- + diff --git a/docs/customization/utility.html b/docs/customization/utility.html index 81abab8..8b60f2c 100644 --- a/docs/customization/utility.html +++ b/docs/customization/utility.html @@ -79,9 +79,7 @@

Utility

-

The utility module contains all the utilities and helper classes that you might want when designing a website or application. They solve common design problems efficiently and provide you with generic rules you can easily apply everywhere.

-

All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.

- +

The utility module contains all the utilities and helper classes that you might want when designing a website or application. They solve common design problems efficiently and provide you with generic rules you can easily apply everywhere.


@@ -89,11 +87,11 @@

Quick overview

-

Every website or app has different needs and no CSS framework can predict them all. The utility module addresses this issue by providing you with a handful of utility and helper classes to make common, repetitive declarations easier. These classes include, but are not limited to, generic border styling and shadows, some responsive sizing and spacing utilities and a few other things, like a close icon, breadcrumbs styling and visiblity helpers for screen readers.


+

Every website or app has different needs and no CSS framework can predict them all. The utility module addresses this issue by providing you with a handful of utility and helper classes to make common, repetitive declarations easier. These classes include, but are not limited to, generic border styling and shadows, some responsive sizing and spacing utilities and a few other things, like a close icon, breadcrumbs styling and visiblity helpers for screen readers.


Quick start

-

To customize the utility module, duplicate an existing flavor file (we suggest you use the mini-default.scss flavor file) and use this page's variable tables and mixins as a reference to change only the values you need. Remember to compile your flavor file (not the module's partial file) using a Sass preprocessor (we highly recommend using sass-autocompile if you are working with Atom).


+

To customize the utility module, duplicate an existing flavor file (we suggest you use the mini-default.scss flavor file) and use this page's variable tables and mixins as a reference to change only the values you need. Remember to compile your flavor file (not the module's partial file) using a Sass preprocessor (we highly recommend using sass-autocompile if you are working with Atom).


@@ -104,7 +102,7 @@

Visibility helpers & legacy features

-

The utility module's visiblity helpers use a couple of custom classes, while certain legacy features are also available via certain variables and custom class definitions.


+

The utility module's visiblity helpers use a couple of custom classes, while certain legacy features are also available via certain variables and custom class definitions.


Variables
@@ -148,7 +146,7 @@

Notes:

-
    +
    1. The value of $float-prefix will only be used if $include-floats is set to true.
    2. The value of $clearfix-name will only be used if $include-clearfix is set to true.
    3. The value of $center-block-name will only be used if $include-center-block is set to true.
      4. @@ -163,7 +161,7 @@

      Breadcrumbs

      -

      The utility module's breadcrumbs use a custom class and a few varaibles to allow you to customize their appearance.


      +

      The utility module's breadcrumbs use a custom class and a few varaibles to allow you to customize their appearance.


Variables
@@ -214,7 +212,7 @@

Close icon

-

The utility module's close icon uses a custom class and a few variable to customize its appearance.


+

The utility module's close icon uses a custom class and a few variable to customize its appearance.


Variables
@@ -249,7 +247,7 @@

Generic border & shadow mixins

-

The utility module contains a few mixins for creating generic borders, border styles and shadows.


+

The utility module contains a few mixins for creating generic borders, border styles and shadows.


Variables
@@ -333,7 +331,7 @@

Responsive sizing & spacing mixins

-

The utility module contains a couple of mixins for creating responsive sizing and spacing classes.


+

The utility module contains a couple of mixins for creating responsive sizing and spacing classes.


Mixin definitions
@@ -454,7 +452,7 @@

Responsive visibility helper mixins

-

The utility module contains a couple of mixins for creating responsive visibility helpers.


+

The utility module contains a couple of mixins for creating responsive visibility helpers.


Mixin definitions
@@ -572,10 +570,10 @@
-

If you want to learn more about customizing mini.css, go back to the customization page or choose a module from the top menu to see its documentation.

+

If you want to learn more about customizing mini.css, go back to the customization page or choose a module from the top menu to see its documentation.

- + diff --git a/docs/flavors.html b/docs/flavors.html index 59934f7..e6bd032 100644 --- a/docs/flavors.html +++ b/docs/flavors.html @@ -42,15 +42,15 @@

Flavors

-

One of the core ideas behind mini.css is its flavor system. A flavor is the final compiled stylesheet a website or web app uses. When you start using mini.css, you usually try out the default flavor, using one of the following references inside your HTML page's <head> tag:

+

One of the core ideas behind mini.css is its flavor system. A flavor is the final compiled stylesheet a website or web app uses. When you start using mini.css, you usually try out the default flavor, using one of the following references inside your HTML page's <head> tag:

<link rel="stylesheet" href="https://gitcdn.link/repo/Chalarangelo/mini.css/master/dist/mini-default.min.css">
<link rel="stylesheet" href="https://cdn.rawgit.com/Chalarangelo/mini.css/v2.2.0/dist/mini-default.min.css">

-

There are, however a handful of other flavors included with mini.css. Below, you can see a full list of them:


+

There are, however a handful of other flavors included with mini.css. Below, you can see a full list of them:


  • Default mini-default

    <link rel="stylesheet" href="https://gitcdn.link/repo/Chalarangelo/mini.css/master/dist/mini-default.min.css">
    -

    The default flavor for mini.css uses a light gray background and gray-black foreground color. Certain containers, such as cards and tabs use white-gray backgrounds. The grid system has 12 columns and most of the components and modules use sharp corners and light border colors. All of the colors used in this flavor are loosely based on Google's Material design color palette.

    +

    The default flavor for mini.css uses a light gray background and gray-black foreground color. Certain containers, such as cards and tabs use white-gray backgrounds. The grid system has 12 columns and most of the components and modules use sharp corners and light border colors. All of the colors used in this flavor are loosely based on Google's Material design color palette.

    Author: Chalarangelo

    Size: 7 KB

    @@ -59,7 +59,7 @@

  • Dark  View on Codepenmini-dark

    <link rel="stylesheet" href="https://gitcdn.link/repo/Chalarangelo/mini.css/master/dist/mini-dark.min.css">
    -

    The dark version of the default flavor, Dark uses a dark gray background with light gray foreground color. All modules are the same as in the default flavor, but with a dark palette, loosely based on Google's Material design color palette.

    +

    The dark version of the default flavor, Dark uses a dark gray background with light gray foreground color. All modules are the same as in the default flavor, but with a dark palette, loosely based on Google's Material design color palette.

    Author: Chalarangelo

    Size: 7 KB

    @@ -68,7 +68,7 @@

  • Lite  View on Codepenmini-lite

    <link rel="stylesheet" href="https://gitcdn.link/repo/Chalarangelo/mini.css/master/dist/mini-lite.min.css">
    -

    Lite is a light flavor that uses the default palette (light gray background and gray-black foreground color). It uses the default naming conventions (.primary, .secondary etc.). The grid system has 12 columns and most components use sharp corners without shadows. To make the flavor lighter, button groups, horizontal tables, certain card and progress styles, along with spinner donuts, tooltips, navigation bars, drawers and toasts are not included.

    +

    Lite is a light flavor that uses the default palette (light gray background and gray-black foreground color). It uses the default naming conventions (.primary, .secondary etc.). The grid system has 12 columns and most components use sharp corners without shadows. To make the flavor lighter, button groups, horizontal tables, certain card and progress styles, along with spinner donuts, tooltips, navigation bars, drawers and toasts are not included.

    Author: Chalarangelo

    Size: 5 KB

    @@ -77,7 +77,7 @@

  • Sucroa  View on Codepenmini-sucroa

    <link rel="stylesheet" href="https://gitcdn.link/repo/Chalarangelo/mini.css/master/dist/mini-sucroa.min.css">
    -

    Sucroa is a full flavor that uses a yellow-pink-lilac background color palette with dark purple-black foreground colors. It uses the default naming conventions (.primary, .secondary etc.). The grid system has 12 columns and most components use soft shadows combined with rounded corners. The card module's .dark and .darker classes have been replaced by the .light and .lighter classes respectively. Finally, the .shadowed class is replaced by varying degrees of generic shadows (.shadow-none, .shadow-small, .shadow-medium and .shadow-large).

    +

    Sucroa is a full flavor that uses a yellow-pink-lilac background color palette with dark purple-black foreground colors. It uses the default naming conventions (.primary, .secondary etc.). The grid system has 12 columns and most components use soft shadows combined with rounded corners. The card module's .dark and .darker classes have been replaced by the .light and .lighter classes respectively. Finally, the .shadowed class is replaced by varying degrees of generic shadows (.shadow-none, .shadow-small, .shadow-medium and .shadow-large).

    Author: Angeliki Daskalakis

    Size: 7 KB (loads external fonts)

    @@ -86,22 +86,18 @@

  • Nord  View on Codepenmini-nord

    <link rel="stylesheet" href="https://gitcdn.link/repo/Chalarangelo/mini.css/master/dist/mini-nord.min.css">
    -

    Nord is a full flavor that uses the Nord color palette (arctic, north-bluish color palette). It uses the default naming conventions (.primary, .secondary etc.). The grid system has 12 columns and most components use soft shadows combined with rounded corners. All modules and components that are available in the default flavor are also available in Nord. Finally, the .shadowed class is replaced by varying degrees of generic shadows (.shadow-none, .shadow-small, .shadow-medium and .shadow-large).

    +

    Nord is a full flavor that uses the Nord color palette (arctic, north-bluish color palette). It uses the default naming conventions (.primary, .secondary etc.). The grid system has 12 columns and most components use soft shadows combined with rounded corners. All modules and components that are available in the default flavor are also available in Nord. Finally, the .shadowed class is replaced by varying degrees of generic shadows (.shadow-none, .shadow-small, .shadow-medium and .shadow-large).

    Author: tphecca

    Size: 7 KB

-

If you would rather modify one of the pre-defined flavors or create your own, check out our customization page for instructions.

-
-
-
-
+

If you would rather modify one of the pre-defined flavors or create your own, check out our customization page for instructions.

- + diff --git a/docs/grid.html b/docs/grid.html index 795f552..40cccbb 100644 --- a/docs/grid.html +++ b/docs/grid.html @@ -83,8 +83,8 @@

Grid

-

The grid module provides you with a modern, responsive grid system based on the Flexible Layout Module (commonly known as flexbox). The structure of the grid is simple and logical, allowing you to quickly build your pages from scratch. Setting the layout for a page is easy and will behave the way you want them to on mobile devices and smaller screens.

-

All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.


+

The grid module provides you with a modern, responsive grid system based on the Flexible Layout Module (commonly known as flexbox). The structure of the grid is simple and logical, allowing you to quickly build your pages from scratch. Setting the layout for a page is easy and will behave the way you want them to on mobile devices and smaller screens.

+

All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.


@@ -92,11 +92,11 @@

Quick overview

-

Easy page layout is one of the main advantages of using a CSS framework over writing your own styles. The grid module utilizes the Flexbox Layout to provide you with a modern and responsive layout grid system for all your needs. Rules in the grid module help you create basic fluid containers for your grid and allow you to design layouts that work well on all screen sizes using a simple row and column structure. The grid system contains definitions for both fluid columns that resize according to their siblings and columns with preset sizes on different screen sizes, as well as rules that allow you to offset or move certain columns to the first or last place on the grid's row on different devices, helping you present the page in a different layout without duplicating any content. All of the rules in the module are built around accessibility, so screen readers can easily read you pages.


+

Easy page layout is one of the main advantages of using a CSS framework over writing your own styles. The grid module utilizes the Flexbox Layout to provide you with a modern and responsive layout grid system for all your needs. Rules in the grid module help you create basic fluid containers for your grid and allow you to design layouts that work well on all screen sizes using a simple row and column structure. The grid system contains definitions for both fluid columns that resize according to their siblings and columns with preset sizes on different screen sizes, as well as rules that allow you to offset or move certain columns to the first or last place on the grid's row on different devices, helping you present the page in a different layout without duplicating any content. All of the rules in the module are built around accessibility, so screen readers can easily read you pages.


Quick start

-

To use the grid module, simply include the link to the flavor you are using and start writing your HTML page as usual. One suggestion we will make is to add the following line inside your HTML page's <head> to utilize the viewport meta tag:

+

To use the grid module, simply include the link to the flavor you are using and start writing your HTML page as usual. One suggestion we will make is to add the following line inside your HTML page's <head> to utilize the viewport meta tag:

<meta name="viewport" content="width=device-width, initial-scale=1">

@@ -121,8 +121,8 @@
-

The grid system's basic layout is composed of three components, presented below in the order they should be added to the DOM tree:

-
    +

    The grid system's basic layout is composed of three components, presented below in the order they should be added to the DOM tree:

    +
    1. The grid's .container is the outermost layer of your grid system. It is a fluid container that wraps the flexible grid system inside it.
    2. Inside the container, .rows are added to specify each row of the grid layout. Rows serve to provide you with a simple basis for your layout's columns.
    3. Finally, inside the rows, .col- elements are added for the columns. The columns are a little bit more complex than the container and rows, as they are what makes the layout respond to changes. There are two basic ways to define a column for your layout: @@ -133,7 +133,7 @@

    Sample code

    -

    The sample code is a bit lengthy, so we hid it by default to make it easier for mobile device users to read this page. Click or tap on Show sample code below to see the code sample for this example. Also, the example presented showcases the grid system's syntax for smaller screens, but you can do the same thing for any screen size.


    +

    The sample code is a bit lengthy, so we hid it by default to make it easier for mobile device users to read this page. Click or tap on Show sample code below to see the code sample for this example. Also, the example presented showcases the grid system's syntax for smaller screens, but you can do the same thing for any screen size.


    @@ -191,7 +191,7 @@

    Notes

    -
      +
      • mini.css uses a mobile-first approach in its grid system. This means that specifying a layout for smaller device sizes will apply the same layout on medium-sized and larger screens, so you do not have to rewrite the same layout for all three screen sizes. However, if you want to change the layout on different screen sizes, check the section below.
      • The grid module is compatible with modern browsers, but might not display properly in older browsers.
      • The specific breakpoints for small, medium and large screen sizes are as follows: @@ -214,14 +214,14 @@ <div class="row"> </div> </div> -

        Do: A column can contain a container or a row inside it. The container can also be skipped if inside a column, so you only need to add a row.

        +

        Do: A column can contain a container or a row inside it. The container can also be skipped if inside a column, so you only need to add a row.

    <div class="col-sm">
   <div class="col-sm">
   </div>
 </div>
    -

    Don't: Avoid using columns inside columns without a row wrapping them. Either make the outer column a row in itself or wrap the inside columns in a row.

    +

    Don't: Avoid using columns inside columns without a row wrapping them. Either make the outer column a row in itself or wrap the inside columns in a row.

    <div class="col-sm row">
@@ -230,14 +230,14 @@
   <div class="col-sm-6">
   </div>
 </div>
    -

    Do: A column can also be a row at the same time, if you want to include sub-columns inside it. You can make the same element both a column in its own row and a row for its containing columns. The same idea can be applied for the container. Containers can, however, be omitted, when already inside a grid.

    +

    Do: A column can also be a row at the same time, if you want to include sub-columns inside it. You can make the same element both a column in its own row and a row for its containing columns. The same idea can be applied for the container. Containers can, however, be omitted, when already inside a grid.

    <div class="row">
   <p>Content without columns...</p>
 </div>
    -

    Don't: Avoid using rows with content inside that is not wrapped in columns. Try to use a single .col-sm to wrap the content inside these, otherwise there might be unexpected behavior.

    +

    Don't: Avoid using rows with content inside that is not wrapped in columns. Try to use a single .col-sm to wrap the content inside these, otherwise there might be unexpected behavior.

    <div class="row">
@@ -253,8 +253,7 @@
   <div class="col-sm-12">
   </div>
 </div>
    -

    Do: Mix fluid columns with fixed, if you like. Fluid columns will adapt to the size of the container left for them. You can also use columns with a total size of more than 12, meaning with a total width of over 100%. The remaining content will flow below the rest, allowing you to specify multiple blocks of content inside the same row if you need to.

    -

    +

    Do: Mix fluid columns with fixed, if you like. Fluid columns will adapt to the size of the container left for them. You can also use columns with a total size of more than 12, meaning with a total width of over 100%. The remaining content will flow below the rest, allowing you to specify multiple blocks of content inside the same row if you need to.

    <div class="container">
@@ -270,7 +269,7 @@
   </div>
   <p>Normal paragraph.</p>
 </div>
    -

    Don't: Avoid mixing rows and columns with normal content that is not wrapped on the respective level of the grid system. Always wrap content inside the proper containers (container, row or column) in your grid layout.

    +

    Don't: Avoid mixing rows and columns with normal content that is not wrapped on the respective level of the grid system. Always wrap content inside the proper containers (container, row or column) in your grid layout.

    @@ -301,7 +300,7 @@
-

You can specify different layouts for your pages and web apps, using the grid system's columns. To do this add classes to your columns for different screen sizes, using either the fluid column syntax (.col-SCR_SZ) or the fixed width column syntax (.col-SCR_SZ-COL_WD) or even both.

+

You can specify different layouts for your pages and web apps, using the grid system's columns. To do this add classes to your columns for different screen sizes, using either the fluid column syntax (.col-SCR_SZ) or the fixed width column syntax (.col-SCR_SZ-COL_WD) or even both.

Sample code

<div class="container">
   <div class="row">
@@ -325,7 +324,7 @@

Notes

-
    +
    • Leaving a column's size unspecified for a resolution will use the style applied for the previous largest resolution recursively.
    • Changing the layout for different screen sizes can sometimes require complex content realignment, offsetting and reordering. For these features, check the sections below.
    @@ -337,7 +336,7 @@ <div class="col-sm-12 col-md-6"> </div> </div> -

    Do: You can radically change the layout of your content for different displays. Laying out your content vertically in .col-sm-12s for small devices and then compacting it to .col-md-6s for medium displays is pretty common. If your columns exceed a total size of 12 on some displays, they will wrap accordingly, so do not worry.

    +

    Do: You can radically change the layout of your content for different displays. Laying out your content vertically in .col-sm-12s for small devices and then compacting it to .col-md-6s for medium displays is pretty common. If your columns exceed a total size of 12 on some displays, they will wrap accordingly, so do not worry.

<div class="row">
@@ -348,7 +347,7 @@
   <div class="col-sm-12 col-md-6">
   </div>
 </div>
-

Don't: If you want to place two columns side by side on some displays, but not on others (e.g. placing them vertically on smaller displays, then next to each other on medium-sized or larger displays), place them in one row, not multiple, otherwise you will not achieve the desired effect.

+

Don't: If you want to place two columns side by side on some displays, but not on others (e.g. placing them vertically on smaller displays, then next to each other on medium-sized or larger displays), place them in one row, not multiple, otherwise you will not achieve the desired effect.

<div class="row">
@@ -357,7 +356,7 @@
   <div class="col-sm-6 col-md-8">
   </div>
 </div>
-

Do: Specify only the screen-specific column sizes that you need. You can omit the medium-sized screens' size from a column if its layout on smaller screens is fluid or should be the same as in medium-sized displays. Or, if your larger screen layout is the same as your medium-sized screen layout, you can omit the class for the larger screen.

+

Do: Specify only the screen-specific column sizes that you need. You can omit the medium-sized screens' size from a column if its layout on smaller screens is fluid or should be the same as in medium-sized displays. Or, if your larger screen layout is the same as your medium-sized screen layout, you can omit the class for the larger screen.

<div class="row">
@@ -366,7 +365,7 @@
   <div class="col-lg">
   </div>
 </div>
-

Don't: Never omit the class needed for the smallest screen size you have (.col-sm or .col-sm-COL_WD), otherwise the column's layout on smaller displays might behave unexpectedly. You can, however, omit layout for the other two screen sizes if you want.

+

Don't: Never omit the class needed for the smallest screen size you have (.col-sm or .col-sm-COL_WD), otherwise the column's layout on smaller displays might behave unexpectedly. You can, however, omit layout for the other two screen sizes if you want.

@@ -379,8 +378,8 @@

Predefined layouts

-

Some simple grid layout problems can be solved using predefined layouts. To use a predefined layout, simply add a predefined layout class to a .row element. Predefined classes can be written using one of two syntaxes, similar to normal column classes:

-
    +

    Some simple grid layout problems can be solved using predefined layouts. To use a predefined layout, simply add a predefined layout class to a .row element. Predefined classes can be written using one of two syntaxes, similar to normal column classes:

    +
    • fluid column layouts can be specified using .cols-SCR_SZ, replacing SCR_SZ with one of the available screen size names.
    • fixed width columns layouts can be specified using .col-SCR_SZ-COL_WD, replacing SCR_SZ with one of the available screen size names and COL_WD with a number from 1 to 12 specifying the width of the columns.
    @@ -397,7 +396,7 @@

Notes

-
    +
    • Predefined layouts can be combined with most of the features of the grid system, such as offsets and reordering.
    • If you use a fluid predefined layout, its columns will always be placed in one row.
    • Not specifying a predefined layout for a resolution will use the style applied for the previous largest resolution recursively.
      • @@ -412,7 +411,7 @@ <p>col-sm-12, col-md-6</p> </div> </div> -

      Do: You can add multiple predefined layout classes for different screen sizes, allowing you to build responsive predefined layouts.

      +

      Do: You can add multiple predefined layout classes for different screen sizes, allowing you to build responsive predefined layouts.

<div class="row cols-sm-6">
@@ -423,7 +422,7 @@
     <p>col-sm-6</p>
   </div>
 </div>
-

Don't: Avoid using the normal column classes in conjunction with predefined layouts, as they will most likely not apply and can sometimes cause unexpected behavior.

+

Don't: Avoid using the normal column classes in conjunction with predefined layouts, as they will most likely not apply and can sometimes cause unexpected behavior.

@@ -447,9 +446,9 @@
-

If you want to move columns to the right, you can use the offset classes on your columns. Offset classes use the .col-SCR_SZ-offset-COL_WD syntax, where SCR_SZ is one of the available screen size names (sm, md or lg) and COL_WD a number from 0 to 11 specifying the width of the column's offset. Offsets can also be used in combination with screen-specific layouts and column sizes, providing you with greater flexibility when spacing out your content.

+

If you want to move columns to the right, you can use the offset classes on your columns. Offset classes use the .col-SCR_SZ-offset-COL_WD syntax, where SCR_SZ is one of the available screen size names (sm, md or lg) and COL_WD a number from 0 to 11 specifying the width of the column's offset. Offsets can also be used in combination with screen-specific layouts and column sizes, providing you with greater flexibility when spacing out your content.

Sample code

-

The example presented below showcases the grid system's offsetting syntax for smaller screens, but you can do the same thing for any screen size.

+

The example presented below showcases the grid system's offsetting syntax for smaller screens, but you can do the same thing for any screen size.

<div class="container">
   <div class="row">
     <div class="col-sm-8 col-sm-offset-2">
@@ -477,7 +476,7 @@

Notes

-
    +
    • Columns with offsets and columns without offsets can be mixed for better results. In fact, we strongly suggest you try that.
    • Remember to specify a basic layout and/or screen specific layouts in addition to the offset classes.
    @@ -489,14 +488,14 @@ <div class="col-sm col-md-5 col-lg-4 col-lg-offset-2"> </div> </div> -

    Do: You can specify offset classes when you need them and omit them otherwise. This means that, if you want to offset a column only on a medium-sized or a larger screen, you can just specify the offset for that specific screen. Specifying an offset for a smaller screen, however, will apply it to medium-sized and larger screens as well, medium-sized screen offsets will apply to larger screens etc. similar to how the layout system works.

    +

    Do: You can specify offset classes when you need them and omit them otherwise. This means that, if you want to offset a column only on a medium-sized or a larger screen, you can just specify the offset for that specific screen. Specifying an offset for a smaller screen, however, will apply it to medium-sized and larger screens as well, medium-sized screen offsets will apply to larger screens etc. similar to how the layout system works.

<div class="row">
   <div class="col-sm col-md-10 col-offset-1 col-lg col-lg-offset-0">
   </div>
 </div>
-

Do: To remove a previously applied offset from a column (i.e. one applied from the layout from a smaller screen size) or to make sure no offsets are active on a column, you can use the .col-SCR_SZ-offset-0 class, replacing SCR_SZ with the desired screen size, effectively resetting all offsets.

+

Do: To remove a previously applied offset from a column (i.e. one applied from the layout from a smaller screen size) or to make sure no offsets are active on a column, you can use the .col-SCR_SZ-offset-0 class, replacing SCR_SZ with the desired screen size, effectively resetting all offsets.

@@ -530,7 +529,7 @@
-

Additionally, if you want to reorder your columns, you can do that to some extent using the .col-SCR_SZ-first, .col-SCR_SZ-last and .col-SCR_SZ-normal classes to your columns, replacing SCR_SZ with one of the available screen size names (sm, md or lg). These classes will change the ordering of your columns appropriately to allow you to move content around any way you want (e.g. moving a navigation sidebar from the left of the content on larger displays to the end of the content on smaller displays).

+

Additionally, if you want to reorder your columns, you can do that to some extent using the .col-SCR_SZ-first, .col-SCR_SZ-last and .col-SCR_SZ-normal classes to your columns, replacing SCR_SZ with one of the available screen size names (sm, md or lg). These classes will change the ordering of your columns appropriately to allow you to move content around any way you want (e.g. moving a navigation sidebar from the left of the content on larger displays to the end of the content on smaller displays).

Sample code

<div class="container">
   <div class="row">
@@ -546,7 +545,7 @@

Notes

-
    +
    • Columns are ordered by default in order of appearance. You should only apply column reordering classes to the columns you want to reorder on the screen-specific layouts you need them.
    • Remember to specify a basic layout and/or screen specific layouts in addition to the column reordering classes.
    • Column reordering is applied from smaller to larger screens, similar to how column layout and offsetting work.
      • @@ -561,7 +560,7 @@ <div class="col-sm"> </div> </div> -

      Do: You can use multiple .col-SCR_SZ-firsts and .col-SCR_SZ-lasts, replacing SCR_SZ with the desired screen size, in the same row for the same screen size. If you specify more than one column to be first or last, the columns with the same order will be placed at the beggining or end of the row and the order between them will be determined based on their order of appearance in the DOM tree afterwards.

      +

      Do: You can use multiple .col-SCR_SZ-firsts and .col-SCR_SZ-lasts, replacing SCR_SZ with the desired screen size, in the same row for the same screen size. If you specify more than one column to be first or last, the columns with the same order will be placed at the beggining or end of the row and the order between them will be determined based on their order of appearance in the DOM tree afterwards.

<div class="row">
@@ -570,7 +569,7 @@
   <div class="col-sm">
   </div>
 </div>
-

Do: To remove a previously applied reorder from a column (i.e. one applied from the layout from a smaller screen size) or to make sure no reordering is active on a column, you can use the .col-SCR_SZ-normal class, replacing SCR_SZ with the desired screen size, effectively resetting all reorders. You do not, however, need to add this class to all other columns or use it when there are no reorders applied.

+

Do: To remove a previously applied reorder from a column (i.e. one applied from the layout from a smaller screen size) or to make sure no reordering is active on a column, you can use the .col-SCR_SZ-normal class, replacing SCR_SZ with the desired screen size, effectively resetting all reorders. You do not, however, need to add this class to all other columns or use it when there are no reorders applied.

@@ -597,7 +596,7 @@
-

Last, but not least, you can use the grid system's classes to create a media object in one of many ways, based on your needs. The simplest way to implement a media object is using two columns, one for the media (i.e. <img>) and one for the textual content next to the media.

+

Last, but not least, you can use the grid system's classes to create a media object in one of many ways, based on your needs. The simplest way to implement a media object is using two columns, one for the media (i.e. <img>) and one for the textual content next to the media.

Sample code

<div class="row">
   <div class="col-sm-1">
@@ -627,7 +626,7 @@
     <p>Media object content...</p>
   </div>
 </div>
-

Do: You can make your media object responsive, by adding screen-specific layout classes to its columns.

+

Do: You can make your media object responsive, by adding screen-specific layout classes to its columns.

<div class="row">
@@ -639,7 +638,7 @@
     <p>Media object content...</p>
   </div>
 </div>
-

Do: You can align the media object's content to the left of the image (instead of the other way round), using the .col-SCR_SZ-normal class, replacing SCR_SZ with the desired screen size.

+

Do: You can align the media object's content to the left of the image (instead of the other way round), using the .col-SCR_SZ-normal class, replacing SCR_SZ with the desired screen size.

<div class="row">
@@ -665,7 +664,7 @@
   </div>
 </div>
-

Do: Media objects can be easily nested. You can use .row elements in the content column of the media object to make everything align perfectly.

+

Do: Media objects can be easily nested. You can use .row elements in the content column of the media object to make everything align perfectly.

<div class="row">
@@ -675,7 +674,7 @@
     <p>Media object content...</p>
   </div>
 </div>
-

Don't: Do not apply a column class directly to the media element (e.g.<img>) or the content of the media object, as this can cause problems with certain elements. Wrap your media objects columns in <div> elements and apply the grid classes to them, instead.

+

Don't: Do not apply a column class directly to the media element (e.g.<img>) or the content of the media object, as this can cause problems with certain elements. Wrap your media objects columns in <div> elements and apply the grid classes to them, instead.

@@ -684,10 +683,10 @@
-

If you want to learn more about mini.css's modules, go back to the modules page and choose another module to see its documentation.

+

If you want to learn more about mini.css's modules, go back to the modules page and choose another module to see its documentation.

- + diff --git a/docs/index.html b/docs/index.html index 422da0a..8240e7d 100644 --- a/docs/index.html +++ b/docs/index.html @@ -107,7 +107,7 @@

Setup & usage

-

mini.css is published in npm, yarn and bower, so you can easily download it, using your preferred package manager:

+

mini.css is published in npm, yarn and bower, so you can easily download it, using your preferred package manager:

npm install mini.css
yarn add mini.css
@@ -115,10 +115,10 @@

After downloading mini.css, pick a Flavor and use it for your project.


-

Alternatively, you can use either GitCDN or RawGit to import the default flavor of mini.css. Simply add one of the following references inside your HTML page's <head> tag:

+

Alternatively, you can use either GitCDN or RawGit to import the default flavor of mini.css. Simply add one of the following references inside your HTML page's <head> tag:

<link rel="stylesheet" href="https://gitcdn.link/repo/Chalarangelo/mini.css/master/dist/mini-default.min.css">
<link rel="stylesheet" href="https://cdn.rawgit.com/Chalarangelo/mini.css/v2.2.0/dist/mini-default.min.css">

-

Finally, you can find mini.css on cdnjs, which you can use to include it in your projects.


+

Finally, you can find mini.css on cdnjs, which you can use to include it in your projects.


@@ -126,14 +126,14 @@

Browser support

-
edge

 Edge12

+
edge

  Edge12

firefox

 Firefox28

chrome

 Chrome26

safari

 Safari7.1

opera

 Opera17

android

 Android4.4

-

 Due to the way mini.css 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. On a side note, remember that some mobile browsers like Opera Mini, IE Mobile and UC Browser for Android are officially supported, but some features may not be displayed properly or behave as expected due to the browsers themselves.

+

 Due to the way mini.css is designed, 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 such as Internet Explorer will display a less feature-rich and modern website. On a side note, remember that some mobile browsers like Opera Mini, IE Mobile and UC Browser for Android are officially supported, but some features may not be displayed properly or behave as expected due to the browsers themselves.

@@ -142,10 +142,10 @@

Take a couple of minutes to explore what makes mini.css different from all those other CSS frameworks and UI toolkits.


Why should I use mini.css?

-

mini.css is a lot lighter than a lot of other full-featured CSS frameworks (e.g. Bootstrap, Semantic UI), but it is not a micro framework (e.g. Milligram, Pure.CSS). Instead, mini.css blurs the line between full-featured and micro frameworks by providing lots of modules and components in a very small file. All the things you expect to find in a CSS framework, such as grids, styling for common elements and typography, along with some more complex components such as tabs or cards are all present in mini.css.

+

mini.css is a lot lighter than a lot of other full-featured CSS frameworks (e.g. Bootstrap, Semantic UI), but it is not a micro framework (e.g. Milligram, Pure.CSS). Instead, mini.css blurs the line between full-featured and micro frameworks by providing lots of modules and components in a very small file. All the things you expect to find in a CSS framework, such as grids, styling for common elements and typography, along with some more complex components such as tabs or cards are all present in mini.css.


What exactly does mini.css provide?

-

Many CSS frameworks utilize modules to deliver more components and features, without making it necessary for all developers to include them. mini.css provides a handful of very powerful modules that can do many different things. This way, developers only have to learn a few different HTML structures and patterns, while having the ability to build a lot of interesting things with them. You can see an overview of the modules below:

+

Many CSS frameworks utilize modules to deliver more components and features, without making it necessary for all developers to include them. mini.css provides a handful of very powerful modules that can do many different things. This way, developers only have to learn a few different HTML structures and patterns, while having the ability to build a lot of interesting things with them. You can see an overview of the modules below:

  • Core - Basic reset and fix rules, based on Normalize.css v5.0.0, typography and common textual element styling
  • Grid - Powerful, responsive grid system based on the Flexible Layout Module (commonly known as flexbox)
    • @@ -159,7 +159,14 @@
  • Utility - Utilities, visibility helper classes, responsive sizing and breadcrumbs

How do I customize mini.css?

-

mini.css allows you to easily customize your designs, using Flavors, pre-built color and style variants of the framework. The functionality is the same, but many things like color palettes, spacing and fonts can be easily changed by the community. Apart from that, you can easily build your own flavor by tweaking variables and using mixins, as explained in depth in the customization section.


+

mini.css allows you to easily customize your designs, using Flavors, pre-built color and style variants of the framework. The functionality is the same, but many things like color palettes, spacing and fonts can be easily changed by the community. Apart from that, you can easily build your own flavor by tweaking variables and using mixins, as explained in depth in the customization section.


+
+
+
+

Support mini.css!

+

If you like mini.css, remember that you can show your support by starring it on Github.
It means a lot to us and it only takes a couple of seconds!

+ Star mini.css +
@@ -178,6 +185,6 @@
- + diff --git a/docs/input_control.html b/docs/input_control.html index 9d3eed8..eb680c2 100644 --- a/docs/input_control.html +++ b/docs/input_control.html @@ -83,8 +83,8 @@

Input Control

-

The input_control module contains rules that affect forms, input elements, buttons, checkboxes and radio buttons. All of these elements' styles are predefined, allowing you to create modern, responsive forms quickly. Layout alternatives are also provided if you want your forms to look a certain way.

-

All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.


+

The input_control module contains rules that affect forms, input elements, buttons, checkboxes and radio buttons. All of these elements' styles are predefined, allowing you to create modern, responsive forms quickly. Layout alternatives are also provided if you want your forms to look a certain way.

+

All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.


@@ -92,11 +92,11 @@

Quick overview

-

The presentation of forms, input fields, buttons and other interactive elements is always very important for any website or app. The input_control module provides you with much needed styling improvements for all of these elements, while keeping everything simple to use and understand, as well as combine with the other modules. Forms and input elements have a clean, modern design, while some elements like checkoxes and radio buttons get a much needed facelift. Buttons have also been stylized to look the same in all browsers, while keeping their design clean and allowing for a few color and size variants. Grouping inputs and labels or buttons is also part of this module and, as always, responsiveness is an important feature. Finally, all of the components are accessible, with a few minor caveats, that are discussed in their respective section in this page.


+

The presentation of forms, input fields, buttons and other interactive elements is always very important for any website or app. The input_control module provides you with much needed styling improvements for all of these elements, while keeping everything simple to use and understand, as well as combine with the other modules. Forms and input elements have a clean, modern design, while some elements like checkoxes and radio buttons get a much needed facelift. Buttons have also been stylized to look the same in all browsers, while keeping their design clean and allowing for a few color and size variants. Grouping inputs and labels or buttons is also part of this module and, as always, responsiveness is an important feature. Finally, all of the components are accessible, with a few minor caveats, that are discussed in their respective section in this page.


Quick start

-

To use the input_control module, simply include the link to the flavor you are using and start writing your HTML page as usual. One suggestion we will make is to add the following line inside your HTML page's <head> to utilize the viewport meta tag:

+

To use the input_control module, simply include the link to the flavor you are using and start writing your HTML page as usual. One suggestion we will make is to add the following line inside your HTML page's <head> to utilize the viewport meta tag:

<meta name="viewport" content="width=device-width, initial-scale=1">

@@ -161,8 +161,8 @@
-

Forms are structured the same way you would structure a normal form in HTML5. Simply create a root <form> element and add your <input> elements inside. Link them to <label> elements for ease of acces and you are pretty much set. We highly recommend using the <fieldset> and <legend> elements to annotate your forms as well, but you can skip them if you wish.

-

Forms are inline by default. Use the .input-group class on a <div> wrapping inside it an <input> and <label> pair to make sure they always display together in one line. You can make your .input-groups respond to viewport changes, by adding the .fluid class to them. Finally, if you want to create aligned forms with a preset layout, you can utilize the grid module's rows and columns.

+

Forms are structured the same way you would structure a normal form in HTML5. Simply create a root <form> element and add your <input> elements inside. Link them to <label> elements for ease of acces and you are pretty much set. We highly recommend using the <fieldset> and <legend> elements to annotate your forms as well, but you can skip them if you wish.

+

Forms are inline by default. Use the .input-group class on a <div> wrapping inside it an <input> and <label> pair to make sure they always display together in one line. You can make your .input-groups respond to viewport changes, by adding the .fluid class to them. Finally, if you want to create aligned forms with a preset layout, you can utilize the grid module's rows and columns.

Sample code

<form>
   <fieldset>
@@ -181,7 +181,7 @@

Notes

-
    +
    • Using the <fieldset> and <legend> elements is highly recommended for a better presentational effect. Using these elements is a matter of personal preference, however try to keep your forms consistent (i.e. either use them in all forms or no forms as to not confuse users).
    • Some <input> elements, such as date & time, color and range types, are not supported and, as a result, do not have a default style defined for them. You can define said styles manually if you need to use them in your website or app.
    • Checkboxes and radio buttons are not stylized the same way as most of the other elements, nor do they follow the exact same stucture for layout. Please refer to the next section for information on how to use those.
      • @@ -210,7 +210,7 @@ </div> </fieldset> </form> -

      Do: You can use .row and .col-SCR_SZ or .col-SCR_SZ-COL_WD (replacing SCR_SZ with one of the available screen size names (sm for smaller screens, md for medium-sized screens or lg for larger screens and COL_WD with a number from 1 to 12 specifying the width of the column) to set specific layouts for your aligned forms. You can also use the same column classes to make them responsive for different screen sizes.

      +

      Do: You can use .row and .col-SCR_SZ or .col-SCR_SZ-COL_WD (replacing SCR_SZ with one of the available screen size names (sm for smaller screens, md for medium-sized screens or lg for larger screens and COL_WD with a number from 1 to 12 specifying the width of the column) to set specific layouts for your aligned forms. You can also use the same column classes to make them responsive for different screen sizes.

<form>
@@ -230,7 +230,7 @@
     </div>
   </fieldset>
 </form>
-

Do: Apart from using .row and .col-SCR_SZ or .col-SCR_SZ-COL_WD for responsiveness, you can also use other classes from the grid module such as the offset classes to make your form layouts more interesting.

+

Do: Apart from using .row and .col-SCR_SZ or .col-SCR_SZ-COL_WD for responsiveness, you can also use other classes from the grid module such as the offset classes to make your form layouts more interesting.

<style>
@@ -251,7 +251,7 @@
     </div>
   </fieldset>
 </form>
-

Do: When creating aligned forms using the grid module's classes, labels might be off-center vertically compared to their inline counterparts. Use a simple styling for their parent .row element, if you want to adjust their vertical alignment.

+

Do: When creating aligned forms using the grid module's classes, labels might be off-center vertically compared to their inline counterparts. Use a simple styling for their parent .row element, if you want to adjust their vertical alignment.

<form>
@@ -267,7 +267,7 @@
     </div>
   </fieldset>
 </form>
-

Don't: Avoid using the .input-group class when creating aligned forms. This might cause unexpected behavior.

+

Don't: Avoid using the .input-group class when creating aligned forms. This might cause unexpected behavior.

@@ -295,7 +295,7 @@
-

Checkboxes and radio buttons come pre-styled, using the checkbox hack, while remaining fully accessible. To create a checkbox or radio button, start using a <div> that implements the .input-group class, and then add an <input> of the proper type inside it ("checkbox" or "radio"), followed immediately by a <label> linking to it. Remember to add tabindex="0" to your <input>, so that it will register properly for screen readers.

+

Checkboxes and radio buttons come pre-styled, using the checkbox hack, while remaining fully accessible. To create a checkbox or radio button, start using a <div> that implements the .input-group class, and then add an <input> of the proper type inside it ("checkbox" or "radio"), followed immediately by a <label> linking to it. Remember to add tabindex="0" to your <input>, so that it will register properly for screen readers.

Sample code

<div class="input-group">
   <input type="checkbox" id="check1" tabindex="0">
@@ -310,7 +310,7 @@

Notes

-
    +
    • Checkboxes and radio buttons are fully accessible. However, if not provided with a label, they are not visible to users, but only to screen readers.
    @@ -321,26 +321,26 @@ <input type="radio" id="rad2" tabindex="0" name="radio-group-1"> <label for="rad2">Value 2</label> </div> -

    Do: You can add multiple radio buttons inside one .input-group, as long as they follow the syntax shown above. In fact, we strongly recommend grouping controls that are relevant to each other in this manner.

    +

    Do: You can add multiple radio buttons inside one .input-group, as long as they follow the syntax shown above. In fact, we strongly recommend grouping controls that are relevant to each other in this manner.

    <input type="checkbox" id="check1" tabindex="0">
 <label for="check1">Checkbox</label>
    -

    Don't: Always use an .input-group for your checkboxes and radio buttons. Not doing so will cause the checkbox or radio button to not display properly.

    +

    Don't: Always use an .input-group for your checkboxes and radio buttons. Not doing so will cause the checkbox or radio button to not display properly.

    <div class="input-group">
   <input type="checkbox" id="check1"
   <label for="check1">Checkbox</label>
 </div>
    -

    Don't: Remember to add tabindex="0" to all your checkboxes and radio buttons to make them accessible.

    +

    Don't: Remember to add tabindex="0" to all your checkboxes and radio buttons to make them accessible.

    <div class="input-group">
   <label for="check1">Checkbox</label>
   <input type="checkbox" id="check1" tabindex="0">
 </div>
    -

    Don't: The structure of checkboxes and radio buttons is very strict, meaning that the <label> should always be after the <input> and never before, otherwise the checkbox or radio button will not display properly.

    +

    Don't: The structure of checkboxes and radio buttons is very strict, meaning that the <label> should always be after the <input> and never before, otherwise the checkbox or radio button will not display properly.

    <div class="input-group">
@@ -349,13 +349,13 @@
   <label for="rad2">Value 2</label>
   <label for="rad1">Value 1</label>
 </div>
    -

    Don't: When using multiple radio buttons inside an .input-group, remember to use the usual structure of the radio button component for each radio button (i.e. the <input> and <label>). Not doing so will cause the radio buttons to not display properly.

    +

    Don't: When using multiple radio buttons inside an .input-group, remember to use the usual structure of the radio button component for each radio button (i.e. the <input> and <label>). Not doing so will cause the radio buttons to not display properly.

    <div class="input-group">
   <input type="checkbox" id="check1" tabindex="0">
 </div>
    -

    Don't: Never leave a checkbox or radio button without a <label>. The <label> is essential to properly display the checkbox or radio button.

    +

    Don't: Never leave a checkbox or radio button without a <label>. The <label> is essential to properly display the checkbox or radio button.

@@ -380,9 +380,9 @@
-

All button types have been stylized by default, while maintaining accessiblity. Simply add any <button> or an <input> with a button type (i.e. "button", "submit" or "reset") and they will be styled accordingly. You can also use the .button class or the role="button" attribute for links, labels and other elements of your choice to make them look like buttons.

-

Color variants are available in the form of the .primary, .secondary, .tertiary and .inverse classes. Size variants are available as well in the form of .small and .large classes.

-

Finally, you can create responsive groups of buttons by wrapping them inside a <div> with the .button-group class.

+

All button types have been stylized by default, while maintaining accessiblity. Simply add any <button> or an <input> with a button type (i.e. "button", "submit" or "reset") and they will be styled accordingly. You can also use the .button class or the role="button" attribute for links, labels and other elements of your choice to make them look like buttons.

+

Color variants are available in the form of the .primary, .secondary, .tertiary and .inverse classes. Size variants are available as well in the form of .small and .large classes.

+

Finally, you can create responsive groups of buttons by wrapping them inside a <div> with the .button-group class.

Sample code

<button>Default button</button>
 <input type="button" class="primary" value="Primary button">
@@ -406,7 +406,7 @@

Notes

-
    +
    • If you want more color or size variants for your buttons, check out the customization page.
    • The .button-group component is compatible with modern browsers, but might not display properly in older browsers.
    • .button-groups will display as a horizontal container with all their buttons in one row on medium-sized and larger displays, however they will collapse into a column view for smaller displays.
      • @@ -414,13 +414,13 @@ 
      <button class="inverse small">Small inverse button</button>
      -

      Do: You can mix and match button color and size variants to achieve the desired effect.

      +

      Do: You can mix and match button color and size variants to achieve the desired effect.

      <button class="secondary inverse">Problematic button</button>
 <!-- or -->
 <button class="small large">Problematic button</button>
      -

      Don't: Avoid mixing two or more button color or size variants, as these combinations might result in unexpected behavior.

      +

      Don't: Avoid mixing two or more button color or size variants, as these combinations might result in unexpected behavior.

      <div class="button-group">
@@ -428,7 +428,7 @@
   <input type="reset" class="secondary" value="Secondary button">
   <label class="button inverse">Label button</label>
 </div>
      -

      Do: You can use button color variants inside the same .button-group. You can also use any component styled like a button inside a .button-group.

      +

      Do: You can use button color variants inside the same .button-group. You can also use any component styled like a button inside a .button-group.

      <div class="button-group">
@@ -436,7 +436,7 @@
   <button>Button</button>
   <button class="small">Button</button>
 </div>
      -

      Don't: Avoid using button size variants inside a .button-group, as this might result in unexpected behavior.

      +

      Don't: Avoid using button size variants inside a .button-group, as this might result in unexpected behavior.

@@ -457,7 +457,7 @@
-

File upload buttons are commonly a sore spot in CSS frameworks. We try to remedy this problem by hiding the <input type="file">, while maintaining accessibility and using a linked <label> of the .button class to display it in a modern way.

+

File upload buttons are commonly a sore spot in CSS frameworks. We try to remedy this problem by hiding the <input type="file">, while maintaining accessibility and using a linked <label> of the .button class to display it in a modern way.

Sample code

<input type="file" id="file-input">
 <label for="file-input" class="button">Upload file...</label>
@@ -465,7 +465,7 @@

Notes

-
    +
    • The icon displayed in the example above is not part of the button styling.
    • File upload buttons do not change their text to the name of the file after the user has selected a file to upload. You can, however, add this functionality using a few lines of Javascript.
    • File upload buttons cannot be focused (i.e. have a :focus state) using the keyboard and this applies to linked labels, too. You can use Javascript to add this functionality, if you wish.
      • @@ -476,7 +476,7 @@ <input type="file" id="file-input"> <label for="file-input" class="button">Upload file...</label> </div> -

      Do: You can use an .input-group to wrap the file upload <input> and its linked <label>, if you wish.

      +

      Do: You can use an .input-group to wrap the file upload <input> and its linked <label>, if you wish.

@@ -485,10 +485,10 @@
-

If you want to learn more about mini.css's modules, go back to the modules page and choose another module to see its documentation.

+

If you want to learn more about mini.css's modules, go back to the modules page and choose another module to see its documentation.

- + diff --git a/docs/modules.html b/docs/modules.html index 5af9fe7..eb40038 100644 --- a/docs/modules.html +++ b/docs/modules.html @@ -76,14 +76,14 @@

Modules

-

mini.css uses modules as its base building blocks. Each module contains one or more components that affect the same part of the user experience. Below you can see a quick overview of all the modules that compose mini.css.


+

mini.css uses modules as its base building blocks. Each module contains one or more components that affect the same part of the user experience. Below you can see a quick overview of all the modules that compose mini.css.


 Core

-

The core module contains basic reset and fix rules, based on Normalize.css v5.0.0, along with lots of custom typography rules. Most textual HTML5 elements are styled by this module, so you can start writing your pages immediately without worrying about font families, weights, sizes, line heights, paddings and the like. More specifically, the core module contains:

    +

    The core module contains basic reset and fix rules, based on Normalize.css v5.0.0, along with lots of custom typography rules. Most textual HTML5 elements are styled by this module, so you can start writing your pages immediately without worrying about font families, weights, sizes, line heights, paddings and the like. More specifically, the core module contains:

    • General typography rules
    • Styling for headings
    • Styling for common textual elements
      • @@ -95,7 +95,7 @@

       Grid

      -

      The grid module provides you with a modern, responsive grid system based on the Flexible Layout Module (commonly known as flexbox). The structure of the grid is simple and logical, allowing you to quickly build your pages from scratch. Setting the layout for a page is easy and will behave the way you want them to on mobile devices and smaller screens. More specifically, the grid module contains:

        +

        The grid module provides you with a modern, responsive grid system based on the Flexible Layout Module (commonly known as flexbox). The structure of the grid is simple and logical, allowing you to quickly build your pages from scratch. Setting the layout for a page is easy and will behave the way you want them to on mobile devices and smaller screens. More specifically, the grid module contains:

        • Containers, rows and columns for layout
        • Classes for defining screen-specific layouts
        • Classes for predefined layouts
          • @@ -110,7 +110,7 @@

           Input Control

          -

          The input_control module contains rules that affect forms, input elements, buttons, checkboxes and radio buttons. All of these elements's styles are predefined, allowing you to create modern, responsive forms quickly. Layout alternatives are also provided if you want your forms to look a certain way. More specifically, the input_control module contains:

            +

            The input_control module contains rules that affect forms, input elements, buttons, checkboxes and radio buttons. All of these elements's styles are predefined, allowing you to create modern, responsive forms quickly. Layout alternatives are also provided if you want your forms to look a certain way. More specifically, the input_control module contains:

            • Styling for forms and input elements
            • Styling for checkboxes and radio buttons
            • Styling and groupping classes for buttons
              • @@ -121,7 +121,7 @@

               Navigation

              -

              The navigation module seeks to remedy the problems of vertical and horizontal navigation design paradigms, by combining the two for a better presentational effect. HTML5 navigational elements are at the heart of the module, allowing you to quickly build your navigation menus. More specifically, the navigation module contains:

                +

                The navigation module seeks to remedy the problems of vertical and horizontal navigation design paradigms, by combining the two for a better presentational effect. HTML5 navigational elements are at the heart of the module, allowing you to quickly build your navigation menus. More specifically, the navigation module contains:

                • Styling for headers, logos and header links
                • Styling for navigation bars
                • Classes for creating responsive drawers
                  • @@ -135,7 +135,7 @@

                   Table

                  -

                  The table module provides styling and responsiveness for tables. Simple rules and accessible design paradigms have been used to make creating tables quick and easy. Large tables will collapse to cards when on smaller devices or, if you don't want that, they can be locked into their default, desktop view. More specifically, the table module contains:

                    +

                    The table module provides styling and responsiveness for tables. Simple rules and accessible design paradigms have been used to make creating tables quick and easy. Large tables will collapse to cards when on smaller devices or, if you don't want that, they can be locked into their default, desktop view. More specifically, the table module contains:

                    • Styling for tables and built-in responsiveness
                    • Classes for creating horizontal tables
                    • Classes for creating table variants and matrices
                      • @@ -145,7 +145,7 @@

                       Card

                      -

                      The card module provides you with modern, responsive, general-purpose containers for your page's contents. They are very easy to use and their structure is really simple and versatile. Layouts will respond to smaller screens, realigning the cards in a manner that makes your page mobile-friendly. More specifically, the card module contains:

                        +

                        The card module provides you with modern, responsive, general-purpose containers for your page's contents. They are very easy to use and their structure is really simple and versatile. Layouts will respond to smaller screens, realigning the cards in a manner that makes your page mobile-friendly. More specifically, the card module contains:

                        • Classes for creating card-based layouts
                        • Classes for creating card sections and adding media
                        • Classes for creating card variants and making cards fluid
                          • @@ -158,7 +158,7 @@

                           Tab

                          -

                          The tab module aims to combine multiple components and design paradigms, like collapses, accordions, carousels and tabs, into one general-purpose component. Tabs are very simple in structure, responsive on mobile and they allow for layout customization so that you can turn them into accordions or collapses whenever you want. More specifically, the tab module contains:

                            +

                            The tab module aims to combine multiple components and design paradigms, like collapses, accordions, carousels and tabs, into one general-purpose component. Tabs are very simple in structure, responsive on mobile and they allow for layout customization so that you can turn them into accordions or collapses whenever you want. More specifically, the tab module contains:

                            See more @@ -167,7 +167,7 @@

                             Contextual

                            -

                            The contextual module provides you with simple tags, marks and highlights for your pages, allowing you to easily emphasize parts of your text. Contextual toasts and tooltips are also provided, aiming to help deliver important information to users. HTML5 elements and simple rules are used in order to make important messages and pieces of content stand out easily. More specifically, the contextual module contains:

                              +

                              The contextual module provides you with simple tags, marks and highlights for your pages, allowing you to easily emphasize parts of your text. Contextual toasts and tooltips are also provided, aiming to help deliver important information to users. HTML5 elements and simple rules are used in order to make important messages and pieces of content stand out easily. More specifically, the contextual module contains:

                              • Styling for highlighted text
                              • Classes for creating toast messages
                              • Classes for creating hover-over tooltips
                                • @@ -179,7 +179,7 @@

                                 Progress

                                -

                                The progress module gives you full control over the presentation of progress and loading on your pages. Apart from progress bars and color variants for them, spinner elements are provided to help communicate that something is loading. More specifically, the progress module contains:

                                  +

                                  The progress module gives you full control over the presentation of progress and loading on your pages. Apart from progress bars and color variants for them, spinner elements are provided to help communicate that something is loading. More specifically, the progress module contains:

                                  - + diff --git a/docs/navigation.html b/docs/navigation.html index ec84797..8bf8971 100644 --- a/docs/navigation.html +++ b/docs/navigation.html @@ -85,8 +85,8 @@
                                  @@ -94,11 +94,11 @@

                                  Quick overview

                                  -

                                  Menus and navigation are some of the most important elements for any website or web app and their design and ease-of-use are key factors that can determine a page's bounce rates. The navigation module takes a step back from the complicated menu and navigation design paradigms of the modern web, using HTML5 elements (i.e. header, nav and footer) for basic navigation, while providing fully accessibility for screen readers. Apart from the simple horizontal navigation (headers) and vertical menus (sidebars), we opted to add a responsive slide-in drawer menu that works well with any page layout. Finally, footers are also part of the navigation module, as they can often provide the user with useful information and/or links that are very important to enhancing their experience.


                                  +

                                  Menus and navigation are some of the most important elements for any website or web app and their design and ease-of-use are key factors that can determine a page's bounce rates. The navigation module takes a step back from the complicated menu and navigation design paradigms of the modern web, using HTML5 elements (i.e. header, nav and footer) for basic navigation, while providing fully accessibility for screen readers. Apart from the simple horizontal navigation (headers) and vertical menus (sidebars), we opted to add a responsive slide-in drawer menu that works well with any page layout. Finally, footers are also part of the navigation module, as they can often provide the user with useful information and/or links that are very important to enhancing their experience.


                                  Quick start

                                  -

                                  To use the navigation module, simply include the link to the flavor you are using and start writing your HTML page as usual. One suggestion we will make is to add the following line inside your HTML page's <head> to utilize the viewport meta tag:

                                  +

                                  To use the navigation module, simply include the link to the flavor you are using and start writing your HTML page as usual. One suggestion we will make is to add the following line inside your HTML page's <head> to utilize the viewport meta tag:

                                  <meta name="viewport" content="width=device-width, initial-scale=1">

                                  @@ -119,7 +119,7 @@
                                -

                                The <header> HTML element is used for a page's top horizontal navigation menu. It can contain a unique .logo element as its first child (this structure is not mandatory, but still recommended as a best practice), which can be either text (with or without a link) or an image. The rest of the elements inside the <header> must be button elements (i.e. <button>, <input type="button">, role="button" or .button) in order to be styled properly. Textual separators between those can be added using <span> elements.

                                +

                                The <header> HTML element is used for a page's top horizontal navigation menu. It can contain a unique .logo element as its first child (this structure is not mandatory, but still recommended as a best practice), which can be either text (with or without a link) or an image. The rest of the elements inside the <header> must be button elements (i.e. <button>, <input type="button">, role="button" or .button) in order to be styled properly. Textual separators between those can be added using <span> elements.

                                Sample code

                                <header>
   <a href="#" class="logo">Logo</a>
@@ -133,7 +133,7 @@

                                Notes

                                -
                                  +
                                  • The <header> element is partially responsive on smaller screen devices. More specifically, when the content inside it exceeds the width of the viewport (ie. overflows to the right), users will be able to scroll horizontally in order to see the rest of the menu.
                                  • The <header> element does not display as fixed by default. You can, however, alter this CSS property manually, if you so desire.
                                  @@ -145,7 +145,7 @@ <a href="#" class="button">Action 2</a> <label class="button">Action 3</label> </header> -

                                  Do: You can mix different elements styled like buttons inside a <header> element. In fact, we strongly recommend doing so, if you need to.

                                  +

                                  Do: You can mix different elements styled like buttons inside a <header> element. In fact, we strongly recommend doing so, if you need to.

                                <header>
@@ -156,7 +156,7 @@
   <a href="#" class="logo">Logo</a>
   <a href="#">Link</a>
 </header>
                                -

                                Don't: The .logo element should not be a <button> element, have the .button class or the role="button" attribute. On the other hand, links and labels in the <header> should not be without a .button class or a role="button" attribute. Ignoring this rule might cause unexpected behavior.

                                +

                                Don't: The .logo element should not be a <button> element, have the .button class or the role="button" attribute. On the other hand, links and labels in the <header> should not be without a .button class or a role="button" attribute. Ignoring this rule might cause unexpected behavior.

                                @@ -180,7 +180,7 @@
                            -

                            To add vertical navigation to your websites, use the <nav> HTML element. Adding links is pretty simple, just use <a> elements, no lists or anything else required. In order to add subcategories to your vertical navigation, use any normal textual element as the title of the subcategory and follow it with its links as normal, adding the .sublink-1 class to them. Similarly, you can create a subcategory with a depth of 2, using a similar structure and the .sublink-2 class.

                            +

                            To add vertical navigation to your websites, use the <nav> HTML element. Adding links is pretty simple, just use <a> elements, no lists or anything else required. In order to add subcategories to your vertical navigation, use any normal textual element as the title of the subcategory and follow it with its links as normal, adding the .sublink-1 class to them. Similarly, you can create a subcategory with a depth of 2, using a similar structure and the .sublink-2 class.

                            Sample code

                            <nav>
   <a href="#">Home</a>
@@ -198,7 +198,7 @@

                            Notes

                            -
                              +
                              • Subcategories and their links support a depth of 2 by default. If, however, you need more than that, we recommend you check the customization page for instructions on how to add more depth to the vertical navigation.
                              • We strongly suggest you do not add irrelevant things inside your <nav> element, like images or text that are not part of the navigation menu.
                              @@ -209,7 +209,7 @@ <!-- navigation content --> </nav> </div> -

                              Do: We strongly recommend using the <nav> element in combination with the grid module to make your layouts more responsive. For example, you could make your sidebar appear on the left side of your content in medium-sized and larger screens, but move to the very bottom of your content on smaller screens.

                              +

                              Do: We strongly recommend using the <nav> element in combination with the grid module to make your layouts more responsive. For example, you could make your sidebar appear on the left side of your content in medium-sized and larger screens, but move to the very bottom of your content on smaller screens.

                            @@ -234,15 +234,15 @@
                          -

                          The drawer component is used to create responsive and collapsible navigation menus. To create the drawer system, follow the steps presented below:

                          -
                            +

                            The drawer component is used to create responsive and collapsible navigation menus. To create the drawer system, follow the steps presented below:

                            +
                            • Inside your <header> element, add a <label> element with the .drawer-toggle class (remember to add the .button class to apply the necessary styles).
                            • Create an <input type="checkbox"> element. Give it an id to be able to link it to the necessary interactive elements.
                            • Immediately after the previous <input type="checkbox">, create a <div> element with the .drawer class. This is where you will put your menu's contents.
                            • Add an empty <label> element inside your .drawer, adding the .close class to it.
                            • Finally, link the .drawer-toggle and .close elements to the id of your <input type="checkbox">.
                            -

                            Drawers are responsive and will expand into normal containers on larger screens. If you want to avoid this, add the .persistent class to both your .drawer-toggle and .drawer elements. You can also change the position of the drawer from the left side of the screen to the right by applying the .right class to your .drawer element.

                            +

                            Drawers are responsive and will expand into normal containers on larger screens. If you want to avoid this, add the .persistent class to both your .drawer-toggle and .drawer elements. You can also change the position of the drawer from the left side of the screen to the right by applying the .right class to your .drawer element.

                            Sample code

                            <header>
   <label for="drawer-checkbox" class="button drawer-toggle"></label>
@@ -257,17 +257,17 @@

                          Notes

                          -
                            -
                          • The .drawer component can be easily and effectively combined with the grid module's system and classes to create fully responsive navigation menus.
                            • +
                              +
                            • The .drawer component can be easily and effectively combined with the grid module's system and classes, as well as the utility module's responsive visibility helper classes to create fully responsive navigation menus.
                            • It's best to use the .drawer component in combination with a <header> element that has the .sticky class (check the last section of this page).
                            -
                            + 
                            <nav class="drawer">
   <label for="drawer-checkbox" class="close"></label>
   <a href="#">Home</a>
 </nav>
                            -

                            Do: You can apply the .drawer class to a <nav> element, effectively making your page's navigation menu collapse on smaller screen sizes.

                            +

                            Do: You can apply the .drawer class to a <nav> element, effectively making your page's navigation menu collapse on smaller screen sizes.

                            <input type="checkbox" id="drawer-checkbox">
@@ -275,7 +275,35 @@
 <div class="drawer">
   <h3>Bad drawer</h3>
 </div>
                            -

                            Don't: The syntax and structure of the drawer container is very strict. Try to follow it exactly as described in this section.

                            +

                            Don't: The syntax and structure of the drawer container is very strict. Try to follow it exactly as described in this section.

                            +
                            +
                            + 
                            <div class="row">
+  <input type="checkbox" id="drawer-checkbox">
+  <div class="drawer col-md-4">
+    <label for="drawer-checkbox" class="close"></label>
+    <a href="#">Home</a>
+  </div>
+
+  <div class="col-sm-12 col-md-8">
+    <p>Page content</p>
+  </div>
+</div>
                            +

                            Do: You can combine the .drawer component with the grid system, similarly to any other element or component. The .drawer will be displayed as a slide-in menu on smaller screens, but it's part of the layout on medium-sized and larger screens.

                            +
                            +
                            + 
                            <header>
+  <label for="drawer-checkbox" class="button drawer-toggle persistent"></label>
+</header>
+<input type="checkbox" id="drawer-checkbox">
+<div class="drawer">...</div>
+<!-- or -->
+<header>
+  <label for="drawer-checkbox" class="button drawer-toggle"></label>
+</header>
+<input type="checkbox" id="drawer-checkbox">
+<div class="drawer peristent">...</div>
                            +

                            Don't: Remember to apply the .persistent class to the .drawer-toggle and .drawer elements to avoid unexpected behavior.

                            @@ -293,7 +321,7 @@
                          -

                          The <footer> element is used to create your page's footer. As normal, add the <footer> at or near the end of your <body> element and add content to it like you would otherwise.

                          +

                          The <footer> element is used to create your page's footer. As normal, add the <footer> at or near the end of your <body> element and add content to it like you would otherwise.

                          Sample code

                          <footer>
   <p>&copy; 2001-2016 Web Corporation | <a href="#">About</a> | <a href="#">Terms of use</a></p>
@@ -309,7 +337,7 @@
             
                          Sticky headers and footers
                          
             
                          
               
                          
-                
                          You can create sticky headers and footers, using the .sticky class on either of these elements.
                          
+                
                          You can create sticky headers and footers, using the .sticky class on either of these elements.
                          
                 
                          Sample code
                          
                 
                          <header class="sticky">
   <a href="#" class="logo">Logo</a> <button>Home</button> <button>About</button>
@@ -322,7 +350,7 @@
             
                          
 			
                          
 			
                          Notes
                          
-			  
                            
+			  
                              
 				
                            • Sticky headers and footers are compatible with modern browsers, but might not display properly in older browsers. Support is being added over time, so be sure to check out if your target platforms support position:sticky.
                              • 
 			  
                            
 			
                          
@@ -331,10 +359,10 @@
       
                          
       
                          
         
                          
-          
                          If you want to learn more about mini.css's modules, go back to the modules page and choose another module to see its documentation.
                          
+          
                          If you want to learn more about mini.css's modules, go back to the modules page and choose another module to see its documentation.
                      - + diff --git a/docs/progress.html b/docs/progress.html index 58b6df4..3e98fe9 100644 --- a/docs/progress.html +++ b/docs/progress.html @@ -81,8 +81,8 @@

                      Progress

                      -

                      The progress module gives you full control over the presentation of progress and loading on your pages. Apart from progress bars and color variants for them, spinner elements are provided to help communicate that something is loading.

                      -

                      All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.


                      +

                      The progress module gives you full control over the presentation of progress and loading on your pages. Apart from progress bars and color variants for them, spinner elements are provided to help communicate that something is loading.

                      +

                      All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.


                      @@ -90,11 +90,11 @@

                      Quick overview

                      -

                      Progress indicators are very common UI elements for almost any website and web app, as they help communicate vital information such as the fact that a process is being executed in the background, informing the user that they should wait for it to complete before proceeding. The progress module provides you with two essential tools to communicate this information: the <progress> HTML element, which is pre-styled and compatible with modern browsers to help you communicate information about the percentage of a task and the .spinner-donut class that allows you to create an animated spinner that communicates that something is loading currently and will continue doing so for an indefinite amount of time. Both elements come with their own color and size variants and are fully accessible.


                      +

                      Progress indicators are very common UI elements for almost any website and web app, as they help communicate vital information such as the fact that a process is being executed in the background, informing the user that they should wait for it to complete before proceeding. The progress module provides you with two essential tools to communicate this information: the <progress> HTML element, which is pre-styled and compatible with modern browsers to help you communicate information about the percentage of a task and the .spinner-donut class that allows you to create an animated spinner that communicates that something is loading currently and will continue doing so for an indefinite amount of time. Both elements come with their own color and size variants and are fully accessible.


                      Quick start

                      -

                      To use the progress module, simply include the link to the flavor you are using and start writing your HTML page as usual. One suggestion we will make is to add the following line inside your HTML page's <head> to utilize the viewport meta tag:

                      +

                      To use the progress module, simply include the link to the flavor you are using and start writing your HTML page as usual. One suggestion we will make is to add the following line inside your HTML page's <head> to utilize the viewport meta tag:

                      <meta name="viewport" content="width=device-width, initial-scale=1">

                      @@ -111,7 +111,7 @@

                      Process is 100% complete!

                      -

                      To create a progress bar, use the <progress> HTML element, specify the preset maximum of max="1000" and set a value between 0 and 1000. Update your <progress> element using some Javascript code, by changing its value to any integer in the same range.

                      +

                      To create a progress bar, use the <progress> HTML element, specify the preset maximum of max="1000" and set a value between 0 and 1000. Update your <progress> element using some Javascript code, by changing its value to any integer in the same range.

                      Sample code

                      <progress value="0" max="1000"></progress>
 <progress value="450" max="1000"></progress>
@@ -120,18 +120,18 @@

                      Notes

                      -
                        +
                        • We made sure that the <progress> element displays properly on all modern browsers, using browser-specific rules. However, there might be some irregularities with older browsers, especially legacy versions of Internet Explorer.
                        • If the preset max="1000" does not suit your needs, you should check the customization page for instructions on how to set your own maximum value for the <progress> element.
                        <progress value="80" max="100"></progress>
                        -

                        Don't: Avoid using different values for the <progress> element's max, except for the preset one (1000).

                        +

                        Don't: Avoid using different values for the <progress> element's max, except for the preset one (1000).

                        <progress value="450.5" max="1000.0"></progress>
                        -

                        Don't: Try not to use floating point values for either the <progress> element's value or max. During testing of the module, we found that floating point values could cause unexpected behavior.

                        +

                        Don't: Try not to use floating point values for either the <progress> element's value or max. During testing of the module, we found that floating point values could cause unexpected behavior.

                      @@ -149,7 +149,7 @@

                      Inline progress bar:

                      -

                      Apart from the default style for the <progress> element, we have also included a couple of variants for it. As with many other elements, you can change the color of your progress bars, based on the context, using the .secondary or .tertiary class. You can also make a <progress> element display inline, using the .inline class.

                      +

                      Apart from the default style for the <progress> element, we have also included a couple of variants for it. As with many other elements, you can change the color of your progress bars, based on the context, using the .secondary or .tertiary class. You can also make a <progress> element display inline, using the .inline class.

                      Sample code

                      <progress class="secondary" value="600" max="1000"></progress>
 <progress class="tertiary" value="300" max="1000"></progress>
@@ -158,7 +158,7 @@

                      Notes

                      -
                        +
                        • If you want to add your own custom size classes for <progress> elements, check the customization page for instructions.
                        @@ -166,11 +166,11 @@ 
                        <progress class="inline secondary" value="800" max="1000"></progress>
 <!-- or -->
 <progress class="inline tertiary" value="650" max="1000"></progress>
                        -

                        Do: You can mix size and color classes for <progress> elements as needed.

                        +

                        Do: You can mix size and color classes for <progress> elements as needed.

                        <progress class="secondary teriary" value="450" max="1000"></progress>
                        -

                        Don't: Avoid mixing two classes of the same type (i.e. two color classes or two size classes).

                        +

                        Don't: Avoid mixing two classes of the same type (i.e. two color classes or two size classes).

                      @@ -188,25 +188,25 @@
                  -

                  Donut spinners can be used to indicate that something is loading or that a process is running in the background. To create a donut spinner, add the .spinner-donut class to an element of your liking. We would recommend using a <div> element for most cases, but <span> elements should work pretty well, too.

                  +

                  Donut spinners can be used to indicate that something is loading or that a process is running in the background. To create a donut spinner, add the .spinner-donut class to an element of your liking. We would recommend using a <div> element for most cases, but <span> elements should work pretty well, too.

                  Sample code

                  <div class="spinner-donut"></div>

                  Notes

                  -
                    +
                    • The .spinner-donut is an animated component, meaning that if a browsers does not support animation, this element might display incorrectly.
                    • In certain cases, it might be useful to add the role="progressbar" attribute to increase donut spinner accessibility.
                    <p>Loading... <span class="spinner-donut"></span></p>
                    -

                    Do: You can place a .spinner-donut inside a paragraph or some other textual context and it will display inline.

                    +

                    Do: You can place a .spinner-donut inside a paragraph or some other textual context and it will display inline.

                    <div class="spinner-donut">Loading...</div>
                    -

                    Don't: Avoid inserting text inside the .spinner-donut, as this might cause unexpected bahavior and will probably make the text spin along with it.

                    +

                    Don't: Avoid inserting text inside the .spinner-donut, as this might cause unexpected bahavior and will probably make the text spin along with it.

                  @@ -224,7 +224,7 @@
                -

                Apart from the default donut spinner style, there are also two more contextual color classes: .secondary and .tertiary. If your donut spinners are too small, you can also use the .large class to make it pop out a little bit more.

                +

                Apart from the default donut spinner style, there are also two more contextual color classes: .secondary and .tertiary. If your donut spinners are too small, you can also use the .large class to make it pop out a little bit more.

                Sample code

                <div class="spinner-donut secondary"></div>
 <div class="spinner-donut tertiary"></div>
@@ -233,7 +233,7 @@

                Notes

                -
                  +
                  • You can mix one of the contextual color classes and the .large class, if you want, similarly to what you can do with progress bars.
                @@ -242,10 +242,10 @@
              -

              If you want to learn more about mini.css's modules, go back to the modules page and choose another module to see its documentation.

              +

              If you want to learn more about mini.css's modules, go back to the modules page and choose another module to see its documentation.

            - + diff --git a/docs/project_thumbnail.png b/docs/project_thumbnail.png new file mode 100644 index 0000000000000000000000000000000000000000..4f4af67a24a88cfff12ded5f3657d23b240479f5 GIT binary patch literal 19199 zcmeIac|g)x_XkW_Ig_PLi&ieQo0(dfOKv#XZfa%bE|sHZE{MAzkkhD{3vFudTB(`a zxUWFvLb>6RqM}feqM{NaAR_R7X=a{x=J$J^_xbbv=l93t_rmv{d+xcP^Ev0kpJxYbbqb8Gs64Zfs= zt;l^8=6YC9t}f%uEyhhBn}Fx{)Ndlsxp{6r6nk)Y=>72h-It z^W&E9AA|mAe5lE;F$6xn=lf$Y@aKYg*?dXc8sO;{%kR#N?=* zKgh`%2iOZ_UK=>?6(*&#f4+9lML6R6ce($DH};U>yndi3sPbSh@amp5e@tl4AB~2j zs?`5HjjSNv;(zS=r(uj4a~y!cKp$=_WETAKlwvLm%zfS09zP=p@D0FpJ$_C<0Z-<& z|4zX$f7>wWD1VyvFB@vzo&Cc^e-7mQsrtlsX@A)C-XDYf@P~o@uMWJC%J^%N4V?5F zf1lTfEOND!VEu ztIxW@M8ZtBxk5Y&6wnBG!GV`131G|;_QjRMmn%h;3N~`nVvf#3$Z|(ctFnX-D=@{6 zNtVHq{cZvUj8YCocp*4!lZ{+=5p%rR|0JHPj@gZo3{mvRLXu>a#Lhvpid7=dF~Ep2>e-{lN4g@*69*Z72{6&eoOXz40HW7S#jHxG@mLz#X8f@kyZI%Y zOc2|!-SW0XV^*>3ap!Vh!zHD~@K=q}8A^@lzOPp}!9LHolKTvZ5j*sMQtosT(nloR zh8UT~F^q&I!5uA#uU*2nV^-SAr>dzKF$0rSzPbP&+VQ(PX8Sab`|T@NMRIX&VYbuc zo-NG`WH|n{aZzRsNMqV}7TZ%G6{>`_d;T-#i^NbRK4Yj=!V?jm+n&LmLa&~2iFnuJ z08CoHtiiW^U_?1?i4rOf)wmfiypDpB+de2s&>co%Gc?A6w!Ao^7Jsr%0c3r?p=>G& zbZ>j`l<=i4K|AHEaH3+P?zH4vPv7!fp;|hRCYi|*Ylx@X2#K&cVd&}tEAk+Z%54Z= z4#Kt@5Go*O0Y~DZTOi@(=d|_LhOoiVh|=44B&&na_PU&vs^xwqH7t@Pjx_I_I#Z;ZxvttpnEyrclK4j!+*wOxRzzC{< zZ$CM1n`^(30}12SvoIh#3 zz`hVB1bq(P-@E3*Ib4)@(Grrey>GI@;p1@4r%sCO-JTZ&UKk;vXA0j)Hm)s|f{P~Z zCLJjYTAEO{#F)I^G41{nv@CFSXfzw4W;?^K!Jc=g$b!1E&1LuO;%-<`Ul?{)?5nYW z@9QVGJ&A;^Qoy37-BpVUHxf8$WM@&jKq7F@DQ(Oea3_R<>=mXu0HJ00E3jZ8=w5@= zgI;EvL(r??B}OpRh+Z$ZXC0sTBoZ3Q<>TGpICbmH2iXUey=tgEtE0=)R>&h|{2;#B z3HRJE=qhXi+>vU$=-_f?@2{E=F`<=VP@89X6w1n$%-|m~MF7UX z93>m?%o2!qj{IIaf#92pgS*XHU3}t0?=`E*!`E)5-Ni}->gQkZCm;zqO*H^oFc!#m2sCsUi2Du0hh89fG<)RNavrBi*PiqO|>ff39d?swvkA>)9b$4mqpZ)v zQ|RJI;H|moSOxgt-nFRODDjO|aSV0(C^Gvl+_~A2dMA>7L9mDc(}wFqBVD|zP>HJa zkC>CMOPns-BO^;aW}(_lJ_zKcA0=;oV%^G78PT%M1TSc)$57jyPDvvi;E7!Yp=ybk z2==#MWmmr5q;4-(VkJJ-vuUe+2X5!KKoXd-1SN_v=V4!V>}~o)@x1TSD%!NHn7jN%Ixt41#cwjotm#id9a=ta zK!WpYz98;1YPAniwskt}ng2a~6-!PF06fFS#ry0yXeFl9eIj+J&;!n=U5J zrRQ>OpfG{HmBQ!p_LNA;E04Qo;zUS-Wjkz>J&HnXuhYeNN1H<--Y&}H_(rTB$F3q` z{)`H=j%QiXz^t7%=HKsYnx5L}BsO;$*MH86}Xvq2*zm6S`m+pvN)1$7zxYY9Hs&u*M5S&NHw9k zmdATop`=9diz^UAfWQO+(gJ!E6}Lpm_fW%zXrU@z6|GiGZnz{ocCvGF7Gt&M?P+P+ z1=v=pD}y@Rn0}uAUfiF+dwaj)5Y6D=2iZf>5q;*tIS|EB%uc4$$|cA_gDdY^ z=OXOU0g9afCM%Pjsm*49Pj@c1R2+qDx8%sM&m@{d)4@kgL+his^2Gktn{!25r}>c+ z9I2OgE?R_?hxv|Mdi}6;iK#^^SlGBG@@G7z|3so0erP##QYR6qxeg(y?;&!mkW?Oy zUYH4UhDQWXlH2+#m{j#$Npa-&H-oc;ZEWU;a;7M_#7FsvmVqIua}YDO=H^}?XMVD` z*M=t5At65=e*%pVPR0+V`ez%QoIh1)hOtLmE|rf#X5{C{OOc0SEW@BVyGMc?|AF!u zrRhngBmOJaGB0w^xgOQ$@a9gaLY822MI$HvxRK$c{G1FFTWT5B{${G^ov9RJ3ZMYb zZQt#gb1}-yVRz~*5x(fVY(9hFT2&xEnpV`Xnrwd+#tnz}6kMz@rThz(FzOZnl^y^p zOI4>W@`+`zn>Z%(houVhQW(I0Zt38M@v(K}AC_jAS;GZ+)A(iD^&dV*UF`iWHY{~LpM3kZ z-<`-N&nA~4mJF!JMH*;+Sh6+lEz~v+F?ChViSu(eh-2dSr3@aYJ|*kAG*S=|0Sc`G zOTd=8^*$+XH*P_8OIcwp$m`G_kStQ3w!L2;sfaY`%?NA#VD3HCD2bZ(Ry!;%aZLQZ zyu_ql=zdZBhRyYdhFD$BEHlfP1a@>I(vWVEo0A^pruJ6TnBbIo5WMWoN^CRJx$mY~KHZLbSA2mGy_AJ?Eiq*c?VMfl^>yXU596nX zuDQSx>=+p1GVn6JzC`%+c=hzC!(iyuk~ z?Ppo(X8+zVuYQ_NTtC_sB`&qy(<@<`tXm0)Hm4n*3FffVn6=ImFG6h5Jl{7|XZq@D z@0mMf#N0Op`pOp({Noe3mzt0(Mv17rDmuKn7h%x>w(92#4rb3gP%PC*2FP&b!HnW|t ze%qbc`)pdr7-vE_H580Cs^y`LYg5;ALPR!gJBlIO?lU5DPi`~Y?y8mAHd;n%JBS0g zJ8H3B?B)yQbB7xzlBRvM-0aP2FT)!;m7RKA$JTss@{i!O1G|Ewov;TUg3bBNWLarW zW0^jb#O&gqCx?IYd)|g1lO0$$XJR~*Ju4P&e^4Yhl`U|sU2ChnT>(sLc2CLMP)O&% zP-LWRdn&6dHHSLB%&~&_%k(9K56=s~5-+=8-6CBC2x6_rZNakZZ<3Y9qf92vk0~9VX8Y9rRcY=|hac{^k6?NWF zXg>#raF*qVRLF=N*ertR`Mc)X)mD0eTKv0>6k9b)GT3=$*$&8GQ#)5oL2uKv!qC!b zUO!5L9kvZsXTi5g%)m@neG)SZ-#tin_8ut`o=PQ>snm|n)bf{)8O5u^X+x(Xy59KN z%(F|m%k3$hD>Vur03csKC6$g4uRmn^1*ZvydFO_XgRxo6=YyQ#b9JuIWgfj46KE;_ z?>)Tv!fJ}be>~~==kZY%ty1G}2LnlfU!qwt5!I7t|w{N^^xOjRF^Uac7G_KHQfsKTS7xT#zZ<8J$7VrHmI=r2l zsFaO3Y8E22V2=p#KgniewA{i2yu3}hCI$UyQ$@nz?Gw{g*tXJ_P4ppEaNN5RqLJfT zRYP6C9=0(K#>t6eVFxy{eq4HL5UT5}yC@1TzVg6b7W~ExAJ1!-i$1M_n%zI>^`04V zIiCSG-A>%dY8O9#+(k4*{UPP^$>V?-G5eBCk(e>T2RV9ST6Q>Ra+tsz9X`3jUGB7} z>15$o{F@iA3rZ-Ten@v9m-1B~LYr-kL`yg*5o%W7p1{ zht&9pS|8s`|D;0N(KBDZS=iz~VOtZ0w8ZyprHLUAZerWzH?V;naHbfFmGF<3&*62| zAlDwew}htG`ce1<Wec&E_y15=n`Rak4i+`-aGzwk*SReF@^CsS0f-^V*KqeK-2=&c^ zH?-H?vMia7Fw8cNJgi0#M%9NbxmPeAPZZS=>S12VjN+in)W}nA7}k9FEt)%fWL%*& z(XBF{V0hp-U7#)tHop-nLM!K1}nTUAOFA|N_9*`D0}!N3xtflO{$zB z{ytStZgS0sH!ePgp3nOh82P5q*H;mBG&`bv3o#p~IrK?aQ8(>Y#?aE(R%A8`vXO<` zg4CZ+cpQ~g;oX-q(G~FJg2_p5irH>iszz(veWd&E?~mtjYkQVgMz>~!5_YOzVp6N< zW%Zl|7BQZc`CuDhyBbzXdy*}Vh)Qv{pAjA7MV?nctD7N(G8JBYd^mz8Q&H3(essk_ zCA@q~bc;gk&2D;A>CXJ<{S^{kmR);&Ht}+8ftQy{gRsr;YPf;?T;suW8*1Bb3ea{D zv?0-{9^&$Mpt1Rka(x1?2ZdxUsf^7!<2 zH<7h3^chzo0d?iLgmtEX47rIY4b-UxM}0O88K!b%1M$9bryA1IgzX8SrdbownQB_8 zQ)}%+_JLz;MuMKra_VDn zTi^S~!vx9v;by@v3AMg)3n`lJq%RW{&&R#Y^HDiJES1Ll$DLQmdGJ0%Rynd;=9NvZ zOkrF_S}N-qevcwIDUxtBv|TK$t(Ob}>w(x4(~+9Bd(?JFPwc@P+4UZMgL36#GMr>t zQ(M(@Jc4n)!u{^yqsTpOX*>^<<1>)n8??*`;qXF#G^4cEqU*C@dEad%C%=$1+nfD&iRSyVH@qlG@o31 z#Ohmj_R2FRRQ;JB^F7hF2uY z&e;0tuO(6R>wI|5{IH!`#tg}RK0MjF8;yn~LY~;^pImfUUB->F+JF>6x3~DH0fiLT z2-pOn zIJh4JHvTmI)_Y>R!cw;E1d%8QpZN9^&M45dWabp^TDpV zc8u!>dZ5b7`x`NETCD~p%wEOFEZ)3aSWgO_dy~*z?KnD1oXKv9c68Z&<)l+%-Mj4F zojps>V`NbBIom=|@`D1m;YhyERYURZxm_blroe8IupkL zmu{FE&9)ETe~GoExHgt?^NF)f;_5u}@(S0d zL$*fAtNFxI@SXn3WU}5*d&17c zWI6|HHp^g%IzTQE`i))h_cdj>f-c8i;=qV~bbx_^ZOg;ZTZ|P4A&1;!E`|A^nV+A+ zC1p+YT2+2~b`!r%jDj9ELx1iIpL!cc7gJbCuKUAU%UrRog6)`&jQq#sLwU&Th4}X)k-o!pgm9@;JFL25oj*Z7q(Sm=UTaBK;+&$1t>~ z6_U5uiR>u37hwZW+4Pp!+miiQqG=su3(_BRQqA<66FbI7xbT3QvI1Nk2-Mf&die7t zX6m~I(#5TrPMQF(Pg0t27-26gM4UulH9CkMMfzIjtnrZWX6f|u`0g-*iuy+N31U;7 zPOqdKIH?6PZmZ0RC~Dxv1S%?Em0u{wQjKFQ2*c;Xza<)8^)pT#SB7W<3BMR?|Kq*U zDC&6N&%RXdFDeM`cpURG4Y?oP%vzY>aL1H|3Ix|sQ%(~*{=QASUuQvyWDr%sc(+LF zL7$SJ!`~X!w?dck>0Aau8QHPFh6*naYbq%7>KkW|A*1_irZ*@3wHV{^{ttvXsQuQ@ zc$mQJzB<$oWdR4&)Sd&G_1Msn^5`@uROw7u=bgFqz@vPY`2Dh;aPyyWq^v*GW$Vi( z%od2Ma5L+DoFQVl$xeJvFCxvN9PjLeVV|NJt-ic%$OH7v!Mxo0E*}HoO?9%nP~e=M zbpW6K+!AG$L5hn3=oE!=-CAerygE{AVcbCuvw#;wj+%7?Ub4#Z+}GO#9F>^L+MM~a z+zFSwU1G=>?)VYd09|Lx@tZ0zU!Nq@-kO4dGPM=aC3QrRj#ajvb^D7ZdN2EQv-rd2 z5ttk(b84N@TaCM%@$(a{kJa5zR{0qQtwp^fB5p#Pv!{z1+aT84Cx~@ePrMdzISQPc zb@iuho0ii;mX_65JerO@gIqIfhwgPw_Ka5UfZGZ8N`tD<4 zrVL2#bgs-X%e5$f{|D!xT5g)CxxxEzo3-R#`9!l*^GBZ$A(ar{|q@Q>~HKN=rO@8bSm%JHv#H6ZT7 zKN{x#cFYUXLH=3C@DFMKXnZL3AKwkU|8J`z{#_whV6n5#9|a2k<^bT&f{s5=1DM{p z1Au6t^aA0evl)2$tB~a%ul=L(29w8z`?%vDruj$1 z+~10_;K*GKs(g#Z=?NpP;hHp zrDZ{XtsEc#9r8B;_r^wf#sAwT=Kg*{z5k-yU$gL`l>f(Nd*n<;1BuMPtn*jJOsNk| z@o!rFI|%*Z9DC}@P{@BHfLjMs06zX7SZNURRR4?Cd&o4j>)!<48#5P%{O>+{40^@y zq_6!|rt@!b{789v`Q~>~9h-w)z`zqw{d8ZI43rf8kLsttroB0IZWHk3|Iqs1ik_|C z3%vRNSp*bgZ&g=+En|zS!Qab}{)hjw>NTuAEau6?Ck0do;C|p;E%O9T z4bbp;;@C=(LR-aVuSsV~zV3az8HerYfz;GL7R&o(b{ob}IkIx@}y z|Ft)Gl|KM3H7iOY3{$3L-R(LrOaZs{AW)*=jaBci^6FhYV`&86Q8SsY{a%R5>sncq^0Ed@5!X_94>w%|)|br1N>ro^-4?P(3$j zs8hF(pus@_xcK~)>ECedMorQg`yfp4r0^xd4>?7-e$gLA?0)>lqnlYABY0k6Tu*+v zZ0k$*!b1V+N1NZ(D!0=k0hT@LL){slexrS&AbZ-U=?G^&a|qm;v=tzXuew3*HPpp7zJ>QPe9{Ap`lr6va`y!5lggdCT>d8&iHkm-I@Z z{oz!#y!3>YTMaS?7d)f`EBb%6z3UYiShy6PgN3Q~IEL9cGU7R5+wQ!L=p z{vpu_PQa89Fw@)Bq8$u(a$c$|LZHENgdw*^;S0En=?1?R=MSllF-<2?zt6995rJ{; zHOzS9O71?l!O7#E43_Rs^T+sG5VamB=kb)?9XT|1FeQ7mZS9by& zzq(R?Q?SJBEp!?+*={l4bYdj7Yc0x^!kaeq8OfYzehe7SJ)*O{3wj;sa?*3Q`}3hw zEZ%UF#2)@adboRLHBiE8Z(}TdN>~C)-73obC>Lqi%WF|*JEu+og91f?B%fTH%tgE| zM`h{w=5KT0frXWxsPA|DkNw zrbI7b8UhlrtKafGB?g(+42tm}9A7xsi`sw=pCeu8#uhaaJhh&fi2G zeuj*eibpXmE zP=jBM9i@srtcS+jzc(?KTOtA+JTwf6EzPEWsT3S-3WQ9-%=uolYDEb_gV5` zcV3i;?Ag(MvUDgR`1VlMjH@83UxUSI!Zsu_A`PboZW6ihg^_W&-3+-9Sw7+@Y{amf ze%24=XHV>(igFk<+N$ZS^RQ-~{0rU+K-fn+jUFFTIzcto45vO+m(==3j{wo?1v}_& z9WQ-Z;m68b?mp@@pk%;31B6XZV-9Ecbg`3mI$!ynUDXvpfBrLm9xp46aKR=F7y~Fk z(n&FZJzw?o-Ssh&0^suL%O>vocCT*P^5@}^$>vZ%0mdZq_DG{md)?Hr4Ezg^piN<8 zCv}8II#FiL_W)>n?qz*;V`;DeaUSB^rml%?5rEVi)xOz0a^*rw{EP1n4kRx}GmGGE z{E~=<-BHxRG3dtmFQ>W-!X{;J=ZYFnv0(o6Q+4ewC4Nm)ue#Gyjduac5+6==2knLw zXkt0HbD>uRb(@{fzbNEZcGW3??&-Dw*@t@wGd~SROuP9SMgE#|)hBqUxyKwj)C|9N zhvcD;0*bZ(fu7bv(?aQ|>{qdZ=OrzXPgbvNs-Zm+#4iUQ)9W$jpzP?8T^&R5w|{r{ znxe>q-p+WVgjRh6p%F{9*!G7hT7CQbl|Fqk%o!|+$O1MQh@Yc}vnjrau+FnpRKDYS z1V)(jG;n|YU27fyCgA4l0lv0a7jrzP<4Buec=Lp3!V+MII_{e;{u0ZyCn`ZRUI$IUAj>l*8(QO!7!K?P*z zB`GUYCBOlKU1wVw;IbtPpUs};3*JrpH|*gkaf@DG%M6=}=kI#04!DA7Vy8dAyrMOr z=P-+TgELTJO+^{Xxx^oL6hSF_$W^WT1@Br|6~$w^1GyOxBY;z1pV6|N5;1MO`Rpsw z%SFQ+PDzAJlo?zVaj+`KDyLh66(YM5K(wl;FH+|K5kr##kj{?T?v^w{z0JYFiDq4z z62k!Id$?C!qT^QpL|L+{Mv$%t+tXX<7HdYUngO!kBBV;7GO0n!v!7y={t+Pik1O&E-0VfO zPiT6AJFL7EMgvZ zT+PSX$2FF^?7PCwnM)MkjiQ;T0Fj<#sHi7{s;65#o&;38I0=N6o>vT6cPr*(8sW38 zo^2*M=ze|Lc1+TIV;6r1DEBI`7)d$(ZXe&I#Ia0@fkVif!p&(g&P?u&=Qb{}_>j>s z%wsd-r|5I@&7@Wv&32YDySsFAPrB6SCy^7Kvb0hoCTi(3xXr552O8^kyjEw$bM?)H z5oR~IjE$U$&p^B&pw4%*KcGHmQeHd(R`>;d&LfQ&e$X*C>}3yZ!~vc_`o)L&fK#^G zcuIEVdG=7}37Qv>5m=e#OM_CXwXjEb7>=5vppR%0cDZOxlJjh80Psu+;cuR=C^H6S za9g735G+LWA-3HM=asHUSlW;IiD2S3znizn6(7O#A1kzVq?7ZoGx3RaV((SILGF_6GMS@ty(?$74aQImK+O?BEVkp2 z4CuP;{4?IAp=!JAt8+dCBaX;$ummQ#G7fi}F$#W6eg1`)aY)i0VH)MOcw?l5@9WuJ zOe&E4?8|)f(~xV^gd7Q{*MgXpTRLl{=?+|e1HQ(ou1MQHZJ}y#APDf^Yqo5 zgc?6Do~$PhPEBLQPj)L$>Gj&zC}NUI%eh@<8$jmiF$Yc=t4^tp-V@cZ@M z9JT3fd1&~iI?Q3t@in03x2L#S{cdcdrS#NgSM7eUW5f8W*{o5o%0_PgE`ktyvVP|2~##cD|0t)*!iP@|;J`Bp}rSWWNRk97MQd%GTG9|@q0^n(wj%~+@35j0sdhj!j29OsCvES z4Ae3WYNh@nE^s_t70Dfapw}7dZ3WYs4 zi9KC>{1{*vNC0&Owj=hyQk$g zISg~?r|QK|8<%)h#<~i#(Shhr*%KH}SKUavG&rZ|l|zc6%nAy*i(SOcAVX9)_ZhEf zWwgw1y2+X?&l0S1N-Rd!h*_J&N#T4yl(8Cw}y0=yx?!}d@V{!Pdn zV>ole22fYIz%U=Tm^e|ZzvNmN9?N&u1!JEA!MB@Z6l5k~3=PFEZS)L*6zz^ezq7)q zK~UxRfnMN}emhkd5y>e?LmP-5)-M%6usM2_Krz4fDtoi@Iz*>qp%@6nK(X3R0Fa3a znViSALoW2@a9O_G3ArV^(n$z0MHIdkREQTCeIH-jXZicg>paY~)ms26t|*v)xIT_E z5i*^jEbbvRM_82j(6R-?M}Gr2rdX0N>bn*dY|}k5|B@s*8_D`6Oe7VMj`@hGHh3kP zp!lVp*Fc>sI!1QIJ4lvq6l?&CvtmSkeOBeKCgrwN?@SwcZoE56sFjA*1O?n3?L{+x zjTS72O#5*GGM75YFtF8_a<6{0VYEDhlQqiV7%dg8Q0lzQ&T+i0;cmx!eFSzRHBjG8S4?_INp5mB{kCAN=><#diwDS>d5*eS7bb+A^s4ymK zy-7X}u)bE1FkAOig)ZlKhK>6Eu1+l<>ajxBs*jUSXJpsZ5+Vm{SgzSid*H>&o{^uo zZw;yO9AG-YfW2jO_(FUlw18i znzVZL4nFhV-t8gTS<Wkb2ONNt(M@4<9jm}`=ZNu0VYSU5 zC3LXa`b_5C$7W*yPfs-0p-v7}yPCmhe4FG8EPvMrtU18gLiFHr4MW$VNiY-cbLkt# zFK8a3eYr^aw5FQ1v577^$DMwdJQ{Dww!{HUD z@{g-BTR|V%V|bJkn>iQBc_eyRW}I=e7o=Tx*ImM`cdSq76J-`UbuT<@OMrtDPDQEb zt%=Be{W_u#3Usd>Uj0m*JnEqy0ZhoOPJ*_{=>8`D%Ix*37q2dpCY1?zxp^QiX>^>S!e;Hs0mGbVouJTuyv~TTIbiKYm=mpEZU2Wjhd^$>rx7>ZBichcLy z!Wq%;iGF)5e|WTo7^!?MUFAsNkFh^!Z$EpX$Z(JK*C&A&ynp-Dd+9;^Q@P}Qfj__5 zXL;)S#OaTD9r@iF4e&_Bb5~aQ2$qfT%uWjv$I_ycOa^RdvkZ=kymqDFf4T=7u5m zLZhr(B=TVLS>A2wZ|iFPU5sZ(l7p)1O&H;REj#*gYCY#`L?`#9s+MwXJAN(B5xl-j zS~hd$R;BwN%q=u~rA!OX&RF>Rrh&EA$fzFpefUXh`Y5Hg`I&!A5JCR|vu!7_w$;r6 zko|UQvU=d;RMclbyGxD%&9xT~S3Q#hhjC9`zDqP|D8(gjWArwhZd7j(G+LDvgl(Q) zEuO;5O;3NuM_l#(^~vIDirXcFmWVU`-u8#-QK{p3kF@RYTt4-|?H54!y%0BAKegv| zBQ1IKP+nL6v#Fl7t@WX;x>=*80WXIDyLQCd81vGMjn8$TGrch&p*UEvw)Y}S(jmgx z4fFA}X|ZZc_j*)AMZOL_eD1YI)t>!NtXuL_B$f-|SIV#5F#hNk0E}ZEh92psUb6Qo z8`6LJ#XZR^_BeMl?=8-;r80=o+kNiz!SkmZVebV-a>X-1Njyn^m4aPL^%=j>O`h&a z3-iA0ofVsO&$V+^r_?{)bhJUS|u0ezR{UBdgE)M8egotJuNd z;%rpNeR%~v%)*LE@VempypBD{w>y5mo}Ozuo0qL~$Ubj&2soA6SSJ1d0stVG(0jl< zxR+F^v=O z{hutIsi#^Re(F^hKz}(W^|uM&v~tg#GsDvLfO-{sC&;tZR}hM}Up)4{7rd^`iJ9DI znFZ^*R3}c8+tovM1Xld_yVQ>Epy_Od>2kjTflTSW4f$-Y7HjN_$-bGB+dB}S4^9oL z5Zj?8fF0IF9d;h2#C1mMSyi<(alMWg;poNI^SIV$N1U@@dasbkg!DwCk^;Vyov!3F;82Rc7q^!oQ;wwtoRo3-!!CUFnUc@r6l2azuypf z47T&?nLC$mSo!7DX8$Y;ez5s@S^iA`cqiM%?;{=`Pnthw#WIxMf#`quEj8Lr&p_Eu z;dk$-YNIKm~Vd}+q~OVpmeBVRj*w0{mP#H&y1d833|7doz7 zE~~`Iu6C6ID=QBWhBg|&w9)3y^?)Wi*E-C2rvdA{)%mqLAD8v4@~vA__0vsnXCqq5 zuB4dCJa04U;}>13v0aY{X!%BFu3s5w^KNu_9g3S;kUmT|pM{jB&h*QkZA9YC!*rBp zE|s1h(dV13{2Zm`l2ed;M~F-tFY#-p6<>R@A@tDn(vMjSkxvSY!OUQR!;_6p2|x+o z%zL7Dql74Lw(F&wg_*+i81&}jaJ|g)2eLvt4=Sv__=bIcE&pAWaVcX#7vuj#OkOa<_AgEKtV0Q2i%7>W_h*%0WdO#O-7nQb zr0^TK?d!(GBG~Ur(jTq6Jyj@Q7y3QSd~mA@etLy5EK@x&(Xk1scqcZj6|TDl^4jhW zy7IDS;l`!l?jL##)D7IK5Uur|5k=+@ljBhL!#b0R0pbJa6?#(dG+ZfoDR;0j!q{11 z=IoozC(BrBz4q8=Mf#4824Fv`x^w41IX71{Pt%&^38+3|AOHSNe4+)jXLzWsW6IsCJI zw{u&vBM*_E@!JXYu}#6cIso3SFTmDK936M14Y}nfJD`|0kB>DO-m&5M~`gWjTyfi(~r!ycT_Qc?b(a_@U5A$eqy6*QS6ND zp!FKu>C{z&lX1#Xl1nH6>-gnKc9zhj9}m&jR&+2?xKWm_qY z0gsZ8E$y;UI+pwLe$(=I%2Mfw_>BE^=aUYV2EQLfR$yd7s6`O~ZE8gM8ucU+o?Ig!9MQT|r1*A_= z#x!v^eK8m~#mO92BL=U%%-3*EkJY{j5JnhV8iUhFga^c(#L$FG#%SQOd{49Q^12({ z$lk%-NL1yneWBr4&8j)U+e;U)8vcp5e83MdE6o>J#73xvf?R>r-Zsi!WPxR5m0PauXL8?7?GBX@Au@|knaY#f+1o&Pg`O-7P_1wbgc-$Vmnt%|zI5l|X@}r;PDM0Eo6;hq}!PN=WM|6{eBfzu1wL;>BVa%sse zDcj7~KVHI!;3SPNIFDga&tHNU^h&d519ECKR!AcF3R!e<#Y4-2Fm}0L`?1vTDPQjFiZ_4} zLmQ=T=h2rQje({%BydJgHLY`?+ldJu?beGE3hvV95F9gd8DpAOAZ!jlY0bB(PIB9J zG*`jb@^{Q$(fe{KcrUxF{@MvZ=r`P3z-@;&`FhvMhN)KC?F$ZP^lTRGd~7*KqPitU zOlf(I7^Hx7s5S0cgSwJ_Q?d_{MUw(r0R05|?!tIL+~_Vc z^_*ed)l06wltbn|GvrzO9};@<u(0d&amGM?s%&;g4VbSx(I++xl5Jt2EI&DtBT6}=d9vJIKU;(LtE&{_ zTY#|cx++EZ=#GwWgjeQpAZbpK%gJ3#lGdS=1P=Ev>~uB#;1)Fev0RlJdwLhoS;oy|`xwPBGV`<3?3f7qxe3ySYwFr}R_R8^yn2ld{9APa3B_8)QAAaG?z0*5< ztz#{+^vgO(NH|u*j^`5f$RDi!eege-DDUUY)V60E6MfE)$N`Dv7N~aQ*5WDc-FEyc z@-Az(Wi0>IEGuYQCwA$kjYr@FkSs}e3jhXR_N(zye?(Xw37U&m27w;PIggGP7VGg= s-uI2RsjE^&XnCC7Ba230Zy-^a?l+l3g$E1(Mgd(sYkj8d^vz%YAB;4$SO5S3 literal 0 HcmV?d00001 diff --git a/docs/quick_reference.html b/docs/quick_reference.html index 77ae4da..abbf267 100644 --- a/docs/quick_reference.html +++ b/docs/quick_reference.html @@ -50,8 +50,8 @@

            Quick Reference

            -

            If you are familiar with mini.css and want a cheat sheet, you've come to the right place. Below you will find a quick overview of the framework and examples to help you brush up on your website-building skills. For more detailed instructions on modules, check out the modules page.

            -

            All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.


            +

            If you are familiar with mini.css and want a cheat sheet, you've come to the right place. Below you will find a quick overview of the framework and examples to help you brush up on your website-building skills. For more detailed instructions on modules, check out the modules page.

            +

            All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.


            @@ -59,17 +59,17 @@

            Setup & usage

            -

            You can download mini.css using npm, yarn or Bower:

            +

            You can download mini.css using npm, yarn or Bower:

            npm install mini.css
            yarn add mini.css
            bower install mini.css

            -

            You can import the default flavor of mini.css in your webpage by simply adding one of the following references inside your HTML page's <head> tag:

            +

            You can import the default flavor of mini.css in your webpage by simply adding one of the following references inside your HTML page's <head> tag:

            <link rel="stylesheet" href="https://gitcdn.link/repo/Chalarangelo/mini.css/master/dist/mini-default.min.css">
            <link rel="stylesheet" href="https://cdn.rawgit.com/Chalarangelo/mini.css/v2.2.0/dist/mini-default.min.css">

            -

            You can also find mini.css on cdnjs, which you can use to include it in your projects.


            -

            We strongly suggest you add the following line inside your HTML page's <head> to utilize the viewport meta tag:

            +

            You can also find mini.css on cdnjs, which you can use to include it in your projects.


            +

            We strongly suggest you add the following line inside your HTML page's <head> to utilize the viewport meta tag:

            <meta name="viewport" content="width=device-width, initial-scale=1">
            @@ -91,7 +91,7 @@

            Typography

            -
              +
              • Basic reset and fix rules applied, based on Normalize.css v5.0.0
              • A native font stack is used
              • The colors are set to background: #f5f5f5; and color: #212121;
                • @@ -200,7 +200,7 @@

            Notes

            -
              +
              • Based on the Flexbox Layout Module
              • Grid structured as follows:
                  @@ -210,7 +210,7 @@
              • SCR_SZ values: -
                  +
                  • sm for screens below 768px wide
                  • md for screens between 768px(inclusive) and 1280px(exclusive)
                  • lg for screens wider than 1280px
                    • @@ -250,7 +250,7 @@

            Notes

            -
              +
              • Apply multiple column classes to the same element, one for each screen size, to define different layouts
              • Mobile-first approach, styles specified for smaller screen sizes apply to larger screen sizes if no override is specified
              • Try to make page content vertical for smaller devices, using .col-sm-12 and transition to two or three columns on larger screen sizes
                • @@ -274,7 +274,7 @@

            Notes

            -
              +
              • Available both as fluid column layouts, using .cols-SCR_SZ, replacing SCR_SZ with one of the available screen size names and fixed width column layouts, using .col-SCR_SZ-COL_WD, replacing SCR_SZ with one of the available screen size names and COL_WD with a number from 1 to 12 specifying the width of the columns
              • Can define screen-specific predefined layouts
              • Can be combined with offsets and reordering, but not normal grid layout classes
                • @@ -310,7 +310,7 @@

            Notes

            -
              +
              • Create offsets using the .col-SCR_SZ-offset-COL_WD classes
              • COL_WD can be any integer from 0 to 11 (both inclusive)
              • You can mix offset columns and non-offset columns
                • @@ -336,7 +336,7 @@

            Notes

            -
              +
              • Create reorders using .col-SCR_SZ-first, .col-SCR_SZ-last and .col-SCR_SZ-normal classes for first, last and normal ordering respectively
              • Default ordering is based on order of appearance
              • Specify reorders in combination with existing column styling, not instead
                • @@ -361,7 +361,7 @@

            Notes

            -
              +
              • Not a new component, rather a popular pattern
              • Use two columns, one for the media (i.e. <img>) and one for the textual content
              • Compatible with most elements
                • @@ -398,7 +398,7 @@

            Notes

            -
              +
              • Link <label> elements to their respective <input> elements for ease-of-use
              • Use of the <fieldset> and <legend> elements is highly recommended
              • Forms are inline by default, use .input-group to align elements inside them
                • @@ -425,7 +425,7 @@

            Notes

            -
              +
              • Pre-styled using the checkbox hack, fully accessible
              • Create a <div class="input-group"> containing the checkbox or radio button along with its linked label
              • Add tabindex="0" to the <input> element to make full accessible
                • @@ -459,7 +459,7 @@

            Notes

            -
              +
              • All button types have been stylized
              • Button styles are available for other elements, using the .button class or the role="button" attribute
              • .primary, .secondary, .tertiary and .inverse color variants
                • @@ -479,7 +479,7 @@

            Notes

            -
              +
              • Link an <input type="file"> element to a <label>
              • The file button will not change text when uploading a file, Javascript may be required
              • Compatible with .input-group
                • @@ -507,7 +507,7 @@

            Notes

            -
              +
              • Use the .logo class for the first child (either textual element or image)
              • The rest of the elements inside the <header> must be button elements (i.e. <button>, <input type="button">, role="button" or .button)
              • Use <span> elements as separators
                • @@ -535,7 +535,7 @@

            Notes

            -
              +
              • Use <nav> element, populate it with links
              • Use .sublink-1 and .sublink-2 classes to create subcategories in your navigation menu
              • Combine the navigation bar with grid reordering to display aside from text on larger displays or at the bottom on smaller displays
                • @@ -557,7 +557,7 @@

            Notes

            -
              +
              • Structure as follows:
                1. <label> element with the .drawer-toggle class in the <header> element, linked to the id of the <input type="checkbox"> used to toggle the drawer component
                2. <input type="checkbox"> element with a unique id
                  3. @@ -580,7 +580,7 @@

            Notes

            -
              +
              • Simple syntax and structure, add content as normal
            @@ -598,7 +598,7 @@

          Notes

          -
            +
            • Use .sticky class to create
            • Compatible with modern browsers, support for position:sticky is growing
            @@ -644,7 +644,7 @@

          Notes

          -
            +
            • Table structure is as follows:
              1. <table> element is the table's root element
                2. @@ -694,7 +694,7 @@

          Notes

          -
            +
            • Use the .horizontal class to make a <table> horizontal
            • Does not support the <tfoot> element
            • Horizontal tables might not be fully compatible with older browsers
              • @@ -746,7 +746,7 @@

          Notes

          -
            +
            • Use the .striped class to make a <table> striped
            • Use the .preset class to make a <table> to create matrices or otherwise preset tables
            • Preset matrix tables might require some CSS tweaks to deal with border styling errors
              • @@ -781,7 +781,7 @@

          Notes

          -
            +
            • Requires familiarity with the grid module
            • Card structure as follows:
                @@ -810,7 +810,7 @@

          Notes

          -
            +
            • Create media sections for images or video, using the .media class
            • Color variants for sections are available using the .dark and .darker classes
            • Extra padding section variant available using the .double-padded class
              • @@ -844,7 +844,7 @@

          Notes

          -
            +
            • Card size variants available using the .large and .small classes
            • Fluid cards available using the .fluid class, require the use of grid columns
            • Fluid cards might not display properly in older browsers and will sometimes slightly disrespect margins on certain layouts
              • @@ -869,7 +869,7 @@

          Notes

          -
            +
            • Create yellow warning cards, using the .warning class
            • Create red error cards, using .error class
            • Avoid combining two or more card color variants
              • @@ -909,7 +909,7 @@

          Notes

          -
            +
            • Tabs structure as follows:
              1. .tabs element is the outermost wrapper of the tabbed layout
                2. @@ -957,7 +957,7 @@

          Notes

          -
            +
            • Use the .stacked class to create stacked tabs
            • Use aria-hidden="true" to input elements in order to add accessibility
            • Use either checkboxes or radio buttons as the <input> elements of stacked tabs
              • @@ -983,7 +983,7 @@

          Notes

          -
            +
            • Use the <mark> element for highlighting text
            • .secondary and .tertiary classes offer color variants
            • Highlighted text is inline by default, use the .inline-block class for longer text highlights
              • @@ -1002,7 +1002,7 @@

          Notes

          -
            +
            • Use the .toast class on <span> elements to create toast messages
            • Size variants available using the .small and .large classes
            • Toasts have no pre-defined behavior, use Javascript
              • @@ -1018,7 +1018,7 @@

          Notes

          -
            +
            • Create using the .tooltip class
            • Put tooltip text in the aria-label attribute's value
            • Use the .bottom class to make a tooltip display at the bottom of its context
              • @@ -1041,7 +1041,7 @@

          Notes

          -
            +
            • Use the <progress> element to create progress bars
            • Set max="1000" and a value between 0 and 1000
            • Do not use floating point values for the progress bar
              • @@ -1057,7 +1057,7 @@

          Notes

          -
            +
            • Color variants available using the .secondary and .tertiary classes
            • Inline variant available using the .inline class
            • Mix color and size variants, but not multiple of the same type
              • @@ -1071,7 +1071,7 @@

          Notes

          -
            +
            • Use the .spinner-donut class to create donut spinners
            • Apply class to a <div> or <span> element
            • Do not insert text inside the .spinner-donut element
              • @@ -1089,7 +1089,7 @@

          Notes

          -
            +
            • Color variants available using the .secondary and .tertiary classes
            • Alternate size available using the .large class
            • You can mix color variants with the .large class, but not with each other
              • @@ -1111,7 +1111,7 @@

          Notes

          -
            +
            • Use .hidden to hide elements
            • Use .visually-hidden to show elements only in screen readers
            • Both classes use !important declarations
              • @@ -1129,7 +1129,7 @@

          Notes

          -
            +
            • Create generic borders using .bordered
            • Rounded and circular border radii available using .rounded and .circular classes
            • Generic shadows available using the .shadowed class
              • @@ -1147,7 +1147,7 @@

          Notes

          -
            +
            • Use the .responsive-padding and .responsive-margin classes to apply responsive padding or margin respectively to any element
            • The two classes can be combined
            • Both classes use !important declarations
              • @@ -1167,10 +1167,10 @@

          Notes

          -
            +
            • Use the .hidden-SCR_SZ or .visually-hidden-SCR_SZ syntax, replacing SCR_SZ with one of the available screen size names
            • SCR_SZ values: -
                +
                • sm for screens below 768px wide
                • md for screens between 768px(inclusive) and 1280px(exclusive)
                • lg for screens wider than 1280px
                  • @@ -1192,7 +1192,7 @@

          Notes

          -
            +
            • To create breadcrumbs, create a <ul> element implementing the .breadcrumbs class
            • Do not use <ol> for breadcrumbs
            • Do not nest lists inside the .breadcrumbs
              • @@ -1207,7 +1207,7 @@

          Notes

          -
            +
            • Use the .close class to create a close icon
            • Use a <span> or <div> element to create a close icon
            • Use a button element implementing the .close class to stylize the close icon as a button
              • @@ -1223,6 +1223,6 @@
        - + diff --git a/docs/tab.html b/docs/tab.html index 039ffe9..99a337f 100644 --- a/docs/tab.html +++ b/docs/tab.html @@ -81,8 +81,8 @@

        Tab

        -

        The tab module aims to combine multiple components and design paradigms, like collapses, accordions, carousels and tabs, into one general-purpose component. Tabs are very simple in structure, responsive on mobile and they allow for layout customization so that you can turn them into accordions or collapses whenever you want.

        -

        All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.


        +

        The tab module aims to combine multiple components and design paradigms, like collapses, accordions, carousels and tabs, into one general-purpose component. Tabs are very simple in structure, responsive on mobile and they allow for layout customization so that you can turn them into accordions or collapses whenever you want.

        +

        All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.


        @@ -90,11 +90,11 @@

        Quick overview

        -

        Spoilers, collapses, accordions, tabs, carousels have been a staple of modern design for quite a long time. All of these elements are implemented using the tab module's single generic container. The tab container replaces all of these design paradigms with one component that is very flexible and responsive in order to let you present your website or app's content any way you like. Tabbed navigation is very easy to implement, while collapse, accordion and carousel components use the stacked architecture of tabs. As usual, the tab container is responsive and accessible, allowing you to deliver your content properly to all devices and users.


        +

        Spoilers, collapses, accordions, tabs, carousels have been a staple of modern design for quite a long time. All of these elements are implemented using the tab module's single generic container. The tab container replaces all of these design paradigms with one component that is very flexible and responsive in order to let you present your website or app's content any way you like. Tabbed navigation is very easy to implement, while collapse, accordion and carousel components use the stacked architecture of tabs. As usual, the tab container is responsive and accessible, allowing you to deliver your content properly to all devices and users.


        Quick start

        -

        To use the tab module, simply include the link to the flavor you are using and start writing your HTML page as usual. One suggestion we will make is to add the following line inside your HTML page's <head> to utilize the viewport meta tag:

        +

        To use the tab module, simply include the link to the flavor you are using and start writing your HTML page as usual. One suggestion we will make is to add the following line inside your HTML page's <head> to utilize the viewport meta tag:

        <meta name="viewport" content="width=device-width, initial-scale=1">

        @@ -122,8 +122,8 @@
      -

      The tab container's basic sytanx is composed of two components, presented below in the order they should be added to the DOM tree:

      -
        +

        The tab container's basic sytanx is composed of two components, presented below in the order they should be added to the DOM tree:

        +
        • At the outermost level of the tab container is a <div> element implementing the .tabs class. This serves as the wrapper of the tab container.
        • Inside the .tabs container, add a set of the following three elements for each tab:
            @@ -133,7 +133,7 @@
        -

        Tabs are responsive and will collapse into a stacked display on smaller screens, allowing the user to view the actual content more easily. The tab container's syntax is accessible, but parts of it might confuse screen readers, so we suggest adding the aria-hidden="true" attribute to all the <input> and <label> elements inside the .tabs container.

        +

        Tabs are responsive and will collapse into a stacked display on smaller screens, allowing the user to view the actual content more easily. The tab container's syntax is accessible, but parts of it might confuse screen readers, so we suggest adding the aria-hidden="true" attribute to all the <input> and <label> elements inside the .tabs container.

        Sample code

        <div class="tabs">
   <input type="radio" name="tab-group" id="tab1" checked aria-hidden="true">
@@ -159,7 +159,7 @@

      Notes

      -
        +
        • Tabs are compatible with modern browsers, but might not display properly in older browsers.
        • Remember to add the checked attribute to one of your <input>s if you want that tab to be the one displayed by default. If none is specified, the first one will be displayed.
        • The height of the tab container's panel area is 400px. If you want to change this default size, please check out the customization page.
          • @@ -174,7 +174,7 @@ <h3>Bad Tab</h3> </div> </div> -

          Don't: Do not use checkboxes inside the default .tabs container, otherwise you might notice unexpected behavior. If you want to use an <input type="checkbox">, check out the next section.

          +

          Don't: Do not use checkboxes inside the default .tabs container, otherwise you might notice unexpected behavior. If you want to use an <input type="checkbox">, check out the next section.

      <div class="tabs">
@@ -184,7 +184,7 @@
     <h3>Lonely Tab</h3>
   </div>
 </div>
      -

      Don't: You can add a single tab in a .tabs container, but what use would that be? You should probably read the next section to see what you can do with a stacked tab container instead.

      +

      Don't: You can add a single tab in a .tabs container, but what use would that be? You should probably read the next section to see what you can do with a stacked tab container instead.

      <div class="tabs">
@@ -199,7 +199,7 @@
     <h3>Bad Tab</h3>
   </div>
 </div>
      -

      Don't: The syntax and structure of the tab container is very strict. Try to follow it exactly as described in this section.

      +

      Don't: The syntax and structure of the tab container is very strict. Try to follow it exactly as described in this section.

      <div class="tabs">
@@ -209,7 +209,7 @@
     <h3>Not fully accessible tab</h3>
   </div>
 </div>
      -

      Don't: Remember to use the aria-hidden="true" attribute to make your tabs fully accessible.

      +

      Don't: Remember to use the aria-hidden="true" attribute to make your tabs fully accessible.

      @@ -240,7 +240,7 @@
-

Apart from the normal tab layout, you can make your tabs stacked instead, using the .stacked class in your .tabs container element. Stacked tabs are more versatile, allowing you to use checkboxes and/or radio buttons to implement collapses, accordions and spoilers. Carousel-styled elements can also be displayed in this fashion, if you wish. Remember to use the aria-hidden="true" attribute to make your tabs fully accessible, as before.

+

Apart from the normal tab layout, you can make your tabs stacked instead, using the .stacked class in your .tabs container element. Stacked tabs are more versatile, allowing you to use checkboxes and/or radio buttons to implement collapses, accordions and spoilers. Carousel-styled elements can also be displayed in this fashion, if you wish. Remember to use the aria-hidden="true" attribute to make your tabs fully accessible, as before.

Sample code

<div class="tabs stacked">
   <input type="radio" name="accordion" id="a1" checked aria-hidden="true">
@@ -273,7 +273,7 @@

Notes

-
    +
    • .stacked tabs can be used with either checkboxes or radio buttons.
    • You can mix and match checkboxes and radio buttons, but we suggest you do not do so, unless you think it is necessary for your design.
    @@ -286,7 +286,7 @@ <p>This is a singular collapse.</p> </div> </div> -

    Do: You can implement single collapses (otherwise known as spoilers), using a .tabs.stacked container with only one checkbox-based tab.

    +

    Do: You can implement single collapses (otherwise known as spoilers), using a .tabs.stacked container with only one checkbox-based tab.

<div class="tabs stacked">
@@ -296,7 +296,7 @@
     <p>This accordion section cannot close once opened</p>
   </div>
 </div>
-

Don't: Avoid having a single radio-based tab in a .tabs.stacked container, as this might result in unexpected behavior.

+

Don't: Avoid having a single radio-based tab in a .tabs.stacked container, as this might result in unexpected behavior.

@@ -305,10 +305,10 @@
-

If you want to learn more about mini.css's modules, go back to the modules page and choose another module to see its documentation.

+

If you want to learn more about mini.css's modules, go back to the modules page and choose another module to see its documentation.

- + diff --git a/docs/table.html b/docs/table.html index d6b2d85..abcc985 100644 --- a/docs/table.html +++ b/docs/table.html @@ -87,8 +87,8 @@

Table

-

The table module provides styling and responsiveness for tables. Simple rules and accessible design paradigms have been used to make creating tables quick and easy. Large tables will collapse to cards when on smaller devices or, if you don't want that, they can be locked into their default, desktop view.

-

All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.


+

The table module provides styling and responsiveness for tables. Simple rules and accessible design paradigms have been used to make creating tables quick and easy. Large tables will collapse to cards when on smaller devices or, if you don't want that, they can be locked into their default, desktop view.

+

All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.


@@ -96,11 +96,11 @@

Quick overview

-

Presenting information the right way is very important, especially so when dealing with large amounts of data. The table module reinvents tabular data presentation, using modern styling and responsiveness to help make tables fun again for all users no matter the device size. Tables can be either vertical or horizontal, both collapsing to a card view on smaller devices, so that they are easier to view properly. Horizontal tables are also flexible, allowing you to take as little space as possible, while still providing your users with a pleasant way to view their data. Finally, like in most CSS frameworks nowadays, you can stripe your tables to make reading them slightly less tiresome for your users' eyes. Note that all of the table variants are fully accessible.


+

Presenting information the right way is very important, especially so when dealing with large amounts of data. The table module reinvents tabular data presentation, using modern styling and responsiveness to help make tables fun again for all users no matter the device size. Tables can be either vertical or horizontal, both collapsing to a card view on smaller devices, so that they are easier to view properly. Horizontal tables are also flexible, allowing you to take as little space as possible, while still providing your users with a pleasant way to view their data. Finally, like in most CSS frameworks nowadays, you can stripe your tables to make reading them slightly less tiresome for your users' eyes. Note that all of the table variants are fully accessible.


Quick start

-

To use the table module, simply include the link to the flavor you are using and start writing your HTML page as usual. One suggestion we will make is to add the following line inside your HTML page's <head> to utilize the viewport meta tag:

+

To use the table module, simply include the link to the flavor you are using and start writing your HTML page as usual. One suggestion we will make is to add the following line inside your HTML page's <head> to utilize the viewport meta tag:

<meta name="viewport" content="width=device-width, initial-scale=1">

@@ -142,8 +142,8 @@
-

Table layout utilizes the <table> HTML element with the following structure (usual tabular structure):

-
    +

    Table layout utilizes the <table> HTML element with the following structure (usual tabular structure):

    +
    1. On the outermost level, there is the <table> element.
    2. If you want to include a <caption> element, it must by the first element inside the <table> element.
    3. Following the above, you need to add a <thead> element. Inside it, you should usually add one <tr> element, which contains one or more <th> elements.
      4. @@ -194,7 +194,7 @@ <td>Wilberts</td> <td>MrOne</td> </tr> -

      Don't: Remember to always add a data-label attribute to your <td> elements, as the table's card view is very dependent on them to display properly. <th> elements, however, do not require or utilize this attribute.

      +

      Don't: Remember to always add a data-label attribute to your <td> elements, as the table's card view is very dependent on them to display properly. <th> elements, however, do not require or utilize this attribute.

<table>
@@ -209,7 +209,7 @@
     <!-- ... -->
   </tfoot>
 </table>
-

Don't: The <tfoot> element must always be immediately after the <thead> element, if included.

+

Don't: The <tfoot> element must always be immediately after the <thead> element, if included.

<tbody>
@@ -218,7 +218,7 @@
     <td data-label="Name">Chad</td>
   </tr>
 </tbody>
-

Don't: Avoid inserting <th> elements inside your <tbody> element. If you want to make your tables horizontal or preset their styling in a manner different from the one shown in the previous examples, check the below sections.

+

Don't: Avoid inserting <th> elements inside your <tbody> element. If you want to make your tables horizontal or preset their styling in a manner different from the one shown in the previous examples, check the below sections.

<thead>
@@ -226,7 +226,7 @@
     <td data-label="Name">Chad</td>
   </tr>
 </thead>
-

Don't: Avoid using <td> elements inside your <thead>. You should use a <tbody> element instead.

+

Don't: Avoid using <td> elements inside your <thead>. You should use a <tbody> element instead.

@@ -257,7 +257,7 @@
-

Horizontal tables can be created, by simply adding the .horizontal class to the root element of your table (i.e. the <table> element). Horizontal tables are flexible, so they can accommodate any amount of data rows and, if there is a lot of data, they will make their overflow scrollable. Remember to add the data-label attribute, as shown in the previous section, to allow your tables to be responsive without any errors. Keep in mind, however, that .horizontal tables do not support the <tfoot> element.

+

Horizontal tables can be created, by simply adding the .horizontal class to the root element of your table (i.e. the <table> element). Horizontal tables are flexible, so they can accommodate any amount of data rows and, if there is a lot of data, they will make their overflow scrollable. Remember to add the data-label attribute, as shown in the previous section, to allow your tables to be responsive without any errors. Keep in mind, however, that .horizontal tables do not support the <tfoot> element.

Sample code

<table class="horizontal">
   <caption>People</caption>
@@ -290,7 +290,7 @@

Notes

-
    +
    • Due to .horizontal tables utilizing the Flexbox Layout, some older browsers may not properly display these tables. This is especially true with legacy versions of Internet Explorer.
    • Mixing the Flexible Layout Module with <table> elements seems to upset some browsers. We noticed this on an older mobile version of Firefox, where our implementation should work in theory, given the fact that both features are properly supported. If you notice any problems with .horizontal tables, feel free to submit a new issue on Github.
    @@ -303,7 +303,7 @@ <!-- ... --> </tfoot> </table> -

    Don't: We already explicitly stated that, due to the way .horizontal tables are styled, the <tfoot> element is not supported. Please refer to the next section if you need to use this element and you want to have a horizontal table layout.

    +

    Don't: We already explicitly stated that, due to the way .horizontal tables are styled, the <tfoot> element is not supported. Please refer to the next section if you need to use this element and you want to have a horizontal table layout.

@@ -329,7 +329,7 @@
-

Tables are responsive by default, however you can disable this functionality for one or more tables (normal or .horizontal), using the .preset class. This class can also be used for a multitude of things, like dealing with tables not allowing you to have <th> elements inside the <tbody> element, building matrices (i.e. tables with a header column and a header row) etc. Finally, you can make your tables use a different color for every other row, using the .striped class.

+

Tables are responsive by default, however you can disable this functionality for one or more tables (normal or .horizontal), using the .preset class. This class can also be used for a multitude of things, like dealing with tables not allowing you to have <th> elements inside the <tbody> element, building matrices (i.e. tables with a header column and a header row) etc. Finally, you can make your tables use a different color for every other row, using the .striped class.

Sample code

The sample code is a bit lengthy, so we hid it by default to make it easier for mobile device users to read this page. Click or tap on Show sample code below to see the code sample for this example. By the way, we present a sample for a matrix table in he first example, but you can use the same principles and classes to create any table layout you wish.


@@ -379,7 +379,7 @@

Notes

-
    +
    • Making a table .striped also affects the color of the cards in their responsive view on mobile devices.
    • If you create a .preset table, which you do not want to alter via Javascript to be responsive at any time in the future, you can omit the data-label attributes.
    @@ -399,7 +399,7 @@ <!-- ... --> </tbody> </table> -

    Do: The first row in a preset matrix table or any table without a <thead> element will have an extra border at the top. You can use a generic class to set border-to: 0; for the elements inside that row to fix this.

    +

    Do: The first row in a preset matrix table or any table without a <thead> element will have an extra border at the top. You can use a generic class to set border-to: 0; for the elements inside that row to fix this.

<table class="horizontal preset">
@@ -417,7 +417,7 @@
 <table class="preset horizontal striped">
   <!-- ... ->
 </table>
-

Do: You can combine any two of the following classes without any problems: .horizontal, .preset, .striped. Just make sure you respect each one's specific rules.

+

Do: You can combine any two of the following classes without any problems: .horizontal, .preset, .striped. Just make sure you respect each one's specific rules.

@@ -426,10 +426,10 @@
-

If you want to learn more about mini.css's modules, go back to the modules page and choose another module to see its documentation.

+

If you want to learn more about mini.css's modules, go back to the modules page and choose another module to see its documentation.

- + diff --git a/docs/templates.html b/docs/templates.html index c2b9e64..444878c 100644 --- a/docs/templates.html +++ b/docs/templates.html @@ -42,53 +42,54 @@

Templates

-

Getting started with mini.css is reasonably easy, however sometimes you need a couple of examples or templates to figure out the optimal way to design your website or app. To help you get started, we maintain a handful of templates that can help you quickstart your projects without having to read the full documentation.


+

Getting started with mini.css is reasonably easy, however sometimes you need a couple of examples or templates to figure out the optimal way to design your website or app. To help you get started, we maintain a handful of templates that can help you quickstart your projects without having to read the full documentation.


    +
  • + +

    Full website template

    +

    A complete sample website created using the grid system of mini.css, cards, navigational elements and input contrls. The website consists of three pages, each showcasing different modules and patterns. The homepage and blog post showcase the typography styling and emphasize the importance of the grid system and the card module, while the contact form showcases the forms, buttons and other input controls. The sample website is fully responsive, changing layout based on screen size, while all of the code is carefully documented, implementing certain patterns and tricks that can be very useful when designing a website.

    +

  • See the Pen Single Column Template (mini.css) by Angelos Chalaris (@chalarangelo) on CodePen.

    Single column template

    -

    The most basic layout template for a blog or website consists of a sticky header, one column used to display content and a footer at the bottom of the page. This template uses the grid system of mini.css, along with its navigational elements to provide a simple responsive website design, that you can use to display content across devices without the need for any changes in the layout.

    +

    The most basic layout template for a blog or website consists of a sticky header, one column used to display content and a footer at the bottom of the page. This template uses the grid system of mini.css, along with its navigational elements to provide a simple responsive website design, that you can use to display content across devices without the need for any changes in the layout.

  • See the Pen Two Column Template (mini.css) by Angelos Chalaris (@chalarangelo) on CodePen.

    Two-column template

    -

    Another common layout template for blogs and websites consists of a sticky header, a footer and two columns for displaying content. Like in most templates, the grid system of mini.css is used to provide an easy way to create columns and make them responsive across multiple screen sizes and devices.

    +

    Another common layout template for blogs and websites consists of a sticky header, a footer and two columns for displaying content. Like in most templates, the grid system of mini.css is used to provide an easy way to create columns and make them responsive across multiple screen sizes and devices.

  • See the Pen Three Column Template (mini.css) by Angelos Chalaris (@chalarangelo) on CodePen.

    Three-column template

    -

    Last but not least, the three-column website layout template is better used in websites with a lot of content. The grid system of mini.css provides an easy solution to handling lots of content on multiple screen sizes and devices, making the content responsive. Finally, as in most templates, navigational elements such as sticky headers and foooters are used to complete the template.

    +

    Last but not least, the three-column website layout template is better used in websites with a lot of content. The grid system of mini.css provides an easy solution to handling lots of content on multiple screen sizes and devices, making the content responsive. Finally, as in most templates, navigational elements such as sticky headers and foooters are used to complete the template.

  • See the Pen Card Showcase Template (mini.css) by Angelos Chalaris (@chalarangelo) on CodePen.

    Card showcase template

    -

    Card-based website layout templates are another common need, as many websites utilize a tile system to display lots of smaller pieces of content. Using the card and grid modules of mini.css, along with a couple of navigational elements, it's really easy to create a responsive website with lots of cards containing small pieces of content, such as a showcase for a website, a photo album or an article browser.

    +

    Card-based website layout templates are another common need, as many websites utilize a tile system to display lots of smaller pieces of content. Using the card and grid modules of mini.css, along with a couple of navigational elements, it's really easy to create a responsive website with lots of cards containing small pieces of content, such as a showcase for a website, a photo album or an article browser.

  • See the Pen Login Form Template (mini.css) by Angelos Chalaris (@chalarangelo) on CodePen.

    Login form template

    -

    Login forms are one of the most commonly used elements in any website design. Using the input_control and grid modules of mini.css, along with a couple of navigational elements and a couple of optional tricks, it's really easy to create a responsive login form with the required fields and buttons.

    +

    Login forms are one of the most commonly used elements in any website design. Using the input_control and grid modules of mini.css, along with a couple of navigational elements and a couple of optional tricks, it's really easy to create a responsive login form with the required fields and buttons.

  • See the Pen Android App Template (mini.css) by Angelos Chalaris (@chalarangelo) on CodePen.

    Android app template

    -

    Web application layout templates are pretty popular these days, especially ones that look and feel like native Android apps. Utilizing some clever CSS tricks, the grid module and navigational elements from mini.css, we created a pretty simple app template, complete with a call-to-action button and header bar, making it look quite similar to a native Android app and display properly across multiple devices.

    +

    Web application layout templates are pretty popular these days, especially ones that look and feel like native Android apps. Utilizing some clever CSS tricks, the grid module and navigational elements from mini.css, we created a pretty simple app template, complete with a call-to-action button and header bar, making it look quite similar to a native Android app and display properly across multiple devices.

  • See the Pen Tabbed App Template (mini.css) by Angelos Chalaris (@chalarangelo) on CodePen.

    Tabbed app template

    -

    A single page application layout template can be built using many things, but tabbed web applications are one of our favorites. Utilizing the tab module of mini.css and some CSS tricks, we created a simple single page app template with three tabs, containing different content. The template will switch to a stacked view on smaller devices, although if you add more than three tabs, you will have to alter a couple of values to make sure that everything fits nicely on the screen.

    +

    A single page application layout template can be built using many things, but tabbed web applications are one of our favorites. Utilizing the tab module of mini.css and some CSS tricks, we created a simple single page app template with three tabs, containing different content. The template will switch to a stacked view on smaller devices, although if you add more than three tabs, you will have to alter a couple of values to make sure that everything fits nicely on the screen.


-
-
-
-
- + diff --git a/docs/utility.html b/docs/utility.html index c615f4c..fe2b9c6 100644 --- a/docs/utility.html +++ b/docs/utility.html @@ -82,8 +82,8 @@

Utility

-

The utility module contains all the utilities and helper classes that you might want when designing a website or application. They solve common design problems efficiently and provide you with generic rules you can easily apply everywhere.

-

All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.


+

The utility module contains all the utilities and helper classes that you might want when designing a website or application. They solve common design problems efficiently and provide you with generic rules you can easily apply everywhere.

+

All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.


@@ -91,11 +91,11 @@

Quick overview

-

Every website or app has different needs and no CSS framework can predict them all. The utility module addresses this issue by providing you with a handful of utility and helper classes to make common, repetitive declarations easier. These classes include, but are not limited to, generic border styling and shadows, some responsive sizing and spacing utilities and a few other things, like a close icon, breadcrumbs styling and visiblity helpers for screen readers.


+

Every website or app has different needs and no CSS framework can predict them all. The utility module addresses this issue by providing you with a handful of utility and helper classes to make common, repetitive declarations easier. These classes include, but are not limited to, generic border styling and shadows, some responsive sizing and spacing utilities and a few other things, like a close icon, breadcrumbs styling and visiblity helpers for screen readers.


Quick start

-

To use the utility module, simply include the link to the flavor you are using and start writing your HTML page as usual. One suggestion we will make is to add the following line inside your HTML page's <head> to utilize the viewport meta tag:

+

To use the utility module, simply include the link to the flavor you are using and start writing your HTML page as usual. One suggestion we will make is to add the following line inside your HTML page's <head> to utilize the viewport meta tag:

<meta name="viewport" content="width=device-width, initial-scale=1">

@@ -107,7 +107,7 @@

Visibility helpers

-

You can hide content for all your users, using the default hidden attribute. However, we provide you with the .hidden class for the same purpose, as well as the .visually-hidden class which will make your content hidden, except for screen readers.

+

You can hide content for all your users, using the default hidden attribute. However, we provide you with the .hidden class for the same purpose, as well as the .visually-hidden class which will make your content hidden, except for screen readers.

Sample code

<span class="hidden">Hidden text</span>
 <span class="visually-hidden">Screen-reader-only text</span>
@@ -115,13 +115,13 @@

Notes

-
    +
    • Both classes utilize !important declarations, so be careful when and how to use them.
    <span class="hidden visually-hidden">Not a good idea</span>
    -

    Don't: Avoid using both classes at the same time. Instead, use .hidden to hide content for all users, .visually-hidden to hide it for non-screen-reader users or aria-hidden="true" to hide it for screen-reader-only users.

    +

    Don't: Avoid using both classes at the same time. Instead, use .hidden to hide content for all users, .visually-hidden to hide it for non-screen-reader users or aria-hidden="true" to hide it for screen-reader-only users.

@@ -143,7 +143,7 @@
-

Use the .bordered class to apply a generic black border with 25% opacity to any element. Apart from that you can use the .rounded and .circular classes to create generic border radiuses. Finally, you can use the .shadowed class to add a generic box-shadow to any element.

+

Use the .bordered class to apply a generic black border with 25% opacity to any element. Apart from that you can use the .rounded and .circular classes to create generic border radiuses. Finally, you can use the .shadowed class to add a generic box-shadow to any element.

Sample code

<span class="bordered">Bordered</span>
 <span class="rounded">Rounded</span>
@@ -153,7 +153,7 @@

Notes

-
    +
    • All of these classes utilize !important declarations, so be careful when and how to use them.
    • The .bordered class was originally created with elements such as buttons in mind, to allow users highlighting certain elements in their designs, without having to change any default styles.
    • All of the above classes can be used with most modern HTML elements.
      • @@ -161,13 +161,13 @@ 
      <span class="bordered rounded shadow-small">Stylized element</span>
      -

      Do: You can combine a generic border with any border radius or shadow or even both.

      +

      Do: You can combine a generic border with any border radius or shadow or even both.

      <span class="rounded circular">Bad radius</span>
 <!-- or -->
 <span class="shadow-small shadow-large">Bad shadow</span>
      -

      Don't: Avoid combining two classes of the same type (i.e. two radii or two shadow styles), as they might overwrite each other and cause unexpected behavior.

      +

      Don't: Avoid combining two classes of the same type (i.e. two radii or two shadow styles), as they might overwrite each other and cause unexpected behavior.

@@ -180,7 +180,7 @@

Responsive sizing & spacing classes

-

Helper classes for the padding and margin attributes are provided in the form of .responsive-margin and .responsive-padding classes. Both of these classes are responsive, allowing you to collapse the spacing and size of elements on different displays to make better use of the device's viewport.

+

Helper classes for the padding and margin attributes are provided in the form of .responsive-margin and .responsive-padding classes. Both of these classes are responsive, allowing you to collapse the spacing and size of elements on different displays to make better use of the device's viewport.

Sample code

<div class="responsive-padding">Responsive padding</div>
 <div class="responsive-margin">Responsive margin</div>
@@ -188,14 +188,14 @@

Notes

-
    +
    • If the default values of these classes are not suited to your needs, check out the customization page.
    • Both classes utilize !important declarations, so be careful when and how to use them.
    <div class="responsive-padding responsive-margin">Responsive padding and margin</div>
    -

    Do: You can use both of these classes to make certain element adapt to changes. This could be especially useful for certain grid layouts.

    +

    Do: You can use both of these classes to make certain element adapt to changes. This could be especially useful for certain grid layouts.

@@ -208,7 +208,7 @@

Responsive visibility helpers

-

You can hide content (either fully or only visually) for certain screens, using the responsive visibility helpers. To hide elements completely use the .hidden-SCR_SZ syntax, replacing SCR_SZ with one of the available screen size names (sm for smaller screens, md for medium-sized screens or lg for larger screens). If you want to hide certains elements for all users, except screen readers, replace .hidden with .visually-hidden, followed by the screen size name.

+

You can hide content (either fully or only visually) for certain screens, using the responsive visibility helpers. To hide elements completely use the .hidden-SCR_SZ syntax, replacing SCR_SZ with one of the available screen size names (sm for smaller screens, md for medium-sized screens or lg for larger screens). If you want to hide certains elements for all users, except screen readers, replace .hidden with .visually-hidden, followed by the screen size name.

Sample code

<span class="hidden-sm">Hidden in smaller screens</span>
 <span class="hidden-md">Hidden in medium-sized screens</span>
@@ -221,7 +221,7 @@

Notes

-
    +
    • Responsive visibility helper classes utilize !important declarations, so be careful when and how to use them.
    • The specific breakpoints for small, medium and large screen sizes are as follows:
        @@ -239,11 +239,11 @@ <span class="visually-hidden-md visually-hidden-lg">Visually hidden in medium-sized and larger screens, visible in smaller screens</span> <!-- or --> <span class="hidden-sm visually-hidden-lg">Hidden in smaller screens, visually hidden in larger screens, visible in medium-sized screens</span> -

        Do: You can combine responsive visibility helpers for different sizes, based on your needs.

        +

        Do: You can combine responsive visibility helpers for different sizes, based on your needs.

<span class="hidden-sm visually-hidden-sm">Not a good idea</span>
-

Don't: Avoid combining responsive visibility helpers for the same screen size. Combining both of them might cause unexpected behavior.

+

Don't: Avoid combining responsive visibility helpers for the same screen size. Combining both of them might cause unexpected behavior.

@@ -261,7 +261,7 @@
-

Breadcrumbs are usually used to show the navigational hierarchy of pages or folders. To use them, simply create a <ul> element that implements the .breadcrumbs class. Inside this unordered list, add as many <li> elements as needed to show your hierarchy. You can add links to the list elements, as necessary.

+

Breadcrumbs are usually used to show the navigational hierarchy of pages or folders. To use them, simply create a <ul> element that implements the .breadcrumbs class. Inside this unordered list, add as many <li> elements as needed to show your hierarchy. You can add links to the list elements, as necessary.

Sample code

<ul class="breadcrumbs">
   <li><a href="#">Root</a></li>
@@ -272,7 +272,7 @@

Notes

-
    +
    • The separators between breadcrumbs are added using some tricky CSS rules. Due to that, there might be a few browser versions or devices where you can see part of the seams between the element separators.
    • Breadcrumbs show a hierarchy, an ordered list. However, we do not use the <ol> element, as it might conflict with some custom styles we've seen people use.
    • If you want to add some accesibility to your breadcrumbs, you can add the role="navigation" attribute, although it is not required.
      • @@ -284,7 +284,7 @@ <li><a href="#">Not</a></li> <li>Work</li> </ol> -

      Don't: The structure of the breadcrumb component prohibits the use of <ol> in place of the <ul> element.

      +

      Don't: The structure of the breadcrumb component prohibits the use of <ol> in place of the <ul> element.

<ul class="breadcrumbs">
@@ -295,7 +295,7 @@
   </li>
   <li>File</li>
 </ul>
-

Don't: Avoid nesting lists, breadcrumbs or a combination of the two inside the .breadcrumbs list, as this might cause unexpected behavior.

+

Don't: Avoid nesting lists, breadcrumbs or a combination of the two inside the .breadcrumbs list, as this might cause unexpected behavior.

@@ -315,24 +315,24 @@
-

To create a close icon, simply add an element implementing the .close class.

+

To create a close icon, simply add an element implementing the .close class.

Sample code

<span class="close"></span>

Notes

-
    +
    • The close icon behaves similar to a button when hovering over it or otherwise focusing or selecting it.
    <div class="close"></div>
    -

    Do: You can use a handful of other HTML elements instead of the <span> element showcased in the example above, most commonly <div> elements.

    +

    Do: You can use a handful of other HTML elements instead of the <span> element showcased in the example above, most commonly <div> elements.

    <button class="close"></button>
    -

    Do: If you want your close icon to behave like a button (i.e. register as a button on screen readers and have the required logic attached to it), you can apply the .close class to a <button> element instead. You can even apply any of the button color variant classes.

    +

    Do: If you want your close icon to behave like a button (i.e. register as a button on screen readers and have the required logic attached to it), you can apply the .close class to a <button> element instead. You can even apply any of the button color variant classes.

@@ -341,10 +341,10 @@
-

If you want to learn more about mini.css's modules, go back to the modules page and choose another module to see its documentation.

+

If you want to learn more about mini.css's modules, go back to the modules page and choose another module to see its documentation.

- + diff --git a/docs/v2/DEVLOG.md b/docs/v2/DEVLOG.md index 6c7c19e..f23c726 100644 --- a/docs/v2/DEVLOG.md +++ b/docs/v2/DEVLOG.md @@ -238,7 +238,7 @@ ## 20161102 - Updated `checkbox` and `radio` styles for accesibility. Now they are visible to screen readers. -- Added style for `:hover`, :focus`, `:active` for the `label` elements of the `checkbox` module. +- Added style for `:hover`, `:focus`, `:active` for the `label` elements of the `checkbox` module. - Added `tabindex` marks for labels in the `checkbox` module demo. - Added styling for `readonly` and `disabled` for `checkbox` module. - Updated `checkbox` module and added variables. @@ -1168,3 +1168,14 @@ - Updated flavor descriptions in `flavors.html`. - Everything is ready for release, let's write the `CHANGELOG` for **v2.2.0**. (A couple of templates and things might be done later today, as well as linking to them from certain components such as the `.drawer` which could benefit from that.) - Updated `CHANGELOG`, readying up for release. See you and **hugging cat** on the other side! + +# v2.2.1 Development Log + +## 20170522 + +- After taking a break, started updating the documentation. Added the sample website codpen project to the `templates.html` page to help newcomers get started. +- Added a small prompt for starring from the homepage. +- Added an exclamation mark next to Edge in the `index.html` page to make sure people read the note. +- Justify-aligned all paragraphs of text in documentation pages. +- Fixed a couple of mistakes in the documentation pages. +- Updated `navigation`'s `.drawer` documentation with better notes and examples.
Mixin definitions