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

CSS class vs id

Guideline (rule?) about using class or id for an element

Main point is that id must be unique and can appear once only in a page. So why use ids? You can never know when you will need to display that element more than once on a page.

Tiki guideline (or rule?): only use classes, never use ids

Please argue with this statement 😊 (the goal is to have an easy to follow rule).

Isn't now pretty much a "best practice" that ids shouldn't be given CSS style properties? Their CSS style properties are too hard to override with class properties without resorting to !important, etc.

Overview of the main elements classes changes

Buttons

How to approach and handle buttons

Discusson points:

1.1.1.1. when should an element be a button

1.1.1.2. the default classes for a Tiki button

What are the default classes?

1.1.1.3. how to manage externals (eg: jquery dialogs)

External sources come with their own styling. How is this neutralized and turned into Tiki styling?

1.1.1.4. how to customize (write down how to do it)

eg: I dont like that the edit page save button class is btn-primary, I want it to look like btn-warning, how do I do that in my css file without modifying any other source files

[-] lib/

<span class="button" ...>

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

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