THEME: div#content (bphome) VS. div#main (bp-member)
-
I am customising a test BP site here:
As I progress, I am noticing some CSS architecture quirks that I thought I’d ask about before doing the work of writing a patch. Namely, in bp-home, the primary content div is called #content and in bp-member, it is called #main. And, because of the way it is applied, the results are inconsitent, even if you get your CSS values to match closely; as evidenced here:
VS.
http://beta.darkwilds.com/members
The red area in members is from … html {background: red;} … in custom.css in bp-home. However, it does not render the same way on the home page at all due to the difference between #content and #main (i think).
So, my main question is … was this by design? If so, could Andy explain the logic (or point me to the appropriate FAQ/video to do so. If it is a bug, then I’d like to take a crack at cleaning it up and submitting a patch.
Once cleaned up, I could see a lot of value in pulling all of the color values & branding (logo) out of base.css and into branding.css so folks could quickly rebrand their site with our impacting the structural integrity of the CSS design. This could be native to the theme(s) or, it could work like custom and be there as a branding-sample.css to be activated by renaming to branding.css.
If folks think this is a valuable addition to the project, I’ll be glad to raise my hand to make it happen.
Thanks,
Doug
- The topic ‘THEME: div#content (bphome) VS. div#main (bp-member)’ is closed to new replies.