Bootstrap 2.0

Sounds good. Drop me a line when ready so we can make up a plan.

I'm really excited to see this project underway, but I saw on another posting that there were licensing conflicts for bundling this framework as a theme for release on Drupal. Is that true?

Thread in reference:
http://drupal.org/node/1276060#comment-5006754

Alright, just read that thread. Great to hear there is a way to work around this. I'll start testing out the theme, and see if there is anywhere I can help out.

Thanks

I'm also interested in knowing if there's any progress. Also, I can dedicate some time to this project if it's needed.

I made a 2.x branch to get work going. Only change i made is hot linking to the new 2.0 files. So its a mess.
Ill contact adregriffin to see if he has anything to get 2.x going. Nevertheless ill start working on it myself the next days.

Anyone can create patches and post them into the issue queue for now.
For everybody who wants to have access to the repo for development, drop me a line directly.

Looking at the Twitter Dev site, it has me wondering if Acquia has possibly already embarked on something like this internally? Or published back to Drupal.org under a different name.

I'm just guessing the Twitter Dev site is using Twitter bootstrap, it may not be...

Example: https://dev.twitter.com/docs/rate-limiting

I've been building it from the Framework theme, and requiring the user to download their own version of the bootstrap and copy into the theme folder. I'm also trying to do as few overrides as possible, just adding the appropriate classes with theme functions in the settings.php and in the tpl files.

Ideally, I'm just trying to make some clean tpl files work seamlessly with a vanilla package of Bootstrap. I'll post my progress soon.

Same here andregriffin. Creating a good starter theme. Though i hotlink the bootstrap files by default. Wich can then be overridden by the user.
Maybe we can "borrrow" code from each other.
You can find the latest code of this theme in the dev version.

Seems to me dev.twitter.com is using a custom theme. Not twitter bootstrap.
Contacted andregriffin to see how he's standing on joining forces.

There a few things to be done right now.

Create helper and theme functions for the twitter bootstrap templates.
Some things cannot be done from the theme. Like creating theme functions for several components. Most important being navigation/dropdowns.
Ive setup a module for that: http://drupal.org/project/twitter_bootstrap_ui
Also nice to be able to use install functions.

If i look at some of the components of bootstrap:

- Navigation
- Forms
- Pager
- Buttons
- Tables
- Labels
....

Then i already get a good idea what is done and what needs to be done.

Create some pre-defined templates.
Where i would like some help with is the bigger picture. The templates itself.
Im going to focus on helper/preprocess/theme functions for now. So if anyone want to create a template based on this let me know.

First thing that needs to be done is to provide a good skeleton/starter template for people to work with. Something like the twitter bootstrap example sites.

There's also the problem of twitter bootstrap requiring a high version of jQuery. 1.7+

@arnoldbird: subtheming can be n levels deep, as I said in #16, Arctica is base theme that provides HTML5 and responsive design, Tundra is subtheme that adds some features like web fonts, background, slider and drop down menus and TouchPro adds color configuration.

Some may agrue that three levels is too much (remember, you also need your theme on top of that) but reality according to my opinion is not like that. This is good example of layering functionality that Drupal enables and that is the case for this theme if you ask me.

We need some solid HTML5 foundation and I see Framework as good candidate (maybe equally good would be Genesis, BigDaddy, Boron, Mothership or Om). This way we would not have to think about things that others have already thought of and solved (or are solving) well. Whole DRY principle is based on that idea of reusing something.

In this case, I think, we should evaluate which one is the best for merging with Bootstrap as some themes may have layout presumption that interfere with Bootstrap (that is why I omitted AdaptiveTheme or Omega and other responsive base themes).

If I may say, I admire every work and respect what Docc is making for Bootstrap and community. Therefore I did ask about some road map and delegation of activities to others as it is easier to work together under coordination.

I would call Docc to "pick" candidates based on their preference to do some part of job as every fine theme needs a lot of time devoted to it and we all have our day job that brings food to table. Some may test, others may respond to issues, some may write docs, some may write installation profiles and sample content and some may develop other subthemes based on our work.

That would be a win situation for all.

I would suggest to pick a base HTML5 theme (I've done research to pick candidates among Framework, Genesis, BigDaddy, Boron, Mothership or Om), to build Bootstrap as subtheme and allow any other subtheming to occur at third level that will bring more regions, options and features structured just like Arctica, Tundra and TouchPro (I have no affiliation with Sooperthemes but I greatly appreciate the structure and implementation).

I'd like Docc to comment on this one and also I'm ready to do my part. I see that including Framework author andregriffin is good opportunity to have at least that base part solved as he can help connect Framework with Bootstrap as its subtheme (not to mention that it would elevate Framework to that level of AdaptiveTheme and Omega ;)

Docc, andregriffin what do you say?

MacMladen , thank you for your post.

First off, Im a real fan of the framework theme. I use it as a base of most of my projects.
Mostly because its so slick and lightweight. Thats also what im looking for in this theme. In my opinion, themes like Omega are too bloated and too focused on the end user. Im not a fan of (sub)theming in such a way.
Im really looking for a way to give tools to themer's to build a template based on bootstrap in a quick and solid way.

Combining bootstrap with HTML 5 is a good idea. But i don't know about introducing a theme dependancy.
Though if there should be a dependency it should be indeed framework.

So we need Andre on this. Im in favour of combining forces in one way or another.

PS while writing this response i see that Andre posted a reaction aswell. Ill respond to his post tomorrow. Thanks Andre.

Now time for the superbowl ;)

have aways loved framework theme - even if i have munged it into something else for my own purposes, so great that you are on this Andre

Hey bkildow. That looks promising indeed. Ill contact the author to see what his plans are.

Not necessarily. There would be a lot of overlap between the projects, as bootstrap is a package of different components. Regions are just the endpoint.

"Stanley" might be that "third layer" project you are talking about.
So why not bundle efforts to create one solid base theme everybody can use for there own projects. Like Stanley.

I yet have to confirm Andre coming aboard but ill probably let him decide if we are going to use framework as a base theme or not.

Meanwhile ill be grinding away slowly on this project but hoping i have more info soon on those people joining the effort.

Framework, being what it is (just a stripped down collection of tpls and a single well organized CSS file) would seem redundant by being the base of a sub-theme. If it were a very complex theme with lots of functions and styles, that would make sense. However, this Bootstrap project will require different markup all around, yet in total, the markup will not be much more complex than Framework itself.

My vote is to just fork the Framework theme, and build Twitter_Bootstrap as needed using the ideology of Framework. I don't see a reason to make what will essentially be base theme (Bootstrap), as a sub-theme from yet another base theme (Framework). It's a level of complexity that I simply don't see as warranted. Having the two themes independent will allow the markup of each to stay optimally suited to their respective workflow, without compromise on either end. Having me being a part of both projects will obviously lend some similarity and consistency between them, but I would rather work with them in parallel, rather than in serial. Sub-themes of Twitter_Bootstrap will obviously be a different story, as the included markup and styling will be much more comprehensive and complex than Framework ever will be.

A far as the administration theme mentioned above goes, It would be nice to have that work in conjunction with this theme. I am undecided on whether it would be best to keep front-end and administration development modular and independent, or if they should come together as a complete overhaul of the Drupal UI and theme development platform.

Just found http://drupal.org/sandbox/rerooting/1429486

Bootstrap on the basis of Omega .. now that would be sweet. You could then just use Omega's responsive grid and patch in bootstrap's grid later on.

@XiaN Vizjereij Not sure how it is implemented, but that is not what we (if I may say) are looking for. Omega is rich theme that is responsive for itself so hooking Bootstrap would mean that one responsiveness should be removed and that is against base idea of both Omega and Bootstrap.

Also Omega is quite rich and have its way more toward end user than being thin (slim) and base for further development.

That is why we are looking into more trimmed HTML5 base than to rich bases like Omega, Adaptive Theme, Arctica or similar.

While main initiator Docc is looking into helper functions, andregriffin is looking into adapting Framework or going from zero based on his experience with Framework. Genesis 7.x-2.x-dev is similar, while Mothership and BigDaddy could be a bit complicated based on fact that they try hard to change core and contributed modules CSS and HTML.

Any progress, andregriffin?

Hi guys, I'm the maintainer of the above mentioned Stanley theme. A bootstrap admin theme. Docc contacted me about my plans for Stanley and to see if there is any future in this theme and Stanley working together. Instead of replying him via mail, I'll just throw my thoughts in the group.

At the time I built Stanley I was of aware of this initiative, but there was little to no progress, and a lot of uncertainty on what path to take, so I just wen ahead and created Stanley. I wasn't interested in doing anything on the frontend, I just wanted a usable admin side as I was getting tired of Rubik's quirks. I decided on still using Tao as a base theme because I knew it well, and because I think it has some interesting ideas.

Stanley right now is ok, it's pretty stable, and it's fine-tuned the most popular modules. The reason it's still in alpha is that I want to have the theme work with the libraries API first, before moving on to beta and later to stable. But we've been using the theme now for some weeks on different projects without major problems.

So that's that. Now that we have Bootstrap 2, and after my experiences creating v1 of Stanley, the story is different.

First I wanted to get rid of Tao, either I make Stanley work standlone, or I use a decent base theme. I look into some of the more popular base themes, but they are way to feature rich. I really don't need al these settings. (On the other hand, some settings might be interesting).

Second, I doubt changing Drupal to work with stanley is the right way to go. It's what I've been doing with Stanley and it's what makes this whole development process frustrating because you just won't get it all. It's not just some template files, it's copying over a whole bunch of theme functions just to add a class or a wrapper div. It's stupid, just copying over large chunks of core, while there is fundamentally nothing wrong with the code. Not only that, it's adding and overriding a bunch of javascript as well. Only to discover that all the work you just did to get those silly messages look like bootstraps message doesn't work on that one (core) form or that small contrib module. ALso, the original message has been overridden by your generic message in your theme. So you end up reverting all these changes and copying over the messages css to make it work for drupal. Et voila, it works everywhere.

My point is, you can't get it all. A lot of modules use custom markup and theme functions to accomplish the required page layout, but they do use general accepted drupal classes which magically color their pages.

And now what you really wanted to know (kudos for sticking with me), my current thoughts on the future of Stanley:

- I'm only interested in the admin side. I'm not going to make it easy on you as an end user to use Stanley for your fron end needs, so don't ask.

- I was/am regularly keeping an eye on this project, but it's been a wait and see attitude. My ideal situation is this theme becomes a stable and flexible base theme, without enforcing any structure or layout (similar to Tao, or cores Stark). Based on the discussion, this seems to be the case, so I will gladly help out and build Stanley 2 on top of this.

- Immediately after I released the first alpha of Stanley I was relieved that I got something decent. But I regretted not forking the Bootstrap library and making my own Drupal Twitter Bootstrap library. Making the css match my needs would have been a lot easier than making Drupal match those of Bootstrap. Specially with LESS (although I'm more of a SASS guy).

So there you have it: get a clean source (Framework), fork Twitter Bootstrap and add the Drupal classes to the css declarations, fine tune the remaining theming functions and templates and you're down. Let other developer build sub theme (or provide one or more of your own, ie a simple ui on top of the base).

Hey guys, I've started working on a bootstrap starterkit theme as I've got a couple of projects I'd like to use it for coming up soon. I've got most of the elements working except for the fixed navbar and a couple of issues with horizontal form layouts.

I've got the code up here if you'd like to take a look https://github.com/mpezzi/bootstrap

If you guys need any help let me know, I'd be glad to help out!

Thanks for all the great work on this theme. I am using it as a base theme for a couple sites, which is the only way I will be able to motivate myself to test and contribute patches. Let me know if there is anything in particular I can help with.

@stopshinal
I've got similar issues as well when running PHP 5.3. It works well in 5.2...