History: Bootstrapping WikiPlugins

As I see myself forced to use WYSIWYG on dev.t.o, I am a bit puzzled, how to use this together with bootstrap.
Don't get me wrong: I find WYSIWYG a very important feature marketingwise - today just a "must have". And CKE Editor seems to bestate of the art, used by a lot of projects. But same time, I do not like to work with it. It simply costs a lot of extra time to fix the page layout in the html source code and the page layout never gets where I want to.
Tikis original WikiSyntax with WikiPlugin is simply much more  reliable and efficient than the WYSIYG - especially once you got used to it.

Independantly of using WYSIWYG or not, we need a way to implement the various Bootstrap Elements into Tiki without the need for our users to hack them manually in HTML.

That means, we need some new WikiPlugins with decent parameters, to make it easy to use them.
Preferably we find a way to represent the Bootstrap grid (-column-) classes with obvious and easy to remember parameters, to make it easy to fit elements into the grid.

I see without a number of WikiPlugins - all very similarly structured - we will not come very much further in providing an easy to use half-self-explaining system for non-techie users.

List of WikiPlugins to either extend or newly to code:

• Buttons, Blocklevelbuttons, Dropdownbuttons
• Blockquotes
• Tables
• Forms and Inputs (more integrated in other features like tracker or jquery elements)
• Navs, Pills, Breadcrumbs, Pagination
• Indicators, Alerts (Boxes)
• Labels
• Badges with smarty elements (for ex showing numbers of members)
• Progress Bars
• Containers
• Lists
• Panels and Wells

See here an overview of the Bootstrap elements on a Tikisite - HTML coded and still with a few css errors:

bootstrapped.fabricius.me - Amelia Example

Original (non-Tiki):

bootswatch.com - Amelia Example

Basis from Twitter Bootstrap:

getbootstrap.com - Components