Actually it seems a show stopper for Orchard expansion to have its own css class names.
As Css does not allow creating class alias and tools as .less are another layer of complication, why continue making complicated, let's align all orchard standard css class names ... and concepts on bootstrap.
I have been trying to create a Orchard2Bootstrap css but it is a mess.
Why layout, the default cshtml in TheTheme Machine, and all the class used in Core and Framework view classes wouldn't be aligned to some real standard.
Last point, the actual schema is somehow puzzling in its logical, missing some high level view as we could find in bootstrap, may be due to evolution.
I know there is a lot of work behind it, but it is now rather blocking and old....
When you see all the ids and main classes, they seem more here to provide a Mac Giver solution than adapted to an open and high level concept
Let's adopt container, row, row-fluid, spanx, etc. as our standard css class names.
..... why repeating so often classes which represent the same concept???
It could be a positive step to adopt the bootstrap standards, gaining a full online documentation and lot of implementations and support made by another solid community, isn't it ?