Sam,
My cheat notes to myself are that if you paste this formula into a formula rich text field, you get all the known easy colours. (ie before I knew that we could actually specify a colour
List(" ",
"<a class='Vibrant'>Vibrant</a>", // regular grey button
"<a class='Vibrant Alert'>Vibrant Alert</a>", // yellowish
"<a class='Vibrant Danger'>Vibrant Danger</a>", // red
"<a class='Vibrant Primary'>Vibrant Primary</a>", // blue
"<a class='Vibrant Snowy'>Vibrant Snowy</a>", // white
"<a class='Vibrant Success'>Vibrant Success</a>" // green
)
So I just made the field again in a test app, and all the buttons continue to work except that the Vibrant Success turned Blue like the Vibrant Primary.
I read your post above a couple of times, but I'm still not understanding why you felt OK to retain all those other colours (which I appreciate), but not the Green. Given that it arguably takes coding to specifically choose a button colour (ie a basic day to day admin should not know that formula, only coders or keeners who use this forum), why would that be changed?
Was it that the designers felt that purple and green do not mix well? But now we are sort off off the purple for any custom headers, so does that argument still hold on Day 2 of the New UI?
