Getting started : LXcore

To start using LXCore, add the recommended CDN links shown below to the appropriate areas of your markup.

CDN Links

Originally, Bootstrap 3.4.1 was required; however, to allow LXCore to be modular and extended to AEM's Touch UI themes, we combined Bootstrap with our code. Now, Bootstrap does not need to be loaded before LXCore.

CSS

Add the CSS links to the <head> section of your page. Modify the version number of LXCore to match the one you wish to use.

LXCore CSS

<link rel="stylesheet" href="https://media.lexmark.com/www/lxkfef/v3.7.1/css/screen-bs.min.css" crossorigin="anonymous">

JavaScript

Add the JS links to the bottom of your page, preferrably before the closing <body> tag. jQuery must be loaded before LXCore's JS. For AEM implementations, JQuery is already loaded and does not need to be loaded separately.

Currently, jQuery is required. You may use any jQuery version from 1.12.2 to 3.0.0 (per Bootstrap 3.4.1's requirements). Currently, testing with LXCore's third-party JavaScript modules and our custom JavaScript is underway. A quick check on basic functionality has yielded no issues yet.

JQuery JS

<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.0.0/jquery.min.js"></script>

LXCore JS

<script src="https://media.lexmark.com/www/lxkfef/v3.7.1/js/apps-bs.min.js"></script>

Bootstrap follows common web standards and—with minimal extra effort—can be used to create sites that are accessible to those using AT.

Skip navigation

If your navigation contains many links and comes before the main content in the DOM, add a Skip to main content link before the navigation (for a simple explanation, see this A11Y Project article on skip navigation links). Using the .sr-only class will visually hide the skip link, and the .sr-only-focusable class will ensure that the link becomes visible once focused (for sighted keyboard users).

Due to long-standing shortcomings/bugs in Chrome (see issue 262171 in the Chromium bug tracker) and Internet Explorer (see this article on in-page links and focus order), you will need to make sure that the target of your skip link is at least programmatically focusable by adding tabindex="-1".

In addition, you may want to explicitly suppress a visible focus indication on the target (particularly as Chrome currently also sets focus on elements with tabindex="-1" when they are clicked with the mouse) with #content:focus { outline: none; }.

Note that this bug will also affect any other in-page links your site may be using, rendering them useless for keyboard users. You may consider adding a similar stop-gap fix to all other named anchors / fragment identifiers that act as link targets.

<body>
  <a href="#content" class="sr-only sr-only-focusable">Skip to main content</a>
  ...
  <div class="container" id="content" tabindex="-1">
    <!-- The main page content -->
  </div>
</body>

Nested headings

When nesting headings (<h1> - <h6>), your primary document header should be an <h1>. Subsequent headings should make logical use of <h2> - <h6> such that screen readers can construct a table of contents for your pages.

Learn more at HTML CodeSniffer and Penn State's AccessAbility.

Color contrast

Currently, some of the default color combinations available in Bootstrap (such as the various styled button classes, some of the code highlighting colors used for basic code blocks, the .bg-primary contextual background helper class, and the default link color when used on a white background) have a low contrast ratio (below the recommended ratio of 4.5:1). This can cause problems to users with low vision or who are color blind. These default colors may need to be modified to increase their contrast and legibility.

Additional resources

Bootstrap is built to work best in the latest desktop and mobile browsers, meaning older browsers might display differently styled, though fully functional, renderings of certain components.

Supported browsers

Specifically, we support the latest versions of the following browsers and platforms.

Alternative browsers which use the latest version of WebKit, Blink, or Gecko, whether directly or via the platform's web view API, are not explicitly supported. However, Bootstrap should (in most cases) display and function correctly in these browsers as well. More specific support information is provided below.

Mobile devices

Generally speaking, Bootstrap supports the latest versions of each major platform's default browsers. Note that proxy browsers (such as Opera Mini, Opera Mobile's Turbo mode, UC Browser Mini, Amazon Silk) are not supported.

	Chrome	Firefox	Safari
Android	Supported	Supported	N/A
iOS	Supported	Supported	Supported

Desktop browsers

Similarly, the latest versions of most desktop browsers are supported.

	Chrome	Firefox	Internet Explorer	Opera	Safari
Mac	Supported	Supported	N/A	Supported	Supported
Windows	Supported	Supported	Supported	Supported	Not supported

On Windows, we support Internet Explorer 8-11.

For Firefox, in addition to the latest normal stable release, we also support the latest Extended Support Release (ESR) version of Firefox.

Unofficially, Bootstrap should look and behave well enough in Chromium and Chrome for Linux, Firefox for Linux, and Internet Explorer 7, as well as Microsoft Edge, though they are not officially supported.

For a list of some of the browser bugs that Bootstrap has to grapple with, see our Wall of browser bugs.

Internet Explorer 8 and 9

Internet Explorer 8 and 9 are also supported, however, please be aware that some CSS3 properties and HTML5 elements are not fully supported by these browsers. In addition, Internet Explorer 8 requires the use of Respond.js to enable media query support.

Feature	Internet Explorer 8	Internet Explorer 9
`border-radius`	Not supported	Supported
`box-shadow`	Not supported	Supported
`transform`	Not supported	Supported, with `-ms` prefix
`transition`	Not supported
`placeholder`	Not supported

Visit Can I use... for details on browser support of CSS3 and HTML5 features.

Internet Explorer 8 and Respond.js

Beware of the following caveats when using Respond.js in your development and production environments for Internet Explorer 8.

Respond.js and cross-domain CSS

Using Respond.js with CSS hosted on a different (sub)domain (for example, on a CDN) requires some additional setup. See the Respond.js docs for details.

Respond.js and `file://`

Due to browser security rules, Respond.js doesn't work with pages viewed via the file:// protocol (like when opening a local HTML file). To test responsive features in IE8, view your pages over HTTP(S). See the Respond.js docs for details.

Respond.js and `@import`

Respond.js doesn't work with CSS that's referenced via @import. In particular, some Drupal configurations are known to use @import. See the Respond.js docs for details.

Internet Explorer 8 and box-sizing

IE8 does not fully support box-sizing: border-box; when combined with min-width, max-width, min-height, or max-height. For that reason, as of v3.0.1, we no longer use max-width on .containers.

Internet Explorer 8 and @font-face

IE8 has some issues with @font-face when combined with :before. LXCore uses that combination with its Lexicons. If a page is cached, and loaded without the mouse over the window (i.e. hit the refresh button or load something in an iframe) then the page gets rendered before the font loads. Hovering over the page (body) will show some of the icons and hovering over the remaining icons will show those as well. See issue #13863 for details.

IE Compatibility modes

Bootstrap is not supported in the old Internet Explorer compatibility modes. To be sure you're using the latest rendering mode for IE, consider including the appropriate <meta> tag in your pages:

<meta http-equiv="X-UA-Compatible" content="IE=edge">

Confirm the document mode by opening the debugging tools: press F12 and check the "Document Mode".

This tag is included in all of Bootstrap's documentation and examples to ensure the best rendering possible in each supported version of Internet Explorer.

See this StackOverflow question for more information.

Internet Explorer 10 in Windows 8 and Windows Phone 8

Internet Explorer 10 doesn't differentiate device width from viewport width, and thus doesn't properly apply the media queries in Bootstrap's CSS. Normally you'd just add a quick snippet of CSS to fix this:

@-ms-viewport       { width: device-width; }

However, this doesn't work for devices running Windows Phone 8 versions older than Update 3 (a.k.a. GDR3), as it causes such devices to show a mostly desktop view instead of narrow "phone" view. To address this, you'll need to include the following CSS and JavaScript to work around the bug.

@-ms-viewport       { width: device-width; }
@-o-viewport        { width: device-width; }
@viewport           { width: device-width; }

// Copyright 2014-2015 Twitter, Inc.
// Licensed under MIT (https://github.com/twbs/bootstrap/blob/master/LICENSE)
if (navigator.userAgent.match(/IEMobile\/10\.0/)) {
  var msViewportStyle = document.createElement('style')
  msViewportStyle.appendChild(
    document.createTextNode(
      '@-ms-viewport{width:auto!important}'
    )
  )
  document.querySelector('head').appendChild(msViewportStyle)
}

For more information and usage guidelines, read Windows Phone 8 and Device-Width.

As a heads up, we include this in all of Bootstrap's documentation and examples as a demonstration.

Safari percent rounding

The rendering engine of versions of Safari prior to v7.1 for OS X and Safari for iOS v8.0 had some trouble with the number of decimal places used in our .col-*-1 grid classes. So if you had 12 individual grid columns, you'd notice that they came up short compared to other rows of columns. Besides upgrading Safari/iOS, you have some options for workarounds:

Add .pull-right to your last grid column to get the hard-right alignment
Tweak your percentages manually to get the perfect rounding for Safari (more difficult than the first option)

Modals, navbars, and virtual keyboards

Overflow and scrolling

Support for overflow: hidden on the <body> element is quite limited in iOS and Android. To that end, when you scroll past the top or bottom of a modal in either of those devices' browsers, the <body> content will begin to scroll. See Chrome bug #175502 (fixed in Chrome v40) and WebKit bug #153852.

iOS text fields and scrolling

As of iOS 9.3, while a modal is open, if the initial touch of a scroll gesture is within the boundary of a textual <input> or a <textarea>, the <body> content underneath the modal will be scrolled instead of the modal itself. See WebKit bug #153856.

Virtual keyboards

Also, note that if you're using a fixed navbar or using inputs within a modal, iOS has a rendering bug that doesn't update the position of fixed elements when the virtual keyboard is triggered. A few workarounds for this include transforming your elements to position: absolute or invoking a timer on focus to try to correct the positioning manually. This is not handled by Bootstrap, so it is up to you to decide which solution is best for your application.

Navbar Dropdowns

The .dropdown-backdrop element isn't used on iOS in the nav because of the complexity of z-indexing. Thus, to close dropdowns in navbars, you must directly click the dropdown element (or any other element which will fire a click event in iOS).

Browser zooming

Page zooming inevitably presents rendering artifacts in some components, both in Bootstrap and the rest of the web. Depending on the issue, we may be able to fix it (search first and then open an issue if need be). However, we tend to ignore these as they often have no direct solution other than hacky workarounds.

Sticky `:hover`/`:focus` on mobile

Even though real hovering isn't possible on most touchscreens, most mobile browsers emulate hovering support and make :hover "sticky". In other words, :hover styles start applying after tapping an element and only stop applying after the user taps some other element. This can cause Bootstrap's :hover states to become undesirably "stuck" on such browsers. Some mobile browsers also make :focus similarly sticky. There is currently no simple workaround for these issues other than removing such styles entirely.

Printing

Even in some modern browsers, printing can be quirky.

In particular, as of Chrome v32 and regardless of margin settings, Chrome uses a viewport width significantly narrower than the physical paper size when resolving media queries while printing a webpage. This can result in Bootstrap's extra-small grid being unexpectedly activated when printing. See issue #12078 and Chrome bug #273306 for some details. Suggested workarounds:

Embrace the extra-small grid and make sure your page looks acceptable under it.
Customize the values of the @screen-* Less variables so that your printer paper is considered larger than extra-small.
Add custom media queries to change the grid size breakpoints for print media only.

Also, as of Safari v8.0, fixed-width .containers can cause Safari to use an unusually small font size when printing. See #14868 and WebKit bug #138192 for more details. One potential workaround for this is adding the following CSS:

@media print {
  .container {
    width: auto;
  }
}

Android stock browser

Out of the box, Android 4.1 (and even some newer releases apparently) ship with the Browser app as the default web browser of choice (as opposed to Chrome). Unfortunately, the Browser app has lots of bugs and inconsistencies with CSS in general.

Select menus

On <select> elements, the Android stock browser will not display the side controls if there is a border-radius and/or border applied. (See this StackOverflow question for details.) Use the snippet of code below to remove the offending CSS and render the <select> as an unstyled element on the Android stock browser. The user agent sniffing avoids interference with Chrome, Safari, and Mozilla browsers.

<script>
$(function () {
  var nua = navigator.userAgent
  var isAndroid = (nua.indexOf('Mozilla/5.0') > -1 && nua.indexOf('Android ') > -1 && nua.indexOf('AppleWebKit') > -1 && nua.indexOf('Chrome') === -1)
  if (isAndroid) {
    $('select.form-control').removeClass('form-control').css('width', '100%')
  }
})
</script>

Want to see an example? Check out this JS Bin demo.

Validators

In order to provide the best possible experience to old and buggy browsers, Bootstrap uses CSS browser hacks in several places to target special CSS to certain browser versions in order to work around bugs in the browsers themselves. These hacks understandably cause CSS validators to complain that they are invalid. In a couple places, we also use bleeding-edge CSS features that aren't yet fully standardized, but these are used purely for progressive enhancement.

These validation warnings don't matter in practice since the non-hacky portion of our CSS does fully validate and the hacky portions don't interfere with the proper functioning of the non-hacky portion, hence why we deliberately ignore these particular warnings.

Our HTML docs likewise have some trivial and inconsequential HTML validation warnings due to our inclusion of a workaround for a certain Firefox bug.

Stay up to date on the development of LXKcore and reach out to the community with these helpful resources.

Read and subscribe to The Official LXKcore wiki.
Create issues at The Official LXKcore issue page.

Bootstrap automatically adapts your pages for various screen sizes. Here's how to disable this feature so your page works like this non-responsive example.

Steps to disable page responsiveness

Omit the viewport <meta> mentioned in the CSS docs
Override the width on the .container for each grid tier with a single width, for example width: 970px !important; Be sure that this comes after the default Bootstrap CSS. You can optionally avoid the !important with media queries or some selector-fu.
If using navbars, remove all navbar collapsing and expanding behavior.
For grid layouts, use .col-xs-* classes in addition to, or in place of, the medium/large ones. Don't worry, the extra-small device grid scales to all resolutions.

You'll still need Respond.js for IE8 (since our media queries are still there and need to be processed). This disables the "mobile site" aspects of Bootstrap.

Bootstrap template with responsiveness disabled

We've applied these steps to an example. Read its source code to see the specific changes implemented.

View non-responsive example

Please review the Licensing terms

Start with this basic HTML template, or modify these examples. We hope you'll customize our templates and examples, adapting them to suit your needs.

Copy the HTML below to begin working with a minimal Bootstrap document.

<!doctype html>
<html lang="en">
  <head>
    <meta charset="utf-8">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1">
    <!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
    <title>Bootstrap 101 Template</title>

    <!-- Bootstrap -->
    <link href="css/bootstrap.min.css" rel="stylesheet">

    <!-- HTML5 shim and Respond.js for IE8 support of HTML5 elements and media queries -->
    <!-- WARNING: Respond.js doesn't work if you view the page via file:// -->
    <!--[if lt IE 9]>
      <script src="https://oss.maxcdn.com/html5shiv/3.7.3/html5shiv.min.js"></script>
      <script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
    <![endif]-->
  </head>
  <body>
    <h1>Hello, world!</h1>

    <!-- jQuery (necessary for Bootstrap's JavaScript plugins) -->
    <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js"></script>
    <!-- Include all compiled plugins (below), or include individual files as needed -->
    <script src="js/bootstrap.min.js"></script>
  </body>
</html>

Build on the basic template with a LXCore Theme.

Lexmark Theme

Version: 1.0.15

To start using the Lexmark Theme, please add links below to their respective areas in the Web page markup.

Theme CSS

Place the following after the link to the LXCore styles in the <head>. Modify both the name (e.g., "lxk") and the version number (e.g., "v1.0.15") to match the one you wish to use.

Current Version

<link rel="stylesheet" href="https://media.lexmark.com/www/lxkfef/current/themes/lxk/css/screen.min.css" crossorigin="anonymous">

Specific Version

<link rel="stylesheet" href="https://media.lexmark.com/www/lxkfef/themes/lxk/v1.0.15/css/screen.min.css" crossorigin="anonymous">

Theme JS

Place the following after the link to the LXCore JavaScript at the bottom of page.

Current Version

<script src="https://media.lexmark.com/www/lxkfef/current/themes/lxk/js/apps.min.js"></script>

Specific Version

<script src="https://media.lexmark.com/www/lxkfef/themes/lxk/v1.0.15/js/apps.min.js"></script>

Basic examples

Header and Footer

The sitewide navigation and branding for Lexmark.com

Containers

An example of how containers are organized along with a fluid container.

Lexmark PartnerNet Theme

Version: 1.1.6

To start using the Lexmark PartnerNet Theme, please add links below to their respective areas in the Web page markup.

Theme CSS

Place the following after the link to the LXCore styles in the <head>. Modify both the name (e.g., "pnet") and the version number (e.g., "v1.1.6") to match the one you wish to use.

Current Version

<link rel="stylesheet" href="https://media.lexmark.com/www/lxkfef/current/themes/pnet/css/screen.min.css" crossorigin="anonymous">

Specific Version

<link rel="stylesheet" href="https://media.lexmark.com/www/lxkfef/themes/pnet/v1.1.6/css/screen.min.css" crossorigin="anonymous">

Theme JS

Place the following after the link to the LXCore JavaScript at the bottom of page.

Current Version

<script src="https://media.lexmark.com/www/lxkfef/current/themes/pnet/js/apps.min.js"></script>

Specific Version

<script src="https://media.lexmark.com/www/lxkfef/themes/pnet/v1.1.6/js/apps.min.js"></script>

Basic examples

Header and Footer

The sitewide navigation and branding for Lexmark PartnerNet (partnernet.lexmark.com)

Lexmark Elevate Theme

Version: 1.0.1

To start using the Lexmark Elevate Theme, please add links below to their respective areas in the Web page markup.

Theme CSS

Place the following after the link to the LXCore styles in the <head>. Modify both the name (e.g., "elevate") and the version number (e.g., "v1.0.1") to match the one you wish to use.

Current Version

<link rel="stylesheet" href="https://media.lexmark.com/www/lxkfef/current/themes/elevate/css/screen.min.css" crossorigin="anonymous">

Specific Version

<link rel="stylesheet" href="https://media.lexmark.com/www/lxkfef/themes/elevate/v1.0.1/css/screen.min.css" crossorigin="anonymous">

Theme JS

Place the following after the link to the LXCore JavaScript at the bottom of page.

Current Version

<script src="https://media.lexmark.com/www/lxkfef/current/themes/elevate/js/apps.min.js"></script>

Specific Version

<script src="https://media.lexmark.com/www/lxkfef/themes/elevate/v1.0.1/js/apps.min.js"></script>

Basic examples

Header and Footer

The sitewide navigation and branding for Lexmark Elevate (elevate.lexmark.com)

Lexmark Support Theme

Version: 1.0.19

To start using the Support Theme, please add links below to their respective areas in the Web page markup.

Theme CSS

Place the following after the link to the LXCore styles in the <head>. Modify both the name (e.g., "support") and the version number (e.g., "v1.0.19") to match the one you wish to use.

Current Version

<link rel="stylesheet" href="https://media.lexmark.com/www/lxkfef/current/themes/support/css/screen.min.css" crossorigin="anonymous">

Specific Version

<link rel="stylesheet" href="https://media.lexmark.com/www/lxkfef/themes/support/v1.0.19/css/screen.min.css" crossorigin="anonymous">

Theme JS

Place the following after the link to the LXCore JavaScript at the bottom of page.

Current Version

<script src="https://media.lexmark.com/www/lxkfef/current/themes/support/js/apps.min.js"></script>

Specific Version

<script src="https://media.lexmark.com/www/lxkfef/themes/support/v1.0.19/js/apps.min.js"></script>

This section contains documentation around specific application patterns, such as product detail pages, the LPMD platform, and emails.

Lexmark.com eCommerce

Since Lexmark.com has a different target audience, the content and layout for these pages are different from PartnerNet. Reference the section below for designs specific to Lexmark.com. Non-ATG examples have been hidden, since country-specific 'Buy Online' sites are no longer available for our products.

Product detail pages

Devices (ATG)

An example of a device detail page for public Lexmark.com

Supplies (ATG)

An example of a supply detail page for public Lexmark.com

Accessories (ATG)

An example of an accessory detail page for public Lexmark.com

PartnerNet eCommerce

Since PartnerNet has a different target audience, the content and layout for these pages are different from Lexmark.com. Reference the section below for designs specific to PartnerNet.

Product detail pages

Devices

An example of a device detail page for PartnerNet

Supplies

An example of a supply detail page for PartnerNet

Accessories

An example of an accessory detail page for PartnerNet

Apps

An example of an app detail page for PartnerNet

eCommerce Global Patterns/Messaging

There are certain patterns, actions, and messaging that should be consistent across the Lexmark.com and PartnerNet eCommerce pages. Reference the documentation below for global purchasing actions and their corresponding messaging.

Support Website

Mocks for the initial redesign of the support website for Lexmark.

LPMD

This is an internal tool and has unique design patterns for its platform and audience. Reference the documentation below for LPMD patterns, actions, and corresponding messaging.

Product Photography Uploader

This is an internal tool and has unique design patterns for its platform and audience. Reference the documentation below for Product Photography Uploader patterns, actions, and corresponding messaging.

Lexmark.com Emails

The following templates have been optimized for responsive display and should be used when designing emails. An email.scss file exists within the FEF and should be linked within the HTML for proper and consistent styling.

Guidelines

Images saved as jpg and/or gif work best.
For resolution considerations, export images at twice their size and then restrict the size by half on the img tag.
It's important to always include the image alt tag and in-line n1 background color, as some email clients block images from loading.
When the email is ready to launch, remember to remove the QA/PROD/LOCAL notes that are needed when testing, and replace the placeholder text for title and description.
Follow our vertical rhythm patterns when manually adjusting in-line margins.
If expanding upon the email.scss file, the class styles should also be applied in-line.

Standard templates

Email UI Template

Reference HTML example for specific design patterns.

Layout #1

Example layout design for emails.

Layout #2

Example layout design for emails.

Lexmark Blog

New Blog Post

Email when new blog posts are available.

While we don't officially support any third party plugins or add-ons, we do offer some useful advice to help avoid potential issues in your projects.

Box-sizing

Some third party software, including Google Maps and Google Custom Search Engine, conflict with Bootstrap due to * { box-sizing: border-box; }, a rule which makes it so padding does not affect the final computed width of an element. Learn more about box model and sizing at CSS Tricks.

Depending on the context, you may override as-needed (Option 1) or reset the box-sizing for entire regions (Option 2).

/* Box-sizing resets
 *
 * Reset individual elements or override regions to avoid conflicts due to
 * global box model settings of Bootstrap. Two options, individual overrides and
 * region resets, are available as plain CSS and uncompiled Less formats.
 */

/* Option 1A: Override a single element's box model via CSS */
.element {
  -webkit-box-sizing: content-box;
     -moz-box-sizing: content-box;
          box-sizing: content-box;
}

/* Option 1B: Override a single element's box model by using a Bootstrap Less mixin */
.element {
  .box-sizing(content-box);
}

/* Option 2A: Reset an entire region via CSS */
.reset-box-sizing,
.reset-box-sizing *,
.reset-box-sizing *:before,
.reset-box-sizing *:after {
  -webkit-box-sizing: content-box;
     -moz-box-sizing: content-box;
          box-sizing: content-box;
}

/* Option 2B: Reset an entire region with a custom Less mixin */
.reset-box-sizing {
  &,
  *,
  *:before,
  *:after {
    .box-sizing(content-box);
  }
}
.element {
  .reset-box-sizing();
}

Bootstrap is downloadable in two forms, within which you'll find the following directories and files, logically grouping common resources and providing both compiled and minified variations.

jQuery required

Please note that all JavaScript plugins require jQuery to be included, as shown in the starter template. Consult our bower.json to see which versions of jQuery are supported.

Precompiled Bootstrap

Once downloaded, unzip the compressed folder to see the structure of (the compiled) Bootstrap. You'll see something like this:

bootstrap/
├── css/
│   ├── screen.css
│   ├── screen.css.map
│   ├── screen.min.css
│   ├── screen.min.css.map
│   ├── ie.css
│   ├── ie.css.map
│   ├── ie.min.css
│   ├── ie.min.css.map
│   ├── print.css
│   ├── print.css.map
│   ├── print.min.css
│   └── print.min.css.map
├── js/
│   ├──
│   └──
└── fonts/
    ├── glyphs/
    ├── action-icons.eot
    ├── action-icons.svg
    ├── action-icons.ttf
    ├── action-icons.woff
    └──  tp-hero/
         ├── tphero-black-webfont.eot
         ├── tphero-black-webfont.svg
         ├── tphero-black-webfont.ttf
         ├── tphero-black-webfont.woff
         ├── tphero-blackitalic-webfont.eot
         ├── tphero-blackitalic-webfont.svg
         ├── tphero-blackitalic-webfont.ttf
         ├── tphero-blackitalic-webfont.woff
         ├── tphero-bold-webfont.eot
         ├── tphero-bold-webfont.svg
         ├── tphero-bold-webfont.ttf
         ├── tphero-bold-webfont.woff
         ├── tphero-bolditalic-webfont.eot
         ├── tphero-bolditalic-webfont.svg
         ├── tphero-bolditalic-webfont.ttf
         ├── tphero-bolditalic-webfont.woff
         ├── tphero-extrabold-webfont.eot
         ├── tphero-extrabold-webfont.svg
         ├── tphero-extrabold-webfont.ttf
         ├── tphero-extrabold-webfont.woff
         ├── tphero-extrabolditalic-webfont.eot
         ├── tphero-extrabolditalic-webfont.svg
         ├── tphero-extrabolditalic-webfont.ttf
         ├── tphero-extrabolditalic-webfont.woff
         ├── tphero-light-webfont.eot
         ├── tphero-light-webfont.svg
         ├── tphero-light-webfont.ttf
         ├── tphero-light-webfont.woff
         ├── tphero-lightitalic-webfont.eot
         ├── tphero-lightitalic-webfont.svg
         ├── tphero-lightitalic-webfont.ttf
         ├── tphero-lightitalic-webfont.woff
         ├── tphero-medium-webfont.eot
         ├── tphero-medium-webfont.svg
         ├── tphero-medium-webfont.ttf
         ├── tphero-medium-webfont.woff
         ├── tphero-mediumitalic-webfont.eot
         ├── tphero-mediumitalic-webfont.svg
         ├── tphero-mediumitalic-webfont.ttf
         ├── tphero-mediumitalic-webfont.woff
         ├── tphero-regular-webfont.eot
         ├── tphero-regular-webfont.svg
         ├── tphero-regular-webfont.ttf
         ├── tphero-regular-webfont.woff
         ├── tphero-regularitalic-webfont.eot
         ├── tphero-regularitalic-webfont.svg
         ├── tphero-regularitalic-webfont.ttf
         ├── tphero-regularitalic-webfont.woff
         ├── tphero-semibold-webfont.eot
         ├── tphero-semibold-webfont.svg
         ├── tphero-semibold-webfont.ttf
         ├── tphero-semibold-webfont.woff
         ├── tphero-semibolditalic-webfont.eot
         ├── tphero-semibolditalic-webfont.svg
         ├── tphero-semibolditalic-webfont.ttf
         └── tphero-semibolditalic-webfont.woff

Getting started

How to start

CDN Links

CSS

LXCore CSS

JavaScript

JQuery JS

LXCore JS

Accessibility

Skip navigation

Nested headings

Color contrast

Additional resources

Browser and device support

Supported browsers

Mobile devices

Desktop browsers

Internet Explorer 8 and 9

Internet Explorer 8 and Respond.js

Respond.js and cross-domain CSS

Respond.js and file://

Respond.js and @import

Internet Explorer 8 and box-sizing

Internet Explorer 8 and @font-face

IE Compatibility modes

Internet Explorer 10 in Windows 8 and Windows Phone 8

Safari percent rounding

Modals, navbars, and virtual keyboards

Overflow and scrolling

iOS text fields and scrolling

Virtual keyboards

Navbar Dropdowns

Browser zooming

Sticky :hover/:focus on mobile

Printing

Android stock browser

Select menus

Validators

Community

Bootstrap disabling responsiveness

Steps to disable page responsiveness

Bootstrap template with responsiveness disabled

Bootstrap license FAQs

Basic template

Themes

Lexmark Theme

Theme CSS

Current Version

Specific Version

Theme JS

Current Version

Specific Version

Basic examples

Header and Footer

Containers

Lexmark PartnerNet Theme

Theme CSS

Current Version

Specific Version

Theme JS

Current Version

Specific Version

Basic examples

Header and Footer

Lexmark Elevate Theme

Theme CSS

Current Version

Specific Version

Theme JS

Current Version

Specific Version

Basic examples

Header and Footer

Lexmark Support Theme

Theme CSS

Current Version

Specific Version

Theme JS

Current Version

Specific Version

Respond.js and `file://`

Respond.js and `@import`

Sticky `:hover`/`:focus` on mobile