<inputtype="checkbox"class="modal"id="modal1"><div><labelfor="modal1"autocomplete="off"></label><div><labelfor="modal1"><spanclass="close"></span></label><h3>Modal dialog</h3><hr><p>This is a modal dialog.</p></div></div>
<li><ahref="https://chalarangelo.github.io/mini.css/modules#utility"class="link">Utilities & Helper Classes</a></li>
<li><ahref="https://chalarangelo.github.io/mini.css/modules#utility-extra"class="link">Utilities & Experimental Classes</a></li>
</ul>
</div>
</div>
<labelfor="nav-toggle"></label>
<br>
<divclass="grid-container">
<divclass="row">
<divclass="col xs-no md-1"></div>
<divclass="col xs-12 md-10">
<h1>mini.css<small> a minimal Sass-y responsive mobile-first style-agnostic CSS framework</small></h1>
<p>Below you can see each module in action, along with certain suggestions on how to add functionality to the various components. Bear in mind that this demo is for the <strong>Default</strong> flavor. Naming conventions may vary between flavors, however the structure and functionality of the modules should be the same. Please refer to specific flavors for those differences. The <strong><ahref="https://chalarangelo.github.io/mini.css/modules-niteowl">NiteOwl</a></strong> flavor uses the same naming conventions for the module components, so you won't have any trouble. If you are migrating from Bootstrap and want to use the <strong>Bootstrap</strong> flavor, most naming conventions are based on the original naming conventions of Bootstrap 3.3.7.</p>
<p><strong>To use the Default flavor, add the following code inside your HTML page's <code><head></code> tag:</strong></p>
<p>The Base module contains customized typography rules, colors and most of the functionality provided in <ahref="https://necolas.github.io/normalize.css/">normalize.css</a>. Below we showcase some of the most important typography styles.</p>
<h3>Fonts, sizes and colors</h3>
<p>The default flavor uses the <strong>Helvetica</strong> font family and a font-size of <strong>1em</strong> with a line-height of <strong>1.5</strong>. Colors used are <strong>#f5f5f5</strong> for the background and <strong>#222</strong> for the text. Most of the things in this module are subjective to one's preferences and should be changed according to your liking. Heading, <code><sub></code>, <code><sup></code> and <code><small></code> elements use multipliers, so changing the base font-size should affect those too. Apart from that, colors and styles for links can easily be changed, as well as a lot of other parameters. Images are responsive by default, so they will shrink to fit smaller viewports without any additional work. Below we highlight some important things, like heading and code styling, but you can see most of the typography rules in action in these pages.</p>
<p>The grid system provided can be fully customized to use as many columns as you wish and have custom breakpoints for different device sizes. The default grid uses 12 columns (as shown below). Customized classes are also defined to hide certain columns in certain viewport sizes. This can be specifically used to customize column offseting on different devices.</p>
<h3>Grid structure</h3>
<p>The basic grid structure is as follows:</p>
<ul>
<li>The outer wrapper of the grid system uses the <code>.grid-container</code> class.</li>
<li>Inside this wrapper, rows can be defined using the <code>.row</code> class.</li>
<li>Inside the rows, columns can be defined using the <code>.col</code> class.</li>
<li>Column width can be specified for different devices using the respective class prefixes (<code>.xs-</code>, <code>.sm-</code>, <code>.md-</code>, <code>.lg-</code>) followed by the width (in columns) of the specific column.</li>
<li>Columns can be hidden in certain viewports, using the <code>-no</code> suffix for the specific screen size.</li>
<p>The navigation system provided contains custom classes for the navigation bar, logo and links. Navigation bars can be horizontal or vertical, fixed or otherwise. Navigation bars are responsive by default, so fixed navigation bars will properly shrink down to a button on smaller screens and, when the menu is opened, it will be displayed on top of the page's content.</p>
<h3>Navigation structure</h3>
<p>The structure of the navigation system is as follows:</p>
<ul>
<li>You should wrap your navigation system in a <code><div></code> with the <code>.nav</code> class.</li>
<li>If you want your navigation bar to be vertical (horizontal is the default), use the <code>.vertical</code> class.</li>
<li>If you want your navigation bar to be fixed, use the <code>.fixed</code> class.</li>
<li>Use an element with the <code>.logo</code> class for your website's logo.</li>
<li>For the navigation links, use an unordered list (<code><ul></code>) and <strong>inside</strong> each <code><li></code> element, add another element with the <code>.link</code> class to stylize the element as a navigation link.</li>
<li>Responsiveness can be added for fixed navigation bars by adding a hidden <code><input type="checkbox"></code> right before the navigation bar and a label linking to that specific checkbox right after the navigation bar.</li>
<li>Use <code>autocomplete="off"</code> to make your menu not open by default in mobile devices.</li>
<p>The dropdown module is an extra module that allows you to add dropdown components to your navigation bars. These components can be customized and work well on mobile devices. <strong>Using too many dropdowns or nesting dropdowns is yet undocumented and might cause unexpected behavior.</strong></p>
<h3>Dropdown structure</h3>
<p>The basic structure of dropdowns is as follows</p>
<ul>
<li>To add a dropdown component, add the <code>.dropdown</code> class to one of your link elements inside the navigation bar.</li>
<li>Add an <code><input type="checkbox"></code> with the <code>.dropdown</code> class and right after it a <code><div></code> element that contains an unordered list with list elements that contains navigation links, exactly like you would make a normal navigation menu.</li>
<li>For multiple dropdowns, you should use <code><input type="radio"></code> elements.</li>
<li>On mobile devices, there might be issues with the dropdown not closing after a link is clicked (mainly when it links to the same page). This can be easily dealt with using javascript (by making all the links inside the dropdown's <code><div></code> element uncheck the navigation bar's checkbox) or using <code><label></code> elements creatively inside the links.</li>
<li>Use <code>autocomplete="off"</code> to make your dropdown not open by default in mobile devices.</li>
<p>The tabbed navigation module allows you to easily create tabbed navigation systems, that are fully customizable to fit your needs. <strong>Nested tabs are not supported and might cause unexpected behavior.</strong></p>
<h3>Tabbed navigation structure</h3>
<p>The structure of the tabbed navigation system is as follows:</p>
<ul>
<li>Use the <code>.tabs</code> class to specify the container for the tabbed navigation system.</li>
<li>For each tab use an <code><input type="radio"></code>, immediately followed by a <code><div></code> element.</li>
<li>This last element should contain a <code><label></code> linking to the radio button of the tab and another <code><div></code> that will contain the tab's contents.</li>
<li>Specify the tab that will be open by default using the <code>checked</code> property on one of the radio buttons.</li>
<p>(*):Due to a minor incompatibility between panels and tabs, the above example is not shown like most of the others. Our most experienced teams of developers and designers are on this.</p><br>
<h2id="table">Tables</h2>
<p>Tables can be easily stylized to look more modern, using stripes and selective borders (vertical only by default). Classes for horizontal only borders(<code>.hor</code>) and full borders(<code>.bor</code>) are also provided. Use the <code>.tbl</code> class in your <code><table></code> elements to easily apply your styling.</p>
<p>Form customization and styling is easy using the <code>.frm</code> class in any <code><form></code> element. Inputs inside the form will be automatically styled and they will use complementary highlights for certain events (<code>:focus</code>, <code>disabled</code>, <code>:invalid</code> etc.). You can use the <code>.aligned</code> and <code>.inline</code> classes to create aligned and inline forms respectively. Aligned forms should be used in combination with the <code>.ctrl-group</code> class to group together labels with their respective inputs.</p>
<p>Use the <code>.btn</code> class on <code><button></code>, <code><a></code>, <code><label></code> or similar elements to give them a unique style. Color variants are provided (<code>.red</code>, <code>.green</code> and <code>.blue</code>), as well as size variants (<code>.sm</code> and <code>.lg</code>).</p>
<p>Use the <code>.lbl</code> or <code>.bdg</code> class on any elements to style them like labels or badges. Color variants are provided (<code>.red</code>, <code>.green</code> and <code>.blue</code>) for both of these styles.</p>
<p>Modal dialogs can be easily added and customized to the user's liking and offer support for the close button utility. <strong>Showing more than one modal dialog at once might have unexpected results and is not encouraged.</strong></p>
<h3>Modal dialog structure</h3>
<p>The basic structure of a modal dialog is as follows:</p>
<ul>
<li>Use the <code>.modal</code> class on an <code><input type="checkbox"></code>. <strong>Place this checkbox along with any other elements specified below at the very start of your <code><body></code>.</strong></li>
<li>Add a <code><div></code> right after the checkbox. Inside it add a second <code><div></code> with your modal dialog's contents, as well as a <code><label></code> for the checkbox <strong>without any content inside it.</strong> This label will act as the overlay behind the modal. If you do not want clicking the background to close the modal dialog, add the label without linking it to the checkbox.</li>
<li>If you have enabled close button support, you can add a <code><span class="close"></code> inside a label for the checkbox in the innermost <code><div></code> to add a close button to the top right corner of your modal dialog.</li>
<li>Finally, add a label linking to the modal dialog's checkbox anywhere in your page. You can also toggle the modal using Javascript, by setting the checkbox's state to <code>checked</code>.</li>
<p>The collapse module adds two components with similar functionality. </p>
<ul>
<li>Single collapse components can be created by adding the <code>.clps</code> class on an <code><input type="checkbox"></code> element, followed by a <code><div></code> with the content to be hidden/shown based on the collapse's state.</li>
<li>Similarly, accordion collapse components can be created by adding the <code>.acrd</code> class to as many <code><input type="radio"></code> elements as you want. You should add a <code><label></code> linking to each radio immediately after it, followed by a <code><div></code> with the content to be hidden/shown based on the accordion's state. </li>
<li>You can use the single collapse component's styling for a set of radio buttons or the accordion's styling for a single checkbox if you would like to use a different styling for your collapse components without adding new CSS definitions.</li>
<inputtype="checkbox"class="clps"id="collapse1"autocomplete="off"><divclass="well"style="margin-left: 10px; margin-right: 10px;">This text will be shown or hidden based on the above button.</div><br>
<div>This is the final collapse of the accordion.</div></pre>
</div><br>
<h2id="progress">Progress bars</h2>
<p>The progress bar module is very easy to use and extend. Simply create a <code><div></code> with the <code>.prg</code> class and inside it add a <code><span></code> element with the desired <code>style="width:XX%"</code> and you have a progress bar. Add text inside the <code><span></code> element if you want. You can use the <code>.green</code> or <code>.red</code> variants for the <code><span></code> element if you want to use different colors. Finally, you can always stack multiple progress bars, by simply adding more <code><span></code> elements, just make sure their widths add up to 100% or less.</p>
<p>The carousel module allows you to create manually-controlled image slideshows for your pages. <strong>Nested carousels might cause unexpected behavior, please refrain from using them.</strong></p>
<h3>Carousel structure</h3>
<p>The base structure for the carousel component is as follows:</p>
<ul>
<li>Specify a carousel wrapper, using the <code>.carousel</code> class on a <code><div></code> element.</li>
<li>Inside the wrapper, add the an <code><input type="radio"></code>, followed immediately by a <code><div></code> element. Inside the latter, add an <code><img></code> element, followed by a <code><div></code> element which will act as the image's description. Finally, right after closing the first <code><div></code> element, add a <code><label></code> linked to the radio button for the image.</li>
<li>Repeat the process as many times as you want to add more images. <strong>Remember that you cannot skip the description <code><div></code> element, even if it is empty, as it is required for the component to work properly.</strong></li>
<li>Add the <code>checked</code> attribute to the first radio button of your carousel (or the one corresponding to the image you want to be displayed by default) to make the carousel work properly.</li>
</ul>
<p><strong>Auto-scrolling is not enabled by default in this carousel component.</strong> If you want the carousel to scroll automatically, you can check each of the radio buttons automatically using Javascript on set intervals. Using a similar technique you can pause the automatic scrolling when the user's cursor is inside the carousel.</p>
<p>This is yet another image description.</p>
</div>
</div>
<label for="crs3"></label>
</div></pre>
</div><br>
<h2id="utility">Utilities & Helper classes</h2>
<p>The core utilities module contains a set of useful utilities and helper classes to make common tasks easier when developing new pages.</p>
<h3>Generic borders</h3>
<p>By using the <code>opacity</code> CSS property in a creative way, along with <code>border-radius</code>es, we have created utility classes that will create generic borders for virtually any element you want. Simply add the <code>.bordered</code> class to create a generic border around an element. You can also use the <code>.rounded</code> and <code>.circle</code> classes (with or without the border style) to create reounded or circular corners for different elements accordingly.</p>
<p>You can easily add contextual text or background color to certain textual elements by simply using one of the contextual prefixes (<code>.txt-</code> and <code>.bg-</code> respectively) and a color suffix (<code>red</code>, <code>green</code> or <code>blue</code>).</p>
<divclass="panel"><h4class="head">Example</h4>
<p>Here is some text with contextual colors: <spanclass="txt-red">red</span>, <spanclass="txt-green">green</span>&<spanclass="txt-blue">blue</span>.<br>
And here is some text with contextual backgrounds: <spanclass="bg-red">red</span>, <spanclass="bg-green">green</span>&<spanclass="bg-blue">blue</span>.</p>
<p>Apart from the above utilities, there are some extra classes provided to help streamline the development process. Some of these classes use the <codeclass="txt-red">!important</code> property to override other styles, so be careful when using them. The provided helper classes are as follows:</p>
<ul>
<li>Quick floats can be created using the <code>.drg-left</code> and <code>.drg-right</code> classes.</li>
<li>Center content blocks can be created using the <code>.ct-block</code> class.</li>
<li>Utilize the popular <ahref="http://nicolasgallagher.com/micro-clearfix-hack/">micro clearfix hack</a> using the <code>.cf</code> class.</li>
<li>Use the <code>.hidden</code> class to hide any content you wish.</li>
</ul>
<h2id="utility-extra">Utilities & Experimental classes</h2>
<p>The extra utilities module contains some more useful utilities, as well as some more experimental and unstable utility classes, that some people might find of use. <strong>Any components marked as experimental might be unstable and behave unexpectedly, use at your own risk!</strong></p>
<h3>Breadcrumbs</h3>
<p>Create breadcrumbs to indicate the navigational hierarchy of a page's location, using the <code>.brdcrmb</code> class on a list element.</p>
<p>There are multiple types of generic containers provided:</p>
<ul>
<li>Wells can be created using the <code>.well</code> class and are the simplest type of generic container.</li>
<li>Alerts are similar to wells, but are contextualized can be toggled on or off (manually or using scripts). Use the <code>.alert-</code> prefix on an <code><input type="checkbox"></code> along with a color suffix (<code>red</code>, <code>green</code> or <code>blue</code>) and a <code><div></code> element to create an alert. Adding a <code><span class="close"></li> element inside a label pointing to the alert's checkbox will allow user to dismiss the alert.</code>
<li>Panels are similar to wells, but looks like application windows. You can create a panel using the <code>.panel</code> class and you can specify a title element for your panel using the <code>.head</code> class on the very first element of your panel.</li>
<divclass="well"style="margin-left: 10px; margin-right: 10px;">This is a well.</div><br>
<strong>Alerts:</strong><br><br>
<inputtype="checkbox"id="alert1"class="alert-red"checked><divstyle="margin-left: 10px; margin-right: 10px;">This is a red alert without a close button.</div><br>
<inputtype="checkbox"id="alert2"class="alert-green"checked><divstyle="margin-left: 10px; margin-right: 10px;">This is a green alert with a <ahref="#">link</a> but no close button either.</div><br>
<inputtype="checkbox"id="alert3"class="alert-blue"checkedautocomplete="off"><divstyle="margin-left: 10px; margin-right: 10px;">This is a blue alert with a close button. <labelfor="alert3"><spanclass="close"></span></label></div><br>
<div>This is a blue alert with a close button. <label for="alert3"><span class="close"></span></label></div>
<p>You can show a small overlay of content when the user clicks on specific elements using the <code>.popover-</code> prefix on an <code><input type="checkbox"></code> along with the <code>top</code> or <code>bottom</code> suffix. Add a <code><label></code> right after the checkbox linked to it and inside it add another element with the popover's class you are using. When you click the label, the popover will appear above or below the label. Click on the label again or the popover text itself to hide it.</p>
<inputtype="checkbox"id="popover1"class="popover-top"autocomplete="off"><labelfor="popover1"class="btn green">Open top popover<spanclass="popover-top">This is the popover text.</span></label>
<inputtype="checkbox"id="popover2"class="popover-bottom"autocomplete="off"><labelfor="popover2"class="btn red">Open bottom popover<spanclass="popover-bottom">This is the popover text.</span></label><br><br>
<span class="popover-bottom">This is the popover text.</span>
</label></pre>
</div>
<h3>Experimental components</h3>
<p>There are two experimental components provided, stateful buttons and button groups:
<ul><li>To create a stateful button apply the <code>.stateful</code> class to an <code><input type="checkbox"></code>, followed by two labels (the first is for the inactive state and the second one for the active state).<strong>This component is not enabled by default as it is unstable, you can enable it manually.</strong></li>
<li>To create a button group, use the <code>.btn-grp</code> class to wrap a set of <code>.btn</code> elements.<strong>This component is considered stable enough, so it is enabled by default, you can disable it manually.</strong></li></ul>
<pstyle="padding-top: 10px;"><strong>mini.css</strong> was designed and built by <ahref="https://github.com/Chalarangelo">@Chalarangelo</a>. It is licensed under the <ahref="https://github.com/Chalarangelo/mini.css/blob/master/LICENSE">MIT License</a>. You can view the project's source code on <ahref="https://github.com/Chalarangelo/mini.css">Github</a>.</p>
