mini.css aims to provide as much functionality as possible in less than 7KB gzipped. This very small footprint means that your websites and web applications will load faster, while still looking great utilising the modern components we provide!
-
-
-
-
-
-
-
ResponsiveThink mobile!
-
-
mini.css is crafted with both desktops and mobile devices in mind. All of its components are well-tested on different devices and will respond to any changes in the viewport, allowing for an experience tailored to each user's device!
-
-
-
-
-
-
-
Style-agnosticInfinitely customizable!
-
-
mini.css provides you with a customizable flavor system, allowing you to be a designer without all the hard work. This way you can create your own custom design and personalize your websites any way you want!
-
-
-
-
-
-
-
-
Setup & usage
-
mini.css is published in npm, yarn and bower, so you can easily download it, using your preferred package manager:
-
-
npm installmini.css
-
yarn addmini.css
-
bower installmini.css
-
-
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:
Finally, you can find mini.css on cdnjs, which you can use to include it in your projects.
-
-
-
-
-
-
Browser support
-
-
Edge12
-
Firefox28
-
Chrome26
-
Safari7.1
-
Opera17
-
Android4.4
-
-
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.
-
-
-
-
-
Quick overview
-
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.
-
Not convinced yet? Maybe you should read these 5 reasons to try out 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:
-
-
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)
-
Navigation - Common navigational elements such as headers, footers and navigation bars
-
Input Control - Form, input element, checkbox, radio button and button styling
-
Table - Modern table styling, horizontal and preset tables, table responsiveness for mobile devices
-
Card - Sleek, modern general-purpose content containers, media embedding
-
Tab - Modern, responsive tabs, accordions and collapses
-
Contextual - Content highlight element styling, elegant alerts and accessible tooltips
-
Progress - Modern progress bar styling and spinning progress indicators
-
Utility - Utilities, visibility helper classes, responsive sizing and breadcrumbs
-
-
While not strictly part of the framework, we have also created component libraries for React and Preact, which will make your development faster and easier, especially if you are developing progressive web apps. You can get started with one of our Javascript libraries here!
-
-
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.
-
-
-
-
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!
If you are still here after reading this far, we will assume you are interested or at least curious. Based on that assumption, here are a few links to help get you started:
-
-
For a quick guide on getting started, you might want to take a look at the available modules list and the tutorials provided for each one!
-
To get you started even faster, we have created a handful of templates that might fit your needs!
-
If you want a step-by-step guide on how to utilize the most commonly used modules, be sure to check out these articles on Medium:
-
-
If you are familiar with mini.css and want a cheat sheet or quick reference guide, check the quick reference page!
-
If you want to develop a progressive web app or just utilize a virtual DOM, you should check out our React & Preact Libraries, which will help you get started creating all kinds of custom components based on mini.css.
-
mini.css comes with a few nice pre-built customizable flavors. See which one of them better suits your needs!
-
If you are more experienced or demanding, you can always take a look at the customization section to cook up a flavor of your own custom-tailored to your needs!
-
Finally, if you want to contribute to the framework's development in any way or have an interest in what happens behind the scenes, visit the Github repository to find out more.
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.
-
-
-
-
-
-
-
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.
-
-
-
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 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:
-
-
At the outermost level of the card layout syntax is a .row, which serves as a wrapper for all the cards inside it.
-
Inside the .row, cards are defined as <div> elements of the .card class.
-
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.
Do: You can add as many .sections as you like to a card.
-
-
-
<div class="card">
- <div class="section">
- <h3>Card Title</h3>
- </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: 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.
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.
Don't: You should not have elements that are both cards and rows or columns at the same time.
-
-
-
-
-
-
-
-
-
-
Sections & media
-
-
-
-
-
Card with image
Content
-
Card with video
-
Normal section
Double-padded section
-
Normal section
Dark section
Darker section
-
-
-
-
-
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.
The .media class might not be well supported in older browsers, especially legacy versions of Internet Explorer.
-
Due to the .media class using object-fit, you might want to use a polyfill for better browser support, especially if you are targeting Microsoft browsers. We recommend this one for images and this one for videos.
-
Depending on the source website, some embedded videos might not display properly inside a .media section.
-
The .media class has a preset size of height: 200px. If you want to customize this, you should check the customization page for instructions.
-
-
-
-
-
-
-
-
-
Card sizing & fluidity
-
-
-
-
-
Small Card
Small cards are 240px wide.
-
Large Card
Large cards are 480px wide.
-
-
Fluid Card
Fluid cards scale their width based on their container. Always wrap them in a 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.
.fluid cards might not display properly in older browsers, especially legacy versions of Internet Explorer.
-
Due to the fact that .fluid cards stretch to fill their parent container, they might not fully respect their margins, like the rest of the cards. However, this should not cause any noticable problems with layout, except maybe the odd pixel here and there.
Don't: Avoid mixing fixed-width cards with .fluid cards. Mixing the two could result in some unexpected behaviors. You can, however, mix fixed-width cards with fluid columns, which can contain .fluid cards inside them, effectively achieving the desired effect.
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.
-
-
-
-
-
-
-
-
-
-
Card color variants
-
-
-
-
-
Warning Card
Warning cards are used to display important information to users.
-
Error Card
Error cards are used to display error messages to users.
-
-
-
-
-
-
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.
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.
+
+
+
+
+
+
+
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.
+
+
+
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 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:
+
+
At the outermost level of the card layout syntax is a .row, which serves as a wrapper for all the cards inside it.
+
Inside the .row, cards are defined as <div> elements of the .card class.
+
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.
Do: You can add as many .sections as you like to a card.
+
+
+
<div class="card">
+ <div class="section">
+ <h3>Card Title</h3>
+ </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: 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.
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.
Don't: You should not have elements that are both cards and rows or columns at the same time.
+
+
+
+
+
+
+
+
+
+
Sections & media
+
+
+
+
+
Card with image
Content
+
Card with video
+
Normal section
Double-padded section
+
Normal section
Dark section
Darker section
+
+
+
+
+
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.
The .media class might not be well supported in older browsers, especially legacy versions of Internet Explorer.
+
Due to the .media class using object-fit, you might want to use a polyfill for better browser support, especially if you are targeting Microsoft browsers. We recommend this one for images and this one for videos.
+
Depending on the source website, some embedded videos might not display properly inside a .media section.
+
The .media class has a preset size of height: 200px. If you want to customize this, you should check the customization page for instructions.
+
+
+
+
+
+
+
+
+
Card sizing & fluidity
+
+
+
+
+
Small Card
Small cards are 240px wide.
+
Large Card
Large cards are 480px wide.
+
+
Fluid Card
Fluid cards scale their width based on their container. Always wrap them in a 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.
.fluid cards might not display properly in older browsers, especially legacy versions of Internet Explorer.
+
Due to the fact that .fluid cards stretch to fill their parent container, they might not fully respect their margins, like the rest of the cards. However, this should not cause any noticable problems with layout, except maybe the odd pixel here and there.
Don't: Avoid mixing fixed-width cards with .fluid cards. Mixing the two could result in some unexpected behaviors. You can, however, mix fixed-width cards with fluid columns, which can contain .fluid cards inside them, effectively achieving the desired effect.
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.
+
+
+
+
+
+
+
+
+
+
Card color variants
+
+
+
+
+
Warning Card
Warning cards are used to display important information to users.
+
Error Card
Error cards are used to display error messages to users.
+
+
+
+
+
+
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.
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, tooltips and modals 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.
-
-
-
-
-
-
-
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 along with an implementation for .modal dialogs. 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:
Apart from the primary highlight style, there are also secondary and tertiary styles for highlighting.
-
If you want to highlight a longer piece of text, without line breaks, you can turn the highlight into an inline-block like you see this piece of text being displayed.
-
Finally, you can create contextual tags like this or 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.
Try to use elements with the .inline-block class only when absolutely necessary, as they break the normal text flow of the document. Avoid using this class on shorter pieces of text that span a few words and contain no line breaks.
-
<mark> elements, along with their supporting classes (except for .inline-block) can be easily used in paragraphs, headings and other elements, as they scale according to their parent element.
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.
Don't: Avoid using nested <mark> elements, unless the outer <mark> element is an .inline-block.
-
-
-
-
-
-
-
-
-
-
Toasts
-
-
-
- I'm a toast message!
- I'm a small toast message!
- I'm a large toast message!
-
-
-
-
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>
-<span class="toast large">This is a small toast message!</span>
-
-
-
-
Notes
-
-
Toast elements do not have any pre-defined behavior. You should use your own Javascript code and interactive HTML elements to deal with showing and hiding them as necessary.
-
If you want to create your own color or size variants for toast messages, check out the customization page.
-
-
-
-
<span class="toast small large">Not a good toast</span>
-
Don't: Avoid combining two toast size variants, as this might cause unexpected behavior.
-
-
-
-
-
-
-
-
-
-
Tooltips
-
-
-
-
Hover over this text to see a tooltip!
-
Hover over this text to see a reverse tooltip!
-
-
-
-
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>
-
-
-
-
Notes
-
-
Tooltips are built to be accessible and should display properly on screenreaders.
-
If you are not satisfied with the default tooltip colors, please check out the customization page for instuctions on how to create your own tooltip variants.
-
Remember to always add the aria-label attribute, otherwise your tooltip will not have any text to show.
-
-
-
-
-
-
-
-
-
Modals
-
-
-
-
-
-
-
-
-
Modal
-
-
This is a modal window!
-
-
-
-
-
-
-
-
Modal dialogs are pretty ease to make. Simply create an <input type="checkbox"> element, immediately followed by a <div> element with the .modal class. Inside this element, you can add a .card element with your modal dialog's contents. Remember to add a <label> element linked to your modal dialog's <input type="checkbox"> to let users close the dialog. You can also apply the .close class to a <label> element to display a close icon at the top right of the modal dialog.
You can use any styles you want from the card module to create different dialogs based on context (e.g. alerts, warnings etc.).
-
Remember to add a <label> linked to your modal dialog's <input type="checkbox"> or use Javascript to alter its state, otherwise users will not be able to close the dialog.
-
You can place your modal dialog anywhere on your page, as long as the structure is not altered. You can also toggle it from anywhere on a page.
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, tooltips and modals 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.
+
+
+
+
+
+
+
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 along with an implementation for .modal dialogs. 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:
Apart from the primary highlight style, there are also secondary and tertiary styles for highlighting.
+
If you want to highlight a longer piece of text, without line breaks, you can turn the highlight into an inline-block like you see this piece of text being displayed.
+
Finally, you can create contextual tags like this or 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.
Try to use elements with the .inline-block class only when absolutely necessary, as they break the normal text flow of the document. Avoid using this class on shorter pieces of text that span a few words and contain no line breaks.
+
<mark> elements, along with their supporting classes (except for .inline-block) can be easily used in paragraphs, headings and other elements, as they scale according to their parent element.
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.
Don't: Avoid using nested <mark> elements, unless the outer <mark> element is an .inline-block.
+
+
+
+
+
+
+
+
+
+
Toasts
+
+
+
+ I'm a toast message!
+ I'm a small toast message!
+ I'm a large toast message!
+
+
+
+
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>
+<span class="toast large">This is a small toast message!</span>
+
+
+
+
Notes
+
+
Toast elements do not have any pre-defined behavior. You should use your own Javascript code and interactive HTML elements to deal with showing and hiding them as necessary.
+
If you want to create your own color or size variants for toast messages, check out the customization page.
+
+
+
+
<span class="toast small large">Not a good toast</span>
+
Don't: Avoid combining two toast size variants, as this might cause unexpected behavior.
+
+
+
+
+
+
+
+
+
+
Tooltips
+
+
+
+
Hover over this text to see a tooltip!
+
Hover over this text to see a reverse tooltip!
+
+
+
+
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>
+
+
+
+
Notes
+
+
Tooltips are built to be accessible and should display properly on screenreaders.
+
If you are not satisfied with the default tooltip colors, please check out the customization page for instuctions on how to create your own tooltip variants.
+
Remember to always add the aria-label attribute, otherwise your tooltip will not have any text to show.
+
+
+
+
+
+
+
+
+
Modals
+
+
+
+
+
+
+
+
+
Modal
+
+
This is a modal window!
+
+
+
+
+
+
+
+
Modal dialogs are pretty ease to make. Simply create an <input type="checkbox"> element, immediately followed by a <div> element with the .modal class. Inside this element, you can add a .card element with your modal dialog's contents. Remember to add a <label> element linked to your modal dialog's <input type="checkbox"> to let users close the dialog. You can also apply the .close class to a <label> element to display a close icon at the top right of the modal dialog.
You can use any styles you want from the card module to create different dialogs based on context (e.g. alerts, warnings etc.).
+
Remember to add a <label> linked to your modal dialog's <input type="checkbox"> or use Javascript to alter its state, otherwise users will not be able to close the dialog.
+
You can place your modal dialog anywhere on your page, as long as the structure is not altered. You can also toggle it from anywhere on a page.
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.
-
-
-
-
-
-
-
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.
-
-
-
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:
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;.
-
We use a font-size of 16px for the root element.
-
We set line-height to 1.5.
-
-
-
-
-
Notes
-
-
Fluid typography is also included, but not enabled by default. If you want to try it out, check out the out the customization page.
-
-
-
-
-
-
-
-
-
Headings
-
-
-
Heading 1Subheading
-
Heading 2Subheading
-
Heading 3Subheading
-
Heading 4Subheading
-
Heading 5Subheading
-
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.
This is a paragraph with some sample text. Did you know mini.css v2 is codenamed Fermion? No? Well, now you do! Oh, by the way, that was some Bold text and here is some text in Italics. Maybe you want to know what our inline elements look like. For example a link to the Github repository of mini.css looks like that! Neat, right? Maybe you want to see some inline code or some sample input. Oh, also small text is cool, along with its siblings: the subscripthi! and the superscripthello!. Finally, check out the horizontal rule, preformatted code block and quotation below.
-
function sum(num1, num2) {
- var num3 = num1 + num2;
- console.log('Result: ' + num3);
-}
-
This is some quoted text from elsewhere.
-
-
-
-
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>
-<small>This is some small text.</small>
-<sub>Subscript</sub>
-<sup>Superscript</sup>
-<code>Inline code</code>
-<kbd>Keyboard Input</kbd>
-<hr>
-<pre>This is some preformatted text.</pre>
-<blockquote cite="www.quotation.source">
- This is some quoted text from another website or person.
-</blockquote>
-
-
-
-
-
-
-
-
-
Lists
-
-
-
-
-
Apple
-
Orange
-
Strawberry
-
-
-
Wake up
-
Eat breakfast
-
Go to work
-
-
-
-
-
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.
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>.
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.
+
+
+
+
+
+
+
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.
+
+
+
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:
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;.
+
We use a font-size of 16px for the root element.
+
We set line-height to 1.5.
+
+
+
+
+
Notes
+
+
Fluid typography is also included, but not enabled by default. If you want to try it out, check out the out the customization page.
+
+
+
+
+
+
+
+
+
Headings
+
+
+
Heading 1Subheading
+
Heading 2Subheading
+
Heading 3Subheading
+
Heading 4Subheading
+
Heading 5Subheading
+
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.
This is a paragraph with some sample text. Did you know mini.css v2 is codenamed Fermion? No? Well, now you do! Oh, by the way, that was some Bold text and here is some text in Italics. Maybe you want to know what our inline elements look like. For example a link to the Github repository of mini.css looks like that! Neat, right? Maybe you want to see some inline code or some sample input. Oh, also small text is cool, along with its siblings: the subscripthi! and the superscripthello!. Finally, check out the horizontal rule, preformatted code block and quotation below.
+
function sum(num1, num2) {
+ var num3 = num1 + num2;
+ console.log('Result: ' + num3);
+}
+
This is some quoted text from elsewhere.
+
+
+
+
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>
+<small>This is some small text.</small>
+<sub>Subscript</sub>
+<sup>Superscript</sup>
+<code>Inline code</code>
+<kbd>Keyboard Input</kbd>
+<hr>
+<pre>This is some preformatted text.</pre>
+<blockquote cite="www.quotation.source">
+ This is some quoted text from another website or person.
+</blockquote>
+
+
+
+
+
+
+
+
+
Lists
+
+
+
+
+
Apple
+
Orange
+
Strawberry
+
+
+
Wake up
+
Eat breakfast
+
Go to work
+
+
+
+
+
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.
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>.
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/favicon.png b/docs/v2/favicon.png
similarity index 100%
rename from docs/favicon.png
rename to docs/v2/favicon.png
diff --git a/docs/favicon_small.png b/docs/v2/favicon_small.png
similarity index 100%
rename from docs/favicon_small.png
rename to docs/v2/favicon_small.png
diff --git a/docs/flavors.html b/docs/v2/flavors.html
similarity index 99%
rename from docs/flavors.html
rename to docs/v2/flavors.html
index cd1a00e..feb7423 100644
--- a/docs/flavors.html
+++ b/docs/v2/flavors.html
@@ -1,112 +1,112 @@
-
-
-
-
-
- mini.css - Flavors
-
-
-
-
-
-
-
-
-
-
-
-
- m
- IntroductionModules
- FlavorsTemplates
- CustomizationQuick Reference
- Github
-
-
-
-
-
-
-
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:
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 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.
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 and vertical tables, certain card and progress styles, along with spinner donuts, tooltips, navigation bars, modals, drawers and toasts are not included.
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).
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).
The Progressive Web App flavor follows the Google Material Design Guidelines and targets mobile devices and especially those based on the Android operating system. It uses mostly the default naming conventions (.primary etc.). The grid system has 12 columns and most components use rounded corners with soft shadows. To make the flavor lighter, button groups, horizontal and vertical tables, certain card styles, the entirety of the progress and tab modules, along with tooltips, navigation bars, modals and most style variants are not included. Finally, the card module's .dark class has been replaced by the .accent class.
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:
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 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.
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 and vertical tables, certain card and progress styles, along with spinner donuts, tooltips, navigation bars, modals, drawers and toasts are not included.
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).
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).
The Progressive Web App flavor follows the Google Material Design Guidelines and targets mobile devices and especially those based on the Android operating system. It uses mostly the default naming conventions (.primary etc.). The grid system has 12 columns and most components use rounded corners with soft shadows. To make the flavor lighter, button groups, horizontal and vertical tables, certain card styles, the entirety of the progress and tab modules, along with tooltips, navigation bars, modals and most style variants are not included. Finally, the card module's .dark class has been replaced by the .accent class.
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.
-
-
-
-
-
-
-
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.
-
-
-
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:
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's .container is the outermost layer of your grid system. It is a fluid container that wraps the flexible grid system inside it.
-
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.
-
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:
-
-
using .col-SCR_SZ to specify fluid columns, 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).
-
using .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 (1 meaning 1/12 of the width of the row and 12 meaning 100% of the width of the row).
-
-
-
-
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.
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:
-
-
small: less than 768px wide
-
medium: more than or equal to 768px wide but less than 1280px wide
-
large: 1280px wide or more
-
-
-
Fluid columns can be used for sizes that are not of the form 100%/12×X where X an integer value between 1 and 12. For example, if you have 7 .col-sm elements in one row, each of the elements will have a width of 1/7th the width of the 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.
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.
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.
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.
-
-
-
-
-
-
-
-
-
-
Screen-specific layouts
-
-
-
-
-
-
Small screen layout
-
-
-
-
-
-
Medium/Large screen layout
-
-
-
-
-
-
-
-
-
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.
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.
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.
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.
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.
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.
-
-
-
-
-
-
-
-
-
-
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:
-
-
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.
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.
-
-
-
-
-
-
-
-
-
-
Column offsets
-
-
-
-
size = 8, offset = 2
-
size = 6, offset = 3
-
size = 4, offset = 4
-
-
size = 4, offset = 1
-
size = 4, offset = 2
-
-
-
-
-
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.
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: 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.
-
-
-
-
-
-
-
-
-
-
Column reordering
-
-
-
-
-
-
first
-
-
-
-
-
-
normal
-
-
-
-
-
-
-
last
-
-
-
-
-
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).
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.
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: 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.
-
-
-
-
-
-
-
-
-
-
Media object pattern
-
-
-
-
-
-
-
-
-
Media object heading
-
This is an example implementation of the popular media object pattern, using simple grid rules.
-
-
-
-
-
-
-
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.
The media object is not a different component, but rather a popular pattern that can be implemented using the standard grid system classes.
-
You can use many different elements for your media object. For example, you can make the right side of the media object contain a form or an input field.
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.
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.
-
-
-
-
-
-
-
-
-
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.
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.
+
+
+
+
+
+
+
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.
+
+
+
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:
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's .container is the outermost layer of your grid system. It is a fluid container that wraps the flexible grid system inside it.
+
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.
+
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:
+
+
using .col-SCR_SZ to specify fluid columns, 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).
+
using .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 (1 meaning 1/12 of the width of the row and 12 meaning 100% of the width of the row).
+
+
+
+
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.
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:
+
+
small: less than 768px wide
+
medium: more than or equal to 768px wide but less than 1280px wide
+
large: 1280px wide or more
+
+
+
Fluid columns can be used for sizes that are not of the form 100%/12×X where X an integer value between 1 and 12. For example, if you have 7 .col-sm elements in one row, each of the elements will have a width of 1/7th the width of the 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.
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.
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.
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.
+
+
+
+
+
+
+
+
+
+
Screen-specific layouts
+
+
+
+
+
+
Small screen layout
+
+
+
+
+
+
Medium/Large screen layout
+
+
+
+
+
+
+
+
+
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.
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.
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.
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.
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.
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.
+
+
+
+
+
+
+
+
+
+
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:
+
+
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.
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.
+
+
+
+
+
+
+
+
+
+
Column offsets
+
+
+
+
size = 8, offset = 2
+
size = 6, offset = 3
+
size = 4, offset = 4
+
+
size = 4, offset = 1
+
size = 4, offset = 2
+
+
+
+
+
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.
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: 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.
+
+
+
+
+
+
+
+
+
+
Column reordering
+
+
+
+
+
+
first
+
+
+
+
+
+
normal
+
+
+
+
+
+
+
last
+
+
+
+
+
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).
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.
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: 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.
+
+
+
+
+
+
+
+
+
+
Media object pattern
+
+
+
+
+
+
+
+
+
Media object heading
+
This is an example implementation of the popular media object pattern, using simple grid rules.
+
+
+
+
+
+
+
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.
The media object is not a different component, but rather a popular pattern that can be implemented using the standard grid system classes.
+
You can use many different elements for your media object. For example, you can make the right side of the media object contain a form or an input field.
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.
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.
+
+
+
+
+
+
+
+
+
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.
mini.css aims to provide as much functionality as possible in less than 7KB gzipped. This very small footprint means that your websites and web applications will load faster, while still looking great utilising the modern components we provide!
+
+
+
+
+
+
+
ResponsiveThink mobile!
+
+
mini.css is crafted with both desktops and mobile devices in mind. All of its components are well-tested on different devices and will respond to any changes in the viewport, allowing for an experience tailored to each user's device!
+
+
+
+
+
+
+
Style-agnosticInfinitely customizable!
+
+
mini.css provides you with a customizable flavor system, allowing you to be a designer without all the hard work. This way you can create your own custom design and personalize your websites any way you want!
+
+
+
+
+
+
+
+
Setup & usage
+
mini.css is published in npm, yarn and bower, so you can easily download it, using your preferred package manager:
+
+
npm installmini.css
+
yarn addmini.css
+
bower installmini.css
+
+
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:
Finally, you can find mini.css on cdnjs, which you can use to include it in your projects.
+
+
+
+
+
+
Browser support
+
+
Edge12
+
Firefox28
+
Chrome26
+
Safari7.1
+
Opera17
+
Android4.4
+
+
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.
+
+
+
+
+
Quick overview
+
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.
+
Not convinced yet? Maybe you should read these 5 reasons to try out 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:
+
+
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)
+
Navigation - Common navigational elements such as headers, footers and navigation bars
+
Input Control - Form, input element, checkbox, radio button and button styling
+
Table - Modern table styling, horizontal and preset tables, table responsiveness for mobile devices
+
Card - Sleek, modern general-purpose content containers, media embedding
+
Tab - Modern, responsive tabs, accordions and collapses
+
Contextual - Content highlight element styling, elegant alerts and accessible tooltips
+
Progress - Modern progress bar styling and spinning progress indicators
+
Utility - Utilities, visibility helper classes, responsive sizing and breadcrumbs
+
+
While not strictly part of the framework, we have also created component libraries for React and Preact, which will make your development faster and easier, especially if you are developing progressive web apps. You can get started with one of our Javascript libraries here!
+
+
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.
+
+
+
+
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!
If you are still here after reading this far, we will assume you are interested or at least curious. Based on that assumption, here are a few links to help get you started:
+
+
For a quick guide on getting started, you might want to take a look at the available modules list and the tutorials provided for each one!
+
To get you started even faster, we have created a handful of templates that might fit your needs!
+
If you want a step-by-step guide on how to utilize the most commonly used modules, be sure to check out these articles on Medium:
+
+
If you are familiar with mini.css and want a cheat sheet or quick reference guide, check the quick reference page!
+
If you want to develop a progressive web app or just utilize a virtual DOM, you should check out our React & Preact Libraries, which will help you get started creating all kinds of custom components based on mini.css.
+
mini.css comes with a few nice pre-built customizable flavors. See which one of them better suits your needs!
+
If you are more experienced or demanding, you can always take a look at the customization section to cook up a flavor of your own custom-tailored to your needs!
+
Finally, if you want to contribute to the framework's development in any way or have an interest in what happens behind the scenes, visit the Github repository to find out more.
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.
-
-
-
-
-
-
-
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.
-
-
-
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:
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 access 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 or you can align them vertically by adding the .vertical class. Finally, if you want to create aligned forms with a preset layout, you can utilize the grid module's rows and columns.
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.
-
Try not to combine the grid module's classes with .fluid or .vertical.input-groups, as this might cause certain styles to overlap and not display exactly like you want them to.
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: 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: 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.
Don't: Avoid using the .input-group class when creating aligned forms. This might cause unexpected behavior.
-
-
-
-
-
-
-
-
-
-
Checkboxes & radio buttons
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
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.
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.
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: 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: Never leave a checkbox or radio button without a <label>. The <label> is essential to properly display the checkbox or radio button.
-
-
-
-
-
-
-
-
-
-
Switches
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Switches are almost identical in structure to checkboxes and radio buttons (an .input-group containing an <input> of the proper type inside it ("checkbox" or "radio"), followed immediately by a <label> linking to it), their only difference being that you need to add the .switch class to <label> element to turn your input into a switch. Remember to apply tabindex="0" to your <input> to make it accessible.
You can create your own color variants for the .switch component. For more information, check out the customization page.
-
-
-
-
<div class="input-group">
- <label for="switch1">Switch with text on its left</label>
- <input type="checkbox" id="switch1" tabindex="0">
- <label for="switch1" class="switch"></label>
-</div>
-
Do: By using two <label> elements, you can move the actual .switch to the right of the label's text, effectively allowing you to change the layout. Remember to not add any text to your second <label> that implements the .switch class. You might want, however, to add a few trailing spaces to the first <label> element to make sure the text does not get covered by the component.
-
-
-
-
-
-
-
-
-
-
Buttons & button groups
-
-
-
-
-
-
-
-
-
-
-
Button group
-
-
-
-
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.
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.
Don't: Avoid using button size variants inside a .button-group, as this might result in unexpected behavior.
-
-
-
-
-
-
-
-
-
-
File upload buttons
-
-
-
-
-
-
-
-
-
-
-
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.
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.
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.
+
+
+
+
+
+
+
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.
+
+
+
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:
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 access 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 or you can align them vertically by adding the .vertical class. Finally, if you want to create aligned forms with a preset layout, you can utilize the grid module's rows and columns.
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.
+
Try not to combine the grid module's classes with .fluid or .vertical.input-groups, as this might cause certain styles to overlap and not display exactly like you want them to.
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: 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: 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.
Don't: Avoid using the .input-group class when creating aligned forms. This might cause unexpected behavior.
+
+
+
+
+
+
+
+
+
+
Checkboxes & radio buttons
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
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.
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.
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: 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: Never leave a checkbox or radio button without a <label>. The <label> is essential to properly display the checkbox or radio button.
+
+
+
+
+
+
+
+
+
+
Switches
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Switches are almost identical in structure to checkboxes and radio buttons (an .input-group containing an <input> of the proper type inside it ("checkbox" or "radio"), followed immediately by a <label> linking to it), their only difference being that you need to add the .switch class to <label> element to turn your input into a switch. Remember to apply tabindex="0" to your <input> to make it accessible.
You can create your own color variants for the .switch component. For more information, check out the customization page.
+
+
+
+
<div class="input-group">
+ <label for="switch1">Switch with text on its left</label>
+ <input type="checkbox" id="switch1" tabindex="0">
+ <label for="switch1" class="switch"></label>
+</div>
+
Do: By using two <label> elements, you can move the actual .switch to the right of the label's text, effectively allowing you to change the layout. Remember to not add any text to your second <label> that implements the .switch class. You might want, however, to add a few trailing spaces to the first <label> element to make sure the text does not get covered by the component.
+
+
+
+
+
+
+
+
+
+
Buttons & button groups
+
+
+
+
+
+
+
+
+
+
+
Button group
+
+
+
+
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.
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.
Don't: Avoid using button size variants inside a .button-group, as this might result in unexpected behavior.
+
+
+
+
+
+
+
+
+
+
File upload buttons
+
+
+
+
+
+
+
+
+
+
+
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.
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.
Do: You can use an .input-group to wrap the file upload <input> and its linked <label>, if you wish.
+
+
+
+
+
+
+
+
+
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/mini-default.min.css b/docs/v2/mini-default.min.css
similarity index 100%
rename from docs/mini-default.min.css
rename to docs/v2/mini-default.min.css
diff --git a/docs/modules.html b/docs/v2/modules.html
similarity index 99%
rename from docs/modules.html
rename to docs/v2/modules.html
index 1dca0c4..16e777a 100644
--- a/docs/modules.html
+++ b/docs/v2/modules.html
@@ -1,210 +1,210 @@
-
-
-
-
-
- mini.css - Modules
-
-
-
-
-
-
-
-
-
-
-
-
- m
-
- IntroductionModules
- FlavorsTemplates
- CustomizationQuick Reference
- Github
-
-
-
-
-
-
-
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.
-
-
-
-
-
-
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 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 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 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 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 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 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 contextual module provides you with simple tags, marks and highlights for your pages, allowing you to easily emphasize parts of your text. Contextual toasts, tooltips and modals 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 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 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. More specifically, the utility module contains:
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 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 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 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 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 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 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 contextual module provides you with simple tags, marks and highlights for your pages, allowing you to easily emphasize parts of your text. Contextual toasts, tooltips and modals 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 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 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. More specifically, the utility 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.
-
All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.
-
-
-
-
-
-
-
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.
-
-
-
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:
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> 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.
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.
-
-
-
-
-
-
-
-
-
-
Navigation bar
-
-
-
-
-
-
-
-
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.
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.
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.
-
-
-
-
-
-
-
-
-
-
Drawer
-
-
-
-
-
-
-
-
-
-
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.
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).
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.
Don't: Remember to apply the .persistent class to the .drawer-toggle and .drawer elements to avoid unexpected behavior.
-
-
-
-
-
-
-
-
-
-
Footer
-
-
-
-
-
-
-
-
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.
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.
-
-
-
-
-
-
-
-
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.
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.
+
All examples showcased refer to the mini-default flavor, some class names and styles might differ based on the flavor you're using.
+
+
+
+
+
+
+
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.
+
+
+
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:
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> 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.
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.
+
+
+
+
+
+
+
+
+
+
Navigation bar
+
+
+
+
+
+
+
+
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.
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.
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.
+
+
+
+
+
+
+
+
+
+
Drawer
+
+
+
+
+
+
+
+
+
+
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.
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).
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.
Don't: Remember to apply the .persistent class to the .drawer-toggle and .drawer elements to avoid unexpected behavior.
+
+
+
+
+
+
+
+
+
+
Footer
+
+
+
+
+
+
+
+
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.
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.
+
+
+
+
+
+
+
+
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/page_thumb.png b/docs/v2/page_thumb.png
similarity index 100%
rename from docs/page_thumb.png
rename to docs/v2/page_thumb.png
diff --git a/docs/progress.html b/docs/v2/progress.html
similarity index 98%
rename from docs/progress.html
rename to docs/v2/progress.html
index f5cc2c6..0a6e7c2 100644
--- a/docs/progress.html
+++ b/docs/v2/progress.html
@@ -1,251 +1,251 @@
-
-
-
-
-
- mini.css - Progress
-
-
-
-
-
-
-
-
-
-
-
-
- m
-
- IntroductionModules
- FlavorsTemplates
- CustomizationQuick Reference
- Github
-
-
-
-
-
-
-
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.
-
-
-
-
-
-
-
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.
-
-
-
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 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.
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).
-
-
-
<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.
-
-
-
-
-
-
-
-
-
-
Progress bar variants
-
-
-
Secondary process is 60% complete!
-
Tertiary process is 30% complete!
-
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.
Don't: Avoid mixing two classes of the same type (i.e. two color classes or two size classes).
-
-
-
-
-
-
-
-
-
-
Donut spinner
-
-
-
-
-
-
-
-
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.
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.
-
-
-
-
-
-
-
-
-
-
Donut spinner variants
-
-
-
-
-
-
-
-
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.
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.
+
+
+
+
+
+
+
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.
+
+
+
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 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.
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).
+
+
+
<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.
+
+
+
+
+
+
+
+
+
+
Progress bar variants
+
+
+
Secondary process is 60% complete!
+
Tertiary process is 30% complete!
+
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.
Don't: Avoid mixing two classes of the same type (i.e. two color classes or two size classes).
+
+
+
+
+
+
+
+
+
+
Donut spinner
+
+
+
+
+
+
+
+
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.
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.
+
+
+
+
+
+
+
+
+
+
Donut spinner variants
+
+
+
+
+
+
+
+
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.
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.
+
+
+
+
+
+
+
+
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/v2/project_thumbnail.png
similarity index 100%
rename from docs/project_thumbnail.png
rename to docs/v2/project_thumbnail.png
diff --git a/docs/quick_reference.html b/docs/v2/quick_reference.html
similarity index 98%
rename from docs/quick_reference.html
rename to docs/v2/quick_reference.html
index 418ba5e..c1d97ea 100644
--- a/docs/quick_reference.html
+++ b/docs/v2/quick_reference.html
@@ -1,1320 +1,1320 @@
-
-
-
-
- mini.css - Quick Reference
-
-
-
-
-
-
-
-
-
-
-
-
- m
-
- IntroductionModules
- FlavorsTemplates
- CustomizationQuick Reference
- Github
-
-
-
-
-
-
-
-
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.
-
-
-
-
-
-
Setup & usage
-
-
You can download mini.css using npm, yarn or Bower:
-
-
npm installmini.css
-
yarn addmini.css
-
bower installmini.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:
<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>
-<small>This is some small text.</small>
-<sub>Subscript</sub>
-<sup>Superscript</sup>
-<code>Inline code</code>
-<kbd>Keyboard Input</kbd>
-<hr>
-<pre>This is some preformatted text.</pre>
-<blockquote cite="Quotation source">
- This is some quoted text from another website or person.
-</blockquote>
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
Use the same structure as checkboxes and radios, add .switch to the <label> element
-
Add tabindex="0" to the <input> element for accessibility
-
You can add two <label> elements inside the .input-group, the first one containing the text and the second one the .switch component to reverse the switch's layout
<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
-
<input type="checkbox"> element with a unique id
-
<div> element with the .drawer class immediately after the <input type="checkbox">
-
Empty <label> element with the .close class inside the .drawer, linked to the id of the <input type="checkbox">
-
-
Drawers are left-aligned and expand on non-mobile screen sizes by default
-
Use .right to create right-aligned drawers or .persistent for non-responsive drawers.
-
Apply the .drawer class on a navigation bar and combine with grid classes for best results
-
Use the syntax exactly as presented in the examples, do not add elements between the checkbox and the container
<span class="toast">This is a normal toast message!</span>
-<span class="toast small">This is a large toast message!</span>
-<span class="toast large">This is a small toast message!</span>
-
-
-
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
-
Toasts display at the bottom of the screen on top of everything else
<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>
-
-
-
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
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.
+
+
+
+
+
+
Setup & usage
+
+
You can download mini.css using npm, yarn or Bower:
+
+
npm installmini.css
+
yarn addmini.css
+
bower installmini.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:
<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>
+<small>This is some small text.</small>
+<sub>Subscript</sub>
+<sup>Superscript</sup>
+<code>Inline code</code>
+<kbd>Keyboard Input</kbd>
+<hr>
+<pre>This is some preformatted text.</pre>
+<blockquote cite="Quotation source">
+ This is some quoted text from another website or person.
+</blockquote>
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
Use the same structure as checkboxes and radios, add .switch to the <label> element
+
Add tabindex="0" to the <input> element for accessibility
+
You can add two <label> elements inside the .input-group, the first one containing the text and the second one the .switch component to reverse the switch's layout
<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
+
<input type="checkbox"> element with a unique id
+
<div> element with the .drawer class immediately after the <input type="checkbox">
+
Empty <label> element with the .close class inside the .drawer, linked to the id of the <input type="checkbox">
+
+
Drawers are left-aligned and expand on non-mobile screen sizes by default
+
Use .right to create right-aligned drawers or .persistent for non-responsive drawers.
+
Apply the .drawer class on a navigation bar and combine with grid classes for best results
+
Use the syntax exactly as presented in the examples, do not add elements between the checkbox and the container
<span class="toast">This is a normal toast message!</span>
+<span class="toast small">This is a large toast message!</span>
+<span class="toast large">This is a small toast message!</span>
+
+
+
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
+
Toasts display at the bottom of the screen on top of everything else
<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>
+
+
+
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
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.
-
-
-
-
-
-
-
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.
-
-
-
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:
The tab container's basic syntax 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:
-
-
First, add an <input type="radio"> element. Give it a name and an id in order to be able to link to it and group it with the rest of the radio buttons in the container.
-
Follow the <input> element with a <label> element linking to it. Inside this element, add the text you want to be shown as the title of your tab.
-
Finally, add a <div> immediately after the <label>'s closing tag. This will be the panel that contains the tab's content. Inside this element, you can add all the content you want in your tab (headings, images, text).
-
-
-
-
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">
- <label for="tab1" aria-hidden="true">Tab 1</label>
- <div>
- <h3>Tab 1</h3>
- <p>This is the first tab's content.</p>
- </div>
- <input type="radio" name="tab-group" id="tab2" aria-hidden="true">
- <label for="tab2" aria-hidden="true">Tab 2</label>
- <div>
- <h3>Tab 2</h3>
- <p>This is the second tab's content.</p>
- </div>
- <input type="radio" name="tab-group" id="tab3" aria-hidden="true">
- <label for="tab3" aria-hidden="true">Tab 3</label>
- <div>
- <h3>Tab 3</h3>
- <p>This is the third tab's content.</p>
- </div>
-</div>
-
-
-
-
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.
-
Using the method described above for making tabs accessible, screen readers will ignore tab controls and only read the content of tabs.
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: 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: Remember to use the aria-hidden="true" attribute to make your tabs fully accessible.
-
-
-
-
-
-
-
-
-
-
Stacked tabs
-
-
-
-
-
-
Section 1
This is the first accordion section's content.
-
-
-
Section 2
This is the second accordion section's content.
-
-
-
-
-
This is the first collapse section's content.
-
-
-
This is the second collapse section's content.
-
-
-
-
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">
- <label for="a1" aria-hidden="true">Accordion section 1</label>
- <div>
- <h3>Section 1</h3>
- <p>This is the first accordion section's content.</p>
- </div>
- <input type="radio" name="accordion" id="a2"aria-hidden="true">
- <label for="a2" aria-hidden="true">Accordion section 2</label>
- <div>
- <h3>Section 2</h3>
- <p>This is the second accordion section's content.</p>
- </div>
-</div>
-
-<div class="tabs stacked">
- <input type="checkbox" id="c1" aria-hidden="true">
- <label for="c1" aria-hidden="true">Collapse section 1</label>
- <div>
- <p>This is the first collapse section's content.</p>
- </div>
- <input type="checkbox" id="c2" aria-hidden="true">
- <label for="c2" aria-hidden="true">Collapse section 2</label>
- <div>
- <p>This is the second collapse section's content.</p>
- </div>
-</div>
-
-
-
-
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.
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.
+
+
+
+
+
+
+
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.
+
+
+
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:
The tab container's basic syntax 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:
+
+
First, add an <input type="radio"> element. Give it a name and an id in order to be able to link to it and group it with the rest of the radio buttons in the container.
+
Follow the <input> element with a <label> element linking to it. Inside this element, add the text you want to be shown as the title of your tab.
+
Finally, add a <div> immediately after the <label>'s closing tag. This will be the panel that contains the tab's content. Inside this element, you can add all the content you want in your tab (headings, images, text).
+
+
+
+
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">
+ <label for="tab1" aria-hidden="true">Tab 1</label>
+ <div>
+ <h3>Tab 1</h3>
+ <p>This is the first tab's content.</p>
+ </div>
+ <input type="radio" name="tab-group" id="tab2" aria-hidden="true">
+ <label for="tab2" aria-hidden="true">Tab 2</label>
+ <div>
+ <h3>Tab 2</h3>
+ <p>This is the second tab's content.</p>
+ </div>
+ <input type="radio" name="tab-group" id="tab3" aria-hidden="true">
+ <label for="tab3" aria-hidden="true">Tab 3</label>
+ <div>
+ <h3>Tab 3</h3>
+ <p>This is the third tab's content.</p>
+ </div>
+</div>
+
+
+
+
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.
+
Using the method described above for making tabs accessible, screen readers will ignore tab controls and only read the content of tabs.
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: 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: Remember to use the aria-hidden="true" attribute to make your tabs fully accessible.
+
+
+
+
+
+
+
+
+
+
Stacked tabs
+
+
+
+
+
+
Section 1
This is the first accordion section's content.
+
+
+
Section 2
This is the second accordion section's content.
+
+
+
+
+
This is the first collapse section's content.
+
+
+
This is the second collapse section's content.
+
+
+
+
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">
+ <label for="a1" aria-hidden="true">Accordion section 1</label>
+ <div>
+ <h3>Section 1</h3>
+ <p>This is the first accordion section's content.</p>
+ </div>
+ <input type="radio" name="accordion" id="a2"aria-hidden="true">
+ <label for="a2" aria-hidden="true">Accordion section 2</label>
+ <div>
+ <h3>Section 2</h3>
+ <p>This is the second accordion section's content.</p>
+ </div>
+</div>
+
+<div class="tabs stacked">
+ <input type="checkbox" id="c1" aria-hidden="true">
+ <label for="c1" aria-hidden="true">Collapse section 1</label>
+ <div>
+ <p>This is the first collapse section's content.</p>
+ </div>
+ <input type="checkbox" id="c2" aria-hidden="true">
+ <label for="c2" aria-hidden="true">Collapse section 2</label>
+ <div>
+ <p>This is the second collapse section's content.</p>
+ </div>
+</div>
+
+
+
+
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.
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.
-
-
-
-
-
-
-
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.
-
-
-
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:
Table layout utilizes the <table> HTML element with the following structure (usual tabular structure):
-
-
On the outermost level, there is the <table> element.
-
If you want to include a <caption> element, it must by the first element inside the <table> element.
-
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.
-
Immediately after the <thead> element, you can add a <tfoot> element, if you want to. Inside it, you should usually add one or more <tr> elements, which contain one or more <td> elements.
-
Finally, add your <tbody> element. Inside it, you should usually add one or more <tr> elements, which contain one or more <td> elements. For each <td> element, specify a data-label attribute equal to the heading of the column. This enables responsibility for your table, so that the values in the columns will be properly labeled on mobile devices.
Tables are responsive by default and will change to a card-like view below a certain screen width. If you'd rather not make them responsive, check the last section on this page.
-
Specifying the data-label attribute is essential for the responsive version of a table to display properly. You can, however, use a value different from the column's name. Make sure it does not confuse your users, though.
-
We strongly suggest you avoid adding multiple rows in your <thead> element, as it could cause problems with accessibility. However, if you absolutely must, you might want to check this codepen for an idea on how to deal with irregular border styling.
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: 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 using <td> elements inside your <thead>. You should use a <tbody> element instead.
-
-
-
-
-
-
-
-
-
-
-
Scrollable tables
-
-
-
-
-
-
People
-
-
Name
Surname
Alias
-
-
-
Chad
Wilberts
MrOne
-
Adam
Smith
TheSmith
-
Sophia
Canderson
Candee
-
Nick
Thomson
NickThom
-
Mark
Gerkis
Markie
-
John
Fergusson
Fergujohn
-
Sylvia
Pouleau
Sylver
-
Norman
Jones
NormalJones
-
Trevor
Heidel
Heidi
-
-
-
-
-
-
Scrollable tables can be created by simply adding the .scrollable class to the root element of your table (i.e. the <table> element). Scrollable 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.
Due to .scrollable 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 .scrollable tables, feel free to submit a new issue on Github.
-
.scrollable tables have a default maximum height of 400px. If you want to change this, you should check out the customization page.
-
-
-
-
-
<table class="scrollable">
- <!-- ... -->
- <tfoot>
- <!-- Do not do this! -->
- </tfoot>
- <!-- ... -->
-</table>
-
Don't: We already explicitly stated that, due to the way .scrollable tables are styled, the <tfoot> element is not supported. Please refer to the last section of this page if you need to use this element and you want to have a scrollable table layout.
-
-
-
-
-
-
-
-
-
-
-
Horizontal tables
-
-
-
-
-
-
People
-
-
Name
Surname
Alias
-
-
-
Chad
Wilberts
MrOne
-
Adam
Smith
TheSmith
-
Sophia
Canderson
Candee
-
Nick
Thomson
NickThom
-
-
-
-
-
-
Scrollable tables are very similar to horizontal ones and can be created by simply adding the .scrollable class to the root element of your table (i.e. the <table> element). Similarly to horizontal ones, they can accommodate as many data rows as you like, making their overflow scrollable, while they do not support the <tfoot> element. As usual, remember to add the data-label attribute, as shown in the previous section, to allow your tables to be responsive without any errors.
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.
Don't: Avoid comibing the .horizontal and .scrollable classes on the same element, as this can cause unexpected behavior.
-
-
-
-
-
-
-
-
-
-
Table variants & matrices
-
-
-
-
-
Star Wars Character Alignment Table
-
-
Lawful
Neutral
Chaotic
-
Good
Yoda
Luke Skywalker
Chewbacca
-
Neutral
C-3PO
Boba Fett
Han Solo
-
Bad
Darth Vader
Emperor Palpatine
Jabba the Hutt
-
-
-
-
-
-
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.
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.
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-top: 0; for the elements inside that row to fix this.
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.
-
-
-
-
-
-
-
-
-
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.
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.
+
+
+
+
+
+
+
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.
+
+
+
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:
Table layout utilizes the <table> HTML element with the following structure (usual tabular structure):
+
+
On the outermost level, there is the <table> element.
+
If you want to include a <caption> element, it must by the first element inside the <table> element.
+
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.
+
Immediately after the <thead> element, you can add a <tfoot> element, if you want to. Inside it, you should usually add one or more <tr> elements, which contain one or more <td> elements.
+
Finally, add your <tbody> element. Inside it, you should usually add one or more <tr> elements, which contain one or more <td> elements. For each <td> element, specify a data-label attribute equal to the heading of the column. This enables responsibility for your table, so that the values in the columns will be properly labeled on mobile devices.
Tables are responsive by default and will change to a card-like view below a certain screen width. If you'd rather not make them responsive, check the last section on this page.
+
Specifying the data-label attribute is essential for the responsive version of a table to display properly. You can, however, use a value different from the column's name. Make sure it does not confuse your users, though.
+
We strongly suggest you avoid adding multiple rows in your <thead> element, as it could cause problems with accessibility. However, if you absolutely must, you might want to check this codepen for an idea on how to deal with irregular border styling.
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: 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 using <td> elements inside your <thead>. You should use a <tbody> element instead.
+
+
+
+
+
+
+
+
+
+
+
Scrollable tables
+
+
+
+
+
+
People
+
+
Name
Surname
Alias
+
+
+
Chad
Wilberts
MrOne
+
Adam
Smith
TheSmith
+
Sophia
Canderson
Candee
+
Nick
Thomson
NickThom
+
Mark
Gerkis
Markie
+
John
Fergusson
Fergujohn
+
Sylvia
Pouleau
Sylver
+
Norman
Jones
NormalJones
+
Trevor
Heidel
Heidi
+
+
+
+
+
+
Scrollable tables can be created by simply adding the .scrollable class to the root element of your table (i.e. the <table> element). Scrollable 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.
Due to .scrollable 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 .scrollable tables, feel free to submit a new issue on Github.
+
.scrollable tables have a default maximum height of 400px. If you want to change this, you should check out the customization page.
+
+
+
+
+
<table class="scrollable">
+ <!-- ... -->
+ <tfoot>
+ <!-- Do not do this! -->
+ </tfoot>
+ <!-- ... -->
+</table>
+
Don't: We already explicitly stated that, due to the way .scrollable tables are styled, the <tfoot> element is not supported. Please refer to the last section of this page if you need to use this element and you want to have a scrollable table layout.
+
+
+
+
+
+
+
+
+
+
+
Horizontal tables
+
+
+
+
+
+
People
+
+
Name
Surname
Alias
+
+
+
Chad
Wilberts
MrOne
+
Adam
Smith
TheSmith
+
Sophia
Canderson
Candee
+
Nick
Thomson
NickThom
+
+
+
+
+
+
Scrollable tables are very similar to horizontal ones and can be created by simply adding the .scrollable class to the root element of your table (i.e. the <table> element). Similarly to horizontal ones, they can accommodate as many data rows as you like, making their overflow scrollable, while they do not support the <tfoot> element. As usual, remember to add the data-label attribute, as shown in the previous section, to allow your tables to be responsive without any errors.
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.
Don't: Avoid comibing the .horizontal and .scrollable classes on the same element, as this can cause unexpected behavior.
+
+
+
+
+
+
+
+
+
+
Table variants & matrices
+
+
+
+
+
Star Wars Character Alignment Table
+
+
Lawful
Neutral
Chaotic
+
Good
Yoda
Luke Skywalker
Chewbacca
+
Neutral
C-3PO
Boba Fett
Han Solo
+
Bad
Darth Vader
Emperor Palpatine
Jabba the Hutt
+
+
+
+
+
+
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.
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.
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-top: 0; for the elements inside that row to fix this.
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.
+
+
+
+
+
+
+
+
+
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/v2/templates.html
similarity index 100%
rename from docs/templates.html
rename to docs/v2/templates.html
diff --git a/docs/utility.html b/docs/v2/utility.html
similarity index 98%
rename from docs/utility.html
rename to docs/v2/utility.html
index a9460d5..b076274 100644
--- a/docs/utility.html
+++ b/docs/v2/utility.html
@@ -1,350 +1,350 @@
-
-
-
-
-
- mini.css - Utility
-
-
-
-
-
-
-
-
-
-
-
-
- m
-
- IntroductionModules
- FlavorsTemplates
- CustomizationQuick Reference
- Github
-
-
-
-
-
-
-
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.
-
-
-
-
-
-
-
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.
-
-
-
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:
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.
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.
-
-
-
-
-
-
-
-
-
-
Generic borders & shadows
-
-
-
-
-
This is a paragraph with a piece of bordered text.
-
-
-
This is an element that casts a shadow.
-
-
-
-
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.
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.
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.
-
-
-
-
-
-
-
-
-
-
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.
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.
-
-
-
-
-
-
-
-
-
-
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.
-
Sample code
-
<span class="hidden-sm">Hidden in smaller screens</span>
-<span class="hidden-md">Hidden in medium-sized screens</span>
-<span class="hidden-lg">Hidden in larger screens</span>
-
-<span class="visually-hidden-sm">Visually hidden in smaller screens</span>
-<span class="visually-hidden-md">Visually hidden in medium-sized screens</span>
-<span class="visually-hidden-lg">Visually hidden in larger screens</span>
-
-
-
-
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:
-
-
small: less than 768px wide
-
medium: more than or equal to 768px wide but less than 1280px wide
-
large: 1280px wide or more
-
-
-
Responsive visibility helper classes are independent, meaning that hiding an element in one screen size will not affect it visibility in any other screen size.
-
-
-
-
<span class="hidden-sm hidden-md">Hidden in smaller and medium-sized screens, visible in larger screens</span>
-<!-- or -->
-<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.
-
-
-
<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.
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.
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.
Don't: Avoid nesting lists, breadcrumbs or a combination of the two inside the .breadcrumbs list, as this might cause unexpected behavior.
-
-
-
-
-
-
-
-
-
-
Close icon
-
-
-
-
-
-
-
-
-
-
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.
-
-
-
<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.
-
-
-
-
-
-
-
-
-
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.
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.
+
+
+
+
+
+
+
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.
+
+
+
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:
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.
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.
+
+
+
+
+
+
+
+
+
+
Generic borders & shadows
+
+
+
+
+
This is a paragraph with a piece of bordered text.
+
+
+
This is an element that casts a shadow.
+
+
+
+
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.
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.
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.
+
+
+
+
+
+
+
+
+
+
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.
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.
+
+
+
+
+
+
+
+
+
+
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.
+
Sample code
+
<span class="hidden-sm">Hidden in smaller screens</span>
+<span class="hidden-md">Hidden in medium-sized screens</span>
+<span class="hidden-lg">Hidden in larger screens</span>
+
+<span class="visually-hidden-sm">Visually hidden in smaller screens</span>
+<span class="visually-hidden-md">Visually hidden in medium-sized screens</span>
+<span class="visually-hidden-lg">Visually hidden in larger screens</span>
+
+
+
+
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:
+
+
small: less than 768px wide
+
medium: more than or equal to 768px wide but less than 1280px wide
+
large: 1280px wide or more
+
+
+
Responsive visibility helper classes are independent, meaning that hiding an element in one screen size will not affect it visibility in any other screen size.
+
+
+
+
<span class="hidden-sm hidden-md">Hidden in smaller and medium-sized screens, visible in larger screens</span>
+<!-- or -->
+<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.
+
+
+
<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.
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.
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.
Don't: Avoid nesting lists, breadcrumbs or a combination of the two inside the .breadcrumbs list, as this might cause unexpected behavior.
+
+
+
+
+
+
+
+
+
+
Close icon
+
+
+
+
+
+
+
+
+
+
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.
+
+
+
<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.
+
+
+
+
+
+
+
+
+
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/v3/DEVLOG.md b/docs/v3/DEVLOG.md
new file mode 100644
index 0000000..3de8ccb
--- /dev/null
+++ b/docs/v3/DEVLOG.md
@@ -0,0 +1,18 @@
+# mini.css v3 (Gluon) Development Log
+
+## 20171011
+
+- Moved all WIP to `gluon` branch, seems like the right choice.
+- Initialized pages for **v3**.
+- Initialized new folder structure in `src` and `dist`, moved legacy code from **v2** to `_v2` inside of `src`, so that it can be easily identified.
+- Set version for the `gluon` branch to `v3.0.0-alpha.1`, should be ready for a pre-release next month at the latest.
+- Started development of `core` and `default` flavor.
+- Turned color palette of `core` into CSS variables to allow for customization.
+- Changed native font stack to a less legacy-based one.
+- Defined defaults for certain variables that were not defined in the past.
+- `$_body-margin` and `$_apply-defaults-to-all` are now hidden variables, effectively hiding a layer of complexity behind them and allowing for easier customization and more streamlined defaults.
+- Removed a fix for `article, aside, section, figcaption, figure, main, details, menu`, as it was IE-based. Replaced with a single fix for `details` as it could still be a bit of a problem in certain versions of Edge and Firefox.
+- Removed fix for `audio, video`, as it was IE-based.
+- Removed fix for `svg:not(:root)`, as it was IE-based.
+- Completely removed the `dfn` fix, as it's a rarely (if ever) used element and it targets an older version of Android, meaning it's not a really meaningful fix to anyone.
+- Stopped right before the headings, these will be updated and built next time.
diff --git a/docs/v3/index.html b/docs/v3/index.html
new file mode 100644
index 0000000..5749719
--- /dev/null
+++ b/docs/v3/index.html
@@ -0,0 +1,11 @@
+
+mini.css - Minimal, responsive, style-agnostic CSS framework
+
+
+
+
+
+
+
+
+
diff --git a/src/flavors/mini-dark.scss b/src/_v2/flavors/mini-dark.scss
similarity index 98%
rename from src/flavors/mini-dark.scss
rename to src/_v2/flavors/mini-dark.scss
index e759141..c3d31b4 100644
--- a/src/flavors/mini-dark.scss
+++ b/src/_v2/flavors/mini-dark.scss
@@ -1,644 +1,644 @@
-// This is a flavor file. Duplicate it and edit it to create your own flavor. Read instructions carefully.
-// Single-line comments, starting with '//' will not be included in your final CSS file. Multiline comments,
-// structured like the flavor description below, will be included in your final CSS file.
-/*
- Flavor name: Dark (mini-dark)
- Author: Angelos Chalaris (chalarangelo@gmail.com)
- Maintainers: Angelos Chalaris
- mini.css version: v2.3.4
-*/
-// Basic rules for body and typography
-$fore-color: #d0d0d0; // Text and general foreground color
-$back-color: #232e33; // Body background color
-$base-font-family: // Default font stack for all elements:
- '-apple-system, BlinkMacSystemFont,\"Segoe UI\",\"Roboto\", \"Droid Sans\",\"Helvetica Neue\", Helvetica, Arial, sans-serif';
-// OS X and iOS system fonts (San Francisco) -> Windows system fonts -> Android system fonts (newer and older) -> Fallback fonts
-$base-root-font-size: 16px; // Root font sizing for all elements [1]
-$_1px: (1px/$base-root-font-size) * 1rem; // Calculated rem value of 1px [1]
-$base-font-size: 1rem; // Default font sizing for all elements [2]
-$base-line-height: 1.5; // Default line height for all elements.
-$use-fluid-typography: false; // Should fluid typography be used at the root element? (`true`/`false`)
-$body-margin: 0; // Margin for the body
-$apply-defaults-to-all: true; // Should default values be applied to all elements? (`true` or `false`) [3]
-$h1-font-size: 2rem; // Font size of h1
-$h2-font-size: 1.6875rem; // Font size for h2
-$h3-font-size: 1.4375rem; // Font size for h3
-$h4-font-size: 1.1875rem; // Font size for h4
-$h5-font-size: 1rem; // Font size for h5
-$h6-font-size: 0.8125rem; // Font size for h6
-$heading-line-height: 1.2em; // Line height for all headings
-$heading-margin: 0.75rem 0.5rem; // Margin for all headings
-$heading-font-weight: 500; // Font weight for all headings
-$heading-smalltext-fore-color: #acacac; // color in headings
-$make-heading-smalltext-block: true; // Should elements in headings be displayed as blocks (`true`/`false`) [4]
-$heading-smalltext-b-font-size: 0.75em; // Font size of block elements in headings
-$heading-smalltext-b-top-margin:-0.25rem; // Top margin of block elements in headings
-$paragraph-margin: 0.5rem; // Margin for
elements
-$list-margin: 0.5rem; // Margin for
and
elements
-$list-left-padding: 1rem; // Left padding for and
elements
-$bold-font-weight: 700; // Font weight for and
-$horizontal-rule-line-height: 1.25em; // line height
-$horizontal-rule-margin: 0.5rem; // margin
-$horizontal-rule-border-style: $_1px solid #9e9e9e;// Border style for horizontal rules (used in the element's border-top)
-$horizontal-rule-fancy-style: true; // Should a fancy styling be applied for the element (`true`/`false`) [5]
-$horizontal-rule-fancy-gradient:"to right, #616161, #9e9e9e, #616161"; // Gradient style for fancy horizontal rule
-$blockquote-back-color: #232e33; // Background color for
-$blockquote-fore-color: $fore-color; // Text color for
-$blockquote-margin: 0.5rem; // Margin for
-$blockquote-padding: 0.5rem 0.5rem 1.5rem;// Padding for
-$blockquote-sidebar-style: 4*$_1px solid #192024;// Style for the sidebar of
-$blockquote-cite-font-size: 0.875rem; // Font size for citation of
-$blockquote-cite-fore-color: #acacac; // Text color for citation of
-$blockquote-cite-left-position: 0.625rem; // Left padding for citation of
-$blockquote-cite-bottom-position: 0; // Bottom padding for citation of
-$blockquote-border-style: 0; // Border style for
-$blockquote-border-radius: 0 2*$_1px 2*$_1px 0; // Border radius for
-$blockquote-box-shadow: none; // Box shadow for
-$use-default-code-fonts: true; // Should default font choice (monospace) be used for code elements? (`true`/`false`) [6]
-//$code-font-family: monospace, monospace; // Fonts for code elements if not default
-$code-element-padding: 0.125rem 0.25rem; // Padding for
-$code-element-fore-color: $fore-color; // Text color for
-$code-element-back-color: #20292e; // Background color for
-$code-element-border-style: 0; // Border style for
-$code-element-border-radius: 2*$_1px; // Border radius for
-$code-element-box-shadow: none; // Box shadow for
-$pre-element-padding: 0.75rem; // Padding for
-$pre-element-fore-color: $code-element-fore-color; // Text color for
-$pre-element-back-color: $code-element-back-color; // Background color for
-$pre-element-border-style: 0; // Border style for
-$pre-element-border-radius: 0 2*$_1px 2*$_1px 0; // Border radius for
-$pre-element-margin: 0.5rem; // Margin for
-$pre-element-box-shadow: none; // Box shadow for
-$add-pre-element-sidebar: true; // Should a fancy sidebar be added to the left side of
(`true`/`false`) [7]
-$pre-element-sidebar-style: 4*$_1px solid #01579b;// Style of the sidebar of
