solo_wizard
solo_wizard copied to clipboard
Use twitter bootstrap
Haven't used it yet and seemed like it might be nice look for the site. Was planning to use this repo: https://github.com/seyhunak/twitter-bootstrap-rails
Any objections? I'll make sure I do all my exploring with frequent pushes and a PR right out of the gate :)
No objections to switching the site to bootstrap.
The css was done by wife as a sample project to try out being a developer - so it was all hand built instead of leveraging twitter/compass/etc.
haha that's awesome! I almost don't want to convert now...! Tell your wife she's cool as hell. Or wait. Confirm to your wife that she's cool as hell, as I assume she must already know
I'll get cracking on this when I get some time
Haha. The css and the faq section on solowizard are a bit unwieldy, so don't feel bad about ripping it out and starting fresh with bootstrap. we definitely want something which is workable and can be changed easily - bootstrap is a great option.
As far as theme goes, I do like how solowizard has a plain-programmer look, which I had her base on homebrew's look: http://mxcl.github.com/homebrew/ Your thoughts?
Coolio. Thanks!
In regards to the look, my interest in your awesome project is that I'm sorta hoping to help it become a "competitor" to GitHub's "The Setup": https://speakerdeck.com/wfarr/the-setup-managing-an-army-of-laptops-with-puppet?slide=37
I'm really interested in helping Chef becoming the foundation of a non-developer tool. And I really like the approach of GitHub and Apple in giving their internal tools as much polish as any external offering. Homebrew site looks great, but also really like that look of GitHub apps, and its a little bit of a distinct feel.
And to give context, I'm working at a company called Myplanet Digital, and every second Friday, we get a free day to work on whatever we want and collaborate with other Myplaneteers on stuff. I was hoping to lure in a designer and UX person at some point and try to figure out how to make it as user-friendly and slick as possible :) We'd probably do some testing with new hires, and stuff like that.
How about I never go down any path (design or otherwise) without posting samples or thoughts early on. And worst case scenario, we just fork for internal use and brand it how we'd like (but we're still working on the same base tool :)
"The setup"/github/apple sounds like a great direction! Go for it, loop me in as makes sense, but don't feel restricted or anything. No need for internal branding/etc.
With my "homebrew" look, I guess it was less of "look like homebrew" and more of "don't look like boilerplate twitter bootstrap" because engineers get tired of that look quickly, haha.
Tom
On Fri, Nov 2, 2012 at 8:10 AM, Patrick Connolly [email protected]:
Coolio. Thanks!
In regards to the look, my interest in your awesome project is that I'm sorta hoping to help it become a "competitor" to GitHub's "The Setup":
https://speakerdeck.com/wfarr/the-setup-managing-an-army-of-laptops-with-puppet?slide=37
I'm really interested in helping Chef becoming the foundation of a non-developer tool. And I really like the approach of GitHub and Apple in giving their internal tools as much polish as any external offering. Homebrew site looks great, but also really like that look of GitHub apps, and its a little bit of a distinct feel.
And to give context, I'm working at a company called Myplanet Digital, and every second Friday, we get a free day to work on whatever we want and collaborate with other Myplaneteers on stuff. I was hoping to lure in a designer and UX person at some point and try to figure out how to make it as user-friendly and slick as possible :) We'd probably do some testing with new hires, and stuff like that.
How about I never go down any path (design or otherwise) without posting samples or thoughts early on. And worst case scenario, we just fork for internal use and brand it how we'd like (but we're still working on the same base tool :)
— Reply to this email directly or view it on GitHubhttps://github.com/tommyh/solo_wizard/issues/1#issuecomment-10017319.