2

Closed

Orchard default css class names (and concepts) should be aligned to Bootstrap

description

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
#layout-navigation 
#layout-featured 
#layout-before-main
#layout-after-main
#layout-main-container ???
#layout-main
.group ???
#layout-main
#aside-first
#layout-content
#messages
#before-content
#content
#after-content
#aside-second
#layout-tripel
#tripel-first
#tripel-second
#tripel-third
#layout-footer
#footer-quad
#footer-quad-first
#footer-quad-second
#footer-quad-third       
#footer-quad-forth
#footer-sig
.zone-messages,
.zone-before-content,
.zone-content,
.zone-after-content
.zone-aside-first ,
.zone-aside-second
.zone-tripel-first,
.zone-tripel-second,
.zone-tripel-third
.zone-footer-quad-first,
.zone-footer-quad-second,
.zone-footer-quad-third,
.zone-footer-quad-fourth
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 ?
Closed Feb 10, 2013 at 7:56 PM by BertrandLeRoy
Right, but I also disagree that it needs to be aligned to Bootstrap. There is another bug tracking a new default theme. This one is way too prescriptive. Let's keep our options open.

comments

BertrandLeRoy wrote Feb 10, 2013 at 5:34 AM

There are plenty of Bootstrap themes already.

** Closed by BertrandLeRoy 02/09/2013 10:34PM

CSADNT wrote Feb 10, 2013 at 8:17 AM

This was not the idea behind this post, for sure there are plenty of bootstrap version in Orchard.
The idea was that the css class used in Orchard base styling need a re-thinking.

CSADNT wrote Feb 10, 2013 at 8:18 AM

This was not the idea behind this post, for sure there are plenty of bootstrap version in Orchard.
The idea was that the css class used in Orchard base styling need a re-thinking.

CSADNT wrote Feb 11, 2013 at 6:52 AM

Yes but if you close this enlistment, nobody will see it and the discussion will be limited.
If there are so many boostrap themes in Orchard, I am sure their authors will agree with the actual difficulty to transform all that is generated by the internal views to the bootstrap bas concepts.
Why don't make a kind of voting ?
Having this open could show the interest.

BertrandLeRoy wrote Feb 11, 2013 at 8:15 AM

As I said, there are open bugs about a new default theme, as well as a forum discussion. Bugs are not the right place to have a discussion anyway, they are meant to track issues.