Download backend

Download html documentation

Install as any other plugins:

$ asciidoc --backend install bootstrap-<version>.zip

	<version> is to be replaced by the latest version available of the backend. Currently is 4.5.0

The Asciidoc Bootstrap backend standard version included : version 3.3.4 ( themes/ ) of the default, flatly, readable, cerulean, united and darkly themes from Bootswatch template provider. version 3.3.4 ( bootstrap/, less/bootstrap/ ) of Bootstrap. version 4.3.0 ( fonts/, /less/font-awesome/ ) of Font-Awesome. version 2.0.1 ( fonts/, less/ionicons/ ) of Ionicons. version 2.1.2 ( fonts/, less/octicons/ ) of Octicons. version 1.11.1 of jQuery. version 1.2 of jQuery UItoTop plugin. version 0.8 of jQuery TableOfContents plugin. version 5.2.0 of jQuery mmenu plugin. version 1.1.5 of jQuery bootstrapThemeSwitcher plugin. version 1.4.1 of jQuery Cookie plugin.

1.1. Themes from Bootswatch a free template provider

AsciiDoc-Bootstrap backend v4 standard distribution included these following templates with pre-compiled CSS (uncompressed and/or minified) and default behavior :

• Admonition blocks used Font-Awesome icons font
• Support both Glyphicon, Font-Awesome, Ionicons and Octicons icons font

Figure 1.1. Basic Flatly theme

Figure 1.2. Basic Readable theme

Figure 1.3. Basic Cerulean theme

Figure 1.4. Basic United theme

Figure 1.5. Basic Sandstone theme

Figure 1.6. Basic Darkly theme

When you will installed the asciidoc bootstrap backend, you will find the following file structure and contents.

 bootstrap/
  ├── bootstrap/
  │   ├── css/
  │   ├── fonts/
  │   └── js/
  ├── docs/
  ├── fonts/
  ├── images/
  │   ├── icons/
  │   │   ├── callouts/
  │   │   ├── ui.totop.png
  │   │   └── favicon.ico
  ├── javascripts/
  │   ├── asciidoc.js
  │   ├── html5shiv.js
  │   ├── html5shiv.min.js
  │   ├── jquery.bootstrapThemeSwitcher.js
  │   ├── jquery.cookie.js
  │   ├── jquery.js
  │   ├── jquery.min.js
  │   ├── jquery.mmenu.min.all.js
  │   ├── jquery.tableofcontents.min.js
  │   ├── jquery.ui.totop.js
  │   ├── jquery.ui.totop.min.js
  │   ├── respond.js
  │   └── respond.min.js
  ├── less/
  │   ├── asciidoc/
  │   │   ├── admonition-iconsfont.less
  │   │   ├── admonition-text.less
  │   │   ├── common.less
  │   │   ├── iconsfont.less
  │   │   └── pygments.less
  │   ├── bootstrap/
  │   ├── font-awesome/
  │   ├── ionicons/
  │   ├── octicons/
  │   ├── asciidoc-bootstrap.less
  │   └── variable.less
  ├── stylesheets/
  │   ├── asciidoc-bootstrap.cerulean.css
  │   ├── asciidoc-bootstrap.cerulean.min.css
  │   ├── asciidoc-bootstrap.darkly.css
  │   ├── asciidoc-bootstrap.darkly.min.css
  │   ├── asciidoc-bootstrap.css
  │   ├── asciidoc-bootstrap.min.css
  │   ├── asciidoc-bootstrap.flatly.css
  │   ├── asciidoc-bootstrap.flatly.min.css
  │   ├── asciidoc-bootstrap.readable.css
  │   ├── asciidoc-bootstrap.readable.min.css
  │   ├── asciidoc-bootstrap.united.css
  │   ├── asciidoc-bootstrap.united.min.css
  │   ├── asciidoc-bootstrap.sandstone.css
  │   ├── asciidoc-bootstrap.sandstone.min.css
  │   ├── jquery.mmenu.all.css
  │   ├── pygments.css
  │   ├── pygments.monokai.css
  │   ├── pygments.pastie.css
  │   └── ui.totop.css
  └── themes
      ├── cerulean/
      ├── darkly/
      ├── default/
      ├── flatly/
      ├── readable/
      ├── sandstone/
      └── united/

Head to the docs sections for more information and examples.

3.1. Source Code Highlight

The Pygments syntax highlighter can be used for xhtml11, html5 and bootstrap outputs.

	Since version 3.1.0 you have ability to use any of the Pygments 1.5 themes provided at document build time.

The Pygments syntax highlighter can be used for xhtml11, html5 and bootstrap outputs (set the source-highlighter attribute to pygments).

Until now, AsciiDoc allow only to use Pygments with a default theme that look like to emacs theme. We have no way to customize this at document build time, unless editing contents of ./stylesheets/pygments.css file.

AsciiDoc-Bootstrap backend introduce in version 3.1.0 the new attribute pygments-style to change Pygments stylesheet at document build time.

	Credit to AsciiDoctor GH-637 issue.

By default, AsciiDoc-Bootstrap used the AsciiDoc pygments theme. To change the style, set the pygments-style attribute and assign it the alternate style’s name.

To see what pygments styles you have available, open a terminal and type: $ pygmentize -L styles It will output the style names and brief descriptions. Pygments 1.5 provides 19 themes, but only 3 pre-defined stylesheets are available in standard AsciiDoc-Bootstrap backend distribution (default, pastie, monokai). Here are how to setup other themes. Open a terminal and type: $ pygmentize -f html -S <theme> -a .highlight where <theme> is one of those listed by Pygments (-L style). Copy output to the AsciiDoc-Bootstrap install dir stylesheets folder in a file named pygments.<theme>.css. (e.g. pygments.tango.css)

In the example document below, we used the monokai style as main theme, and pastie as local theme to highlight a block of CSS code.

	Pygments token <span> tags will not use CSS classes, but inline styles. This is not recommended for larger pieces of code since it increases output size by quite a bit.

	The source-highlighter args attribute allows the inclusion of arbitrary (highlighter dependent) command options.

== Alternate Pygments Theme
:source-highlighter: pygments
:pygments-style: monokai

[source,php,numbered]
.Using global theme [label label-default]#{pygments-style}#
----
<?php
use Symfony\Component\Finder\Finder;

$finder = new Finder();
$finder->files()->in(__DIR__);

foreach ($finder as $file) {
    // affiche le chemin absolu
    print $file->getRealpath()."\n";
    // affiche le chemin relatif d'un fichier, sans le nom du fichier
    print $file->getRelativePath()."\n";
    // affiche le chemin relatif du fichier
    print $file->getRelativePathname()."\n";
}
----


[source,css]
.Using local theme [label label-default]#{local-css-style}#
----
/*
|--------------------------------------------------------------------------
| UItoTop jQuery Plugin 1.2
| http://www.mattvarone.com/web-design/uitotop-jquery-plugin/
|--------------------------------------------------------------------------
*/

#toTop {
        display:none;
        text-decoration:none;
        position:fixed;
        bottom:10px;
        right:10px;
        overflow:hidden;
        width:51px;
        height:51px;
        border:none;
        text-indent:100%;
        background:url(../images/icons/ui.totop.png) no-repeat left top;
}

#toTopHover {
        background:url(../images/icons/ui.totop.png) no-repeat left -51px;
        width:51px;
        height:51px;
        display:block;
        overflow:hidden;
        float:left;
        opacity: 0;
        -moz-opacity: 0;
        filter:alpha(opacity=0);
}

#toTop:active, #toTop:focus {
        outline:none;
}
----

Renders

Using global theme monokai. 

<?php
use Symfony\Component\Finder\Finder;

$finder = new Finder();
$finder->files()->in(__DIR__);

foreach ($finder as $file) {
    // affiche le chemin absolu
    print $file->getRealpath()."\n";
    // affiche le chemin relatif d'un fichier, sans le nom du fichier
    print $file->getRelativePath()."\n";
    // affiche le chemin relatif du fichier
    print $file->getRelativePathname()."\n";
}

/*
|--------------------------------------------------------------------------
| UItoTop jQuery Plugin 1.2
| http://www.mattvarone.com/web-design/uitotop-jquery-plugin/
|--------------------------------------------------------------------------
*/

#toTop {
        display:none;
        text-decoration:none;
        position:fixed;
        bottom:10px;
        right:10px;
        overflow:hidden;
        width:51px;
        height:51px;
        border:none;
        text-indent:100%;
        background:url(../images/icons/ui.totop.png) no-repeat left top;
}

#toTopHover {
        background:url(../images/icons/ui.totop.png) no-repeat left -51px;
        width:51px;
        height:51px;
        display:block;
        overflow:hidden;
        float:left;
        opacity: 0;
        -moz-opacity: 0;
        filter:alpha(opacity=0);
}

#toTop:active, #toTop:focus {
        outline:none;
}

Asciidoc quoted text attributes and Bootstrap labels

[red]#Obvious# and [big red yellow-background]*very obvious*.

Renders:

Obvious and very obvious.

A bootstrap [label label-warning]#warning# label.

Renders:

A bootstrap warning label.

A sidebar is a short piece of text presented outside the narrative flow of the main text. The sidebar is normally presented inside a bordered box to set it apart from the main text.

.An Example Sidebar
************************************************
Any AsciiDoc SectionBody element (apart from
SidebarBlocks) can be placed inside a sidebar.
************************************************

Renders:

You may also used the attribute role to control padding and rounded corners.

With well-sm role:

.An Example Sidebar
[role="well-sm"]
****
Any AsciiDoc SectionBody element (apart from
SidebarBlocks) can be placed inside a sidebar.
****

Renders:

With well-lg role:

.An Example Sidebar
[role="well-lg"]
****
Any AsciiDoc SectionBody element (apart from
SidebarBlocks) can be placed inside a sidebar.
****

Renders:

Open blocks are special: they are used to generate document abstracts, book part introductions and more.

	Previous version 3, used it to simulate multi columns. Version 4 dropped this behavior. Don’t be afraid, this feature is still possible using the standard Bootstrap classes like .col-md-* and so on.

While not always necessary, sometimes you need to put your DOM in a box. For those situations, try the panel component.

<div class="panel panel-default">
  <div class="panel-body">
    Basic panel example
  </div>
</div>

[panel]
--
Basic panel example
--

<div class="panel panel-default">
  <div class="panel-heading">
    Panel title
  </div>
  <div class="panel-body">
    Panel content
  </div>
</div>

[panel]
.Panel title
--
Panel content
--

<div class="panel panel-primary">
  <div class="panel-heading">
    <h3 class="panel-title">Panel title</h3>
  </div>
  <div class="panel-body">
    Panel content
  </div>
</div>

[panel,primary]
.Panel title
--
Panel content
--

<div class="panel panel-success">
  <div class="panel-heading">
    <h3 class="panel-title">Panel title</h3>
  </div>
  <div class="panel-body">
    Panel content
  </div>
</div>

[panel,success]
.Panel title
--
Panel content
--

<div class="panel panel-info">
  <div class="panel-heading">
    <h3 class="panel-title">Panel title</h3>
  </div>
  <div class="panel-body">
    Panel content
  </div>
</div>

[panel,info]
.Panel title
--
Panel content
--

<div class="panel panel-warning">
  <div class="panel-heading">
    <h3 class="panel-title">Panel title</h3>
  </div>
  <div class="panel-body">
    Panel content
  </div>
</div>

[panel,warning]
.Panel title
--
Panel content
--

<div class="panel panel-danger">
  <div class="panel-heading">
    <h3 class="panel-title">Panel title</h3>
  </div>
  <div class="panel-body">
    Panel content
  </div>
</div>

[panel,danger]
.Panel title
--
Panel content
--

9.4. Learn More

Behind the scene

Build this {docfile} ^[1]

	See [2] for docfile attribute.

with :

html5 backend

$ asciidoc.py
  -b html5
  -a linkcss
  -a stylesdir=./stylesheets
  -a scriptsdir=./javascripts
  {docfile}

	You will have tons of WARNING because AsciiDoc does not support the panel-style open block. But the result is not so bad. Check yourself: select the AsciiDoc entry in Themes menu.

asciidoc: WARNING: panels.asciidoc: line 40: missing style: [blockdef-open]: panel
asciidoc: WARNING: panels.asciidoc: line 78: missing style: [blockdef-open]: panel
asciidoc: WARNING: panels.asciidoc: line 116: missing style: [blockdef-open]: panel
asciidoc: WARNING: panels.asciidoc: line 151: missing style: [blockdef-open]: panel
asciidoc: WARNING: panels.asciidoc: line 186: missing style: [blockdef-open]: panel
asciidoc: WARNING: panels.asciidoc: line 221: missing style: [blockdef-open]: panel
asciidoc: WARNING: panels.asciidoc: line 256: missing style: [blockdef-open]: panel

bootstrap backend

$ asciidoc.py
  -b bootstrap
  -a linkcss
  -a stylesdir=./stylesheets
  -a scriptsdir=./javascripts
  -a theme=flatly
  -a navbar=fixed
  -a totop
  {docfile}

	You will have a WARNING because the theme used (e.g. flatly) is a Bootswatch theme, and not a AsciiDoc Theme.

asciidoc: WARNING: missing theme: flatly

Provide contextual feedback messages for typical user actions with the handful of available and flexible alert messages.

10.1. Basic example

	Alerts don’t have default classes, only base and modifier classes. A default gray alert doesn’t make too much sense, so you’re required to specify a type via contextual class. Choose from success, info, warning, or danger.

AsciiDoc Code. 

[alert,success]
.Well done!
--
You successfully read this important alert message.
--

Example 10.1. Alert with success contextual state class

You successfully read this important alert message.

AsciiDoc Code. 

[alert,info]
.Heads up!
--
This alert needs your attention, but it's not super important.
--

Example 10.2. Alert with info contextual state class

This alert needs your attention, but it’s not super important.

AsciiDoc Code. 

[alert,warning]
.Warning!
--
Better check yourself, you're not looking too good.
--

Example 10.3. Alert with warning contextual state class

Better check yourself, you’re not looking too good.

AsciiDoc Code. 

[alert,danger]
.Oh snap!
--
Change a few things up and try submitting again.
--

Example 10.4. Alert with danger contextual state class

Change a few things up and try submitting again.

[alert,warning,true]
.Warning!
--
Better check yourself, you're not looking too good.
--

10.3. Learn More

Behind the scene

Build this {docfile} ^[3]

	See [4] for docfile attribute.

with :

html5 backend

$ asciidoc.py
  -b html5
  -a linkcss
  -a stylesdir=./stylesheets
  -a scriptsdir=./javascripts
  {docfile}

	You will have tons of WARNING because AsciiDoc does not support the alert-style open block. But the result is not so bad. Check yourself: select the AsciiDoc entry in Themes menu.

asciidoc: WARNING: alerts.asciidoc: line 35: missing style: [blockdef-open]: alert
asciidoc: WARNING: alerts.asciidoc: line 57: missing style: [blockdef-open]: alert
asciidoc: WARNING: alerts.asciidoc: line 79: missing style: [blockdef-open]: alert
asciidoc: WARNING: alerts.asciidoc: line 101: missing style: [blockdef-open]: alert
asciidoc: WARNING: alerts.asciidoc: line 126: missing style: [blockdef-open]: alert

bootstrap backend

$ asciidoc.py
  -b bootstrap
  -a linkcss
  -a stylesdir=./stylesheets
  -a scriptsdir=./javascripts
  -a theme=flatly
  -a navbar=fixed
  -a totop
  {docfile}

	You will have a WARNING because the theme used (e.g. flatly) is a Bootswatch theme, and not a AsciiDoc Theme.

asciidoc: WARNING: missing theme: flatly

TIP, NOTE, IMPORTANT, WARNING and CAUTION admonishment paragraph styles are generated by placing NOTE:, TIP:, IMPORTANT:, WARNING: or CAUTION: as the first word of the paragraph.

Since version 1.2.0, admonitionblock used alert-block Twitter Bootstrap styles. With support of icons font, it’s now time to change the behavior and default styles.

To compare three render categories, we will use the same file source ^[5].

To use Font-Awesome icons font rather than PNG images, build your AsciiDoc source files with attribute iconsfont - use -a iconsfont=font-awesome

14.1. Admonition NOTE block

NOTE: This is an example note.

[NOTE]
Alternatively, you can specify the paragraph admonition style explicitly using an AttributeList element.

Renders:

	This is an example note.

	Alternatively, you can specify the paragraph admonition style explicitly using an AttributeList element.

14.2. Admonition IMPORTANT block

IMPORTANT: This is another example more important.

Renders:

	This is another example more important.

14.3. Admonition CAUTION block

CAUTION: This is another example important but less.

Renders:

	This is another example important but less.

14.4. Admonition WARNING block

WARNING: This is a warning example.

Renders:

	This is a warning example.

14.5. Admonition NOTE custom icon block

[icon="./images/icons/example.png"]
NOTE: What lovely war.

Renders:

	What lovely war.

14.6. Admonition TIP block

[TIP]
.A TIP admonition block
=====================================================================
Qui in magna commodo, est labitur dolorum an. Est ne magna primis
adolescens.

. Fusce euismod commodo velit.
. Vivamus fringilla mi eu lacus.
  .. Fusce euismod commodo velit.
  .. Vivamus fringilla mi eu lacus.
. Donec eget arcu bibendum
  nunc consequat lobortis.
=====================================================================

Renders:

	A TIP admonition block
	Qui in magna commodo, est labitur dolorum an. Est ne magna primis adolescens. Fusce euismod commodo velit. Vivamus fringilla mi eu lacus. Fusce euismod commodo velit. Vivamus fringilla mi eu lacus. Donec eget arcu bibendum nunc consequat lobortis.

@import "asciidoc/admonition-iconsfont.less";

When the icons attribute is enabled, callouts list are rendered with the numbered bullet icons like AsciiDoc. But it will not using images in standard images\icons directory.

AsciiDoc-Bootstrap backend 3.2.0 by introducing this standard AsciiDoc feature will use the badge css rule look like to draw bullet icons (circles).

	Credit to AsciiDoctor GH-114 issue for cool idea.

Here is an example that don’t use images but Bootstrap badges :

 .MS-DOS directory listing
 -----------------------------------------------------
 10/17/97   9:04         <DIR>    bin
 10/16/97  14:11         <DIR>    DOS            <1>
 10/16/97  14:40         <DIR>    Program Files
 10/16/97  14:46         <DIR>    TEMP
 10/17/97   9:04         <DIR>    tmp
 10/16/97  14:37         <DIR>    WINNT
 10/16/97  14:25             119  AUTOEXEC.BAT   <2>
  2/13/94   6:21          54,619  COMMAND.COM    <2>
 10/16/97  14:25             115  CONFIG.SYS     <2>
 11/16/97  17:17      61,865,984  pagefile.sys
  2/13/94   6:21           9,349  WINA20.386     <3>
 -----------------------------------------------------
[role="listing"]
 <1> This directory holds MS-DOS.
 <2> System startup code for DOS.
 <3> Some sort of Windows 3.1 hack.

which renders:

MS-DOS directory listing. 

10/17/97   9:04         <DIR>    bin
10/16/97  14:11         <DIR>    DOS            
10/16/97  14:40         <DIR>    Program Files
10/16/97  14:46         <DIR>    TEMP
10/17/97   9:04         <DIR>    tmp
10/16/97  14:37         <DIR>    WINNT
10/16/97  14:25             119  AUTOEXEC.BAT   
 2/13/94   6:21          54,619  COMMAND.COM    
10/16/97  14:25             115  CONFIG.SYS     
11/16/97  17:17      61,865,984  pagefile.sys
 2/13/94   6:21           9,349  WINA20.386     

	If you want to customize this bullet icons look like, please add a .callout CSS rule in a custom stylesheet, and apply it with -a stylesheet=<your_stylesheet>.

	If you want to customize this specific callout list, add a role (e.g: listing), and the following CSS rule in a custom stylesheet. .colist.arabic.listing > ul { list-style: none; }

	Your custom stylesheet MUST be located in the {stylesdir}.

Hypertext links to files on the local file system are specified using the link inline macro.

link:<target>[<caption>]

The link macro generates relative URLs. The link macro <target> is the target file name (relative to the file system location of the referring document). The optional <caption> is the link’s displayed text. If <caption> is not specified then <target> is displayed.

link:get-started.html[]

Renders:

get-started.html

link:get-started.html[Start]

Renders:

Start

If you want more enhancement and focus on specific link, you want probably to use buttons links as provided by Bootstrap.

It’s now possible with this major version 3 of AsciiDoc-Bootstrap backend.

Let’s restart our example, with the single link, and apply it a button style.

link:get-started.html[role="primary"]

Renders:

Change the text

link:get-started.html["Start Tour",role="primary"]

link:get-started.html[caption="Start Tour",role="primary"]

Renders:

	You have certainly understood that all button color style may be applied with the role attribute. (inverse, default, primary, info, success, warning, danger).

You want probably more than just a button. Adding an icon will improve again more the look and feel !

link:get-started.html["Start Tour",role="info",icon="glyphicon-play-circle"]

Renders:

And finally, choose what side you want to put your icon.

link:get-started.html["Whats wrong",role="danger",icon="glyphicon-remove-circle",options="right,white"]

Renders:

Inline images are inserted into the output document using the image macro.

image:<target>[<attributes>]

The contents of the image file <target> is displayed.

image::screenshots/navbar-default-sample.png[role="thumbnail",options="align,responsive"]

Renders:

Try several resolution and see what happens with or without responsive option.

AsciiDoc-Bootstrap backend 3.1.0 introduces a new inline macro for inserting an icon at an arbitrary place in paragraph content.

	Credit to AsciiDoctor GH-529 issue.

	AsciiDoc-Bootstrap backend 4.0 has dropped this icon inline macro, to keep a better compatibility with other backends. Use then the image inline macro with additional attributes.

Right now we are blessed with many icon fonts that continue to grow with every release, like Glyphicons, Font-Awesome, Ionicons, and more again …

AsciiDoc-Bootstrap backend 4.0 support these three icon fonts. Valid iconsfont attribute values are : glyphicon, font-awesome, and ionicons.

	Our inline image macro is similar to the standard Asciidoc inline image macro with one exception: If the iconsfont attribute is set, the macro will translate image to a font-based icon result.

image:<target>[<attributes>]

The contents of the image <target> is displayed.

Here is an example that inserts a calendar icon in front of a blog entry and its published date.

image:icons/font-awesome/calendar.png[alt="calendar",icon="calendar",size="4x",iconsfont="font-awesome"] by Laurent Laville, published on November 21, 2013

Renders:

by Laurent Laville, published on November 21, 2013

	AsciiDoc-Bootstrap 4.0 did not used anymore the open block to simulate multi-columns. We used now the standard Bootstrap classes col-md-* and so on.

Here is another example that display two columns on medium device (greater than 992 pixels)

AsciiDoc Code. 

[role="col-md-3"]
====
[panel]
--
*About*
http://glyphsearch.com/[GlyphSearch]

image:icons/font-awesome/mobile.png[alt="mobile",icon="mobile",size="lg",iconsfont="font-awesome"]
image:icons/font-awesome/tablet.png[alt="tablet",icon="tablet",size="2x",iconsfont="font-awesome"]
image:icons/font-awesome/laptop.png[alt="laptop",icon="laptop",size="3x",iconsfont="font-awesome"]
image:icons/font-awesome/desktop.png[alt="desktop",icon="desktop",size="3x",iconsfont="font-awesome"]
--
====

[role="col-md-9"]
====
*GlyphSearch: Improving the Search for Icon Fonts*

GlyphSearch is a site that allows you to search
Font Awesome, Glyphicons, and Ionicons simultaneously.
====

unfloat::[]

And another example with three columns on medium device (greater than 992 pixels)

AsciiDoc Code. 

[role="col-md-2"]
====
[yellow]#image:icons/font-awesome/font.png[alt="font",icon="font",size="9x",iconsfont="font-awesome"]#
====

[role="col-md-8"]
[quote,http://fontello.com/]
____
*Fontello*

This http://fontello.com/[tool] lets you combine icon webfonts for your own project. With fontello you can:

* shrink glyph collections, minimizing font size
* merge symbols from several fonts into a single file
* access large sets of professional-grade open source icons
____

[role="col-md-2"]
.About
****
http://fontello.com/[Fontello], the icon font scissors.
****

unfloat::[]

	All icon fonts do not support same icon names. Be carefull if you switch to another icons font.

AsciiDoc-Bootstrap backend 4.0.0 introduces a new inline macro that implement the Bootstrap Progress Component.

	Stacked progress bar is not supported.

progess:<target>[<attributes>]

The contents of the progress <target> is used to draw percent of progress bar completed (Must be numeric and between 0 and 100).

	There is no fallback strategy to build a progress bar with html5 or any other backends.

If you decide to modify LESS source files, remember that switching from one theme to another require only to change theme variable at line 2 in following file.

Source file less/asciidoc-bootstrap.less. 

@import "variables.less";
@theme:     "default";
@themesdir: "../themes/@{theme}";

// Bootstrap 3.3
@import "bootstrap/bootstrap.less";
@import "@{themesdir}/variables.less";

// Font-Awesome 4.3
@import "font-awesome/font-awesome.less";

// Ionicons 2.0
@import "ionicons/ionicons.less";

// Octicons 2.1 with '@octicons-font-path' modified
@import "octicons/octicons.less";

// AsciiDoc 8.6
@import "asciidoc/common.less";
@import "asciidoc/pygments.less";
@import "asciidoc/iconsfont.less";
//@import "asciidoc/admonition-text.less";
@import "asciidoc/admonition-iconsfont.less";

If you don’t want to use Font-Awesome, just remove or comment line 10.

//@import "font-awesome/font-awesome.less";

	Be careful, that admonition block used Font-Awesome by default (see file asciidoc/admonition-iconsfont.less )

If you don’t want to use Ionicons, just remove or comment line 13.

//@import "ionicons/ionicons.less";

If you don’t want to use Octicons, just remove or comment line 16.

//@import "octicons/octicons.less";