I'm not sure what the stance is at this time. Theoretically, all of the
templates could be updated to use the new markup. Or, they could all be
dropped as well. I thought I saw somewhere that Angie was working on a
version of Beez to be compatible with Bootstrap, but I could be wrong there
too.
From: Viet Vu <viet...@gmail.com>
Reply-To: <joomla-dev-cms@googlegroups.com>
Date: Wednesday, July 18, 2012 5:11 AM
To: <joomla-dev-cms@googlegroups.com>
Subject: [jcms] Support for Bluestork, Hathor, Beez in J 3
Hi,
How will Bluestork, Hathor, Beez are supported in upcoming version 3.0? Not
sure how will they work when Strapped is integrated?
Just want to know about this as I could not find any related information
else where.
Thanks
-- You received this message because you are subscribed to the Google Groups
"Joomla! CMS Development" group.
To view this discussion on the web, visit
https://groups.google.com/d/msg/joomla-dev-cms/-/sWi_nNp0c6YJ.
To post to this group, send an email to joomla-dev-cms@googlegroups.com.
To unsubscribe from this group, send email to
joomla-dev-cms+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
On Wednesday, July 18, 2012 4:33:58 PM UTC-4, Michael Babker wrote:
> I'm not sure what the stance is at this time. Theoretically, all of the > templates could be updated to use the new markup. Or, they could all be > dropped as well. I thought I saw somewhere that Angie was working on a > version of Beez to be compatible with Bootstrap, but I could be wrong there > too.
> From: Viet Vu <viet...@gmail.com> > Reply-To: <joomla-dev-cms@googlegroups.com> > Date: Wednesday, July 18, 2012 5:11 AM > To: <joomla-dev-cms@googlegroups.com> > Subject: [jcms] Support for Bluestork, Hathor, Beez in J 3
> Hi,
> How will Bluestork, Hathor, Beez are supported in upcoming version 3.0? > Not sure how will they work when Strapped is integrated?
> Just want to know about this as I could not find any related information > else where.
> Thanks
> -- > You received this message because you are subscribed to the Google Groups > "Joomla! CMS Development" group. > To view this discussion on the web, visit > https://groups.google.com/d/msg/joomla-dev-cms/-/sWi_nNp0c6YJ. > To post to this group, send an email to joomla-dev-cms@googlegroups.com. > To unsubscribe from this group, send email to > joomla-dev-cms+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
I think most of you know that I'm not the best friend of bootstrap.
So maybe some of you remember the discussion we had in the UX Forum.
My opion didn't change much, but I see that bootstrap has some nice looking styles and it looks easy for people who are not so familar with all the CSS stuff.
So what I did the last days:
1. First I took alook at that static page: http://www.kyleledbetter.com/j3ux/site/ It is looking nice but I think the code can be optimized a lot.
I took a look at the source code and saw a lot of nested divs. I think this isn't optimal.
On the other hand the document hasn't got a correct semantic structure and don't linearize correct.
2. This morning I spent few hours to bootstrap the Beez5-Template
Result beez.der-auftritt.de
Here I noticed two big issue :
a) I add the span-classes bootstrap needs into the template-overrides of the frontapge-view, so that we can customize the columncount over the menuitems.
Bootstrap is working with px for the width. If the screensize changed media-queries are changing the width.
So good so far.
In the normal Beez-Template we are working with % for the width. The big advantage of this is that we have good more flexibility with the column-positioning around the main-content (left, right no-column), because the width is related to its parentelement. Maybe somebody has an idea for that.
b) There are no styles for a deep nested navigation, they should be added in the custom theme.css and that can be much code.
We should take care of the file-size.