This page documents Bootstrap classes transition targeted for Tiki 13 and onwards to help Tiki themers and designers.

Bootstrap files

Location: vendor/bootstrap/

To include bootstrap in a tiki theme, create a theme css file (eg. tiki-bootstrap.css) in the following folder: styles/

In the created css file use the @import css function before any css setting as described below:

/*Import Bootstrap*/
@import url("../vendor/bootstrap/dist/css/bootstrap.css");

css selectors

use classes, don't use ids - Tiki uses id selectors only in some core areas (eg: to define main zones). Feature specific styling should not include id selectors.

[+] Discussion

Styling of external sources

External sources come with their own styling. How is this neutralized and turned into Tiki styling?
Vendor (external) source codes contain lots of own formatting. This causes problems when trying to achieve a unified look&feel. For example jquery-ui is nice, but has its own styling. Using bootstrap how will a jquery-ui dropdown will look the same as a dropdown anywhere else in Tiki? Or a button?

One way is to simply add the needed classes, stop and override the usage of external css. This might work for buttons, tables, hyperlinks, etc, but how about divs?

Overview of the main elements classes changes

Buttons

How to approach and handle buttons

1.1.1.1. when should an element be a button or a link

Tiki sometimes uses hyperlinks ( a> tag), sometimes input type submit, sometime buttons

How to unify?

1.1.1.2. usage of navbar

Bootstrap has a navbar component (http://getbootstrap.com/components/#navbar) that could be used as a standard background for buttons.

1.1.1.3. default classes for a Tiki button

A way could be to agree on a naming convention, assign type or class accordingly in tiki templates, than use the smarty function to add the bootstrap class for styling.
An approach could be for example according to functionality:

• Action buttons that result in a commit to the database -> tiki class/type name: "button-action". Use smarty to add btn-primary class for styling
• Cancel action buttons (eg: Cancel Edit) -> tiki class/type name="cancel-button". Use btn-default bootstrap class for styling
• Query buttons (list something, run a report, etc) -> tiki class/type name="button-query". Use btn-default bootstrap class for styling
• Navigation buttons (eg: jump to another screen/feature) -> tiki class/type name="button-navigation". Use btn-default bootstrap class for styling.

issue #1: Bootstrap offers button style and size options, which one to pick? See http://getbootstrap.com/css/#buttons

• btn-default seems ok for most buttons
• btn-primary requiers additional css sytling to have white color for links on buttons

issue #2: use span tag or add class directly in the element?

1.1.1.4. how to customize

eg: I dont like that on the edit page the save button class is btn-primary, I want it to look like btn-warning, how do I do that without modifying php or tpl source files?

[-] lib/

<span class="button" ...>

<span class="btn button" ...>

<a class="btn" data-role="button" ...>

Overview of grid layout issues, etc.

These changes will be made in templates/layouts/bs_grid (or some name indicating Bootstrap grid compatibility. At issue is where to add class="row" container divs.

In parallel with this, presumably the idea of moving everything in the center column to modules will happen. This will simplify the template and give a lot of flexibility to page layout as well.

Overall page

This includes the top module zone, topbar module zone, side columns, center content (less div#role_main, which should be addressed separately), page bottom module zone (bottom of center column), and footer (bottom module zone).

Page center content (div#role_main)

gezza: The classes on layout-view.tpl are going to be simplified or we keep them? What is the plan for shadowlayers, fullscreen, fixedwith? Clearfix classes?

IMO (), we can have several layouts and the designer or site admin can choose which to use, or can add another. For example:

• Responsive_fivealive: This one enables replication of the current Fivealive style (has extra divs needed for full-width header and footer background graphics, but fixed-width content). Within each - header, middle, and footer - of course the areas are responsive.
• Responsive_middle: Simpler than the Fivealive layout, but has support for current Tiki layout of distinct header, middle and footer.
• Responsive_simple: Essentially one large container that depends on wiki code, etc. for layout as well as content.
• Other responsive variants

These templates/layouts/responsive_fivealive.tpl etc. layouts can be added or removed as we experiment with the possibilities.

In my opinion, there's no particular reason to keep old divs and div classes like the shadow divs in layouts other than Classic. If one goal of being Bootstrap compatible is to attract devs and designers who are familiar with Bootstrap, we should provide templates that are clean and familiar as much as possible, not cluttered. Also, Bootstrap provides for the "full-width" and "fixed-width" properties, so I don't think we need explicit divs/classes distinct from Bootstrap's.

To keep these layouts simple I guess the layout_view.tpl has to be clean of any functionality other than layout arrangement. If there is other functionality, logics inside, than it would become hard to maintain them as one would need to copy functionality changes all over the different layout_view.tpl files. So these need to be moved out to separate tpls?:

• share
• tell a friend
• error report
• full screen?
• social networks
• google analytics
• endbody code?
• js?

Any thoughts on changes affecting Tiki module zones? (Top, Topbar, Pagetop, Left, Right, Pagebottom, Bottom). If someone new comes, this might be confusing having also header, main, middle, footer etc.

[+] sample starter layout

<div class="main container">
		<div class="header row">
			<div class="col-md-12">
				{modulelist zone=top}
			</div>
		<div class="middle row">
			<div class="col-md-12">
				<div class="middle-topbar row">
					<div class="col-md-12">
						{modulelist zone=topbar}
					</div>
				<div class="middle-leftcenterright row">
					<div class="middle-left col-md-2">
						{block name=zone_left}
						{modulelist zone=left}
					</div>
					<div class="middle-center col-md-8">
						<div id="tiki-center" {*id needed for ajax editpage link*}" class="row">
							<div class="middle-center-pagetop col-md-12">
								{modulelist zone=pagetop}
							</div>
								<div id="role_main class="middle-center-content col-md-12">
									{block name=title}{/block}
									{block name=content}{/block}
									{block name=show_content}{/block}
								</div>
							<div id="middle-center-pagebottom col-md-12">
								{modulelist zone=pagebottom}
							</div>
						</div>
					</div>
					<div class="middle-right col-md-2">
						{block name=zone_right}
						{modulelist zone=right}
					</div>
				</div>
			</div>
		</div>
		<div class="footer row">
			<div class="col-md-12">
				{modulelist zone=bottom class="content modules" bidi=y}
			</div>
		</div>
	</div>