The goal here is to make the meaning of button colors in Tiki more intuitive and consistent. In the Bootstrap update to version 4, part of Tiki 19, some button class names and default colors have changed from Bootstrap 3. (See https://getbootstrap.com/docs/4.0/components/buttons/ .) The meanings conveyed by button colors may not be as clear now as they were in Bootstrap 3, when the default button color was essentially neutral and colors were used for special meaning and, even with Tiki and Bootstrap 3, there wasn't a clear pattern of button color use.

For this reason, the button classes are being organized in the .tpl files, etc. and will be in the HTML and they will be most apparent in the Default Bootstrap theme. Other themes, of course, can style buttons as they please but the hope is that the organization of button colors makes sense and will benefit themes and users even if the themes' palettes vary from the Bootstrap default.

One suggestion is that sites could assign an admin theme that shows the button colors most clearly, and another site theme with perhaps less obvious colors that are toned down from the default ones.

• In principle, links that are used for navigation should be styled as links (text only or text with icon), not as buttons. But there can be exceptions such as call to action buttons that also link to another page.
• On pages or sites where there aren't many buttons, the button colors might seem random, but as the number of buttons and user interactions increases, then hopefully the color pattern will be more evident and useful from a UI standpoint.
• For consistency this color scheme should be applied to icon buttons as well, like the magnifying-glass "search" icon and the "i" and "?" tooltip icons, in forms and so on, but not in an array like the admin icons where color consistency is more important.

Dev mailing list discussion starts here: https://sourceforge.net/p/tikiwiki/mailman/message/36346433/

Questions

Where is the limit between significant and insignificant changes?

Is it allowed to use btn-primary for confirming a non-destructive change, or to make a destructive change?