Show HN: Themes for Bootstrap
wrapbootstrap.com
wrapbootstrap.com
- I can't find off the shelf themes that meet my needs.
- I want to learn how to do it myself.
- I want a solid foundation to start with.
A codecademy for CSS "cooking" with bootstrap would be great. A quick mover with good design skills could probably make a decent amount of money in a short period if they sold tutorials with focused content. [I'm just throwing this out there in case someone wants to bite.]see my gh-pages sites:
FYI - Your carousel isn't centered, the follow shareme button is clipped, and the Android, Hello article has an extra </div> in the <section id="getsdk">, causing the remainder of the page to be left aligned. I like sausage, mushroom, and olive on my pizza. Did you want my address? <jk ;)>
I wasn't planning on using bootstrap though because I think bootstrap offers too many possibilities to developers who don't understand design. I think keeping things simple and limited is the best approach.
Do you think not using bootstrap would be an issue?
I'd suggest using it specifically for this reason - that is, unless there is another framework that does an equally good job of getting out of one's way as Bootstrap. That said, it definitely makes sense to try to limit its use to a small subset for your tutorials.
Anyway, I'm halway through making my series so I'm gonna launch that and if it's received well I'll probably do a bootstrap customisation series too.
Slightly controversial question, but how much would you be willing to pay for a series like this? I think I paid €80 for Michael Hartl's rails tutorial series and I was satisfied with that price.
That said, there is a lot of buzz around bootstrap v2 now, so you might consider doing it the other way around - pick a few bootstrap customizations as a teaser class to help built market momentum for the full classes.
Interesting idea, I may end up doing that.
Anyway, I'll probably giveaway a bunch of free subscriptions to help get it off the ground. I don't have time right now to build a launch page and get hosting, so if anyone's interested, shoot me your name and email address at colmtuite@gmail.com and I might get in touch when I launch.
Thanks for the feedback guys.
I am interested in your video series and may buy them, but right now:
- I have no way of finding out when you're done, except for polling you, which ups the burden on me
- I am likely to forget about you
- I am likely to miss your announcement that you're opening up shop
A simple "leave your email here if you want to be kept up to date" form would be awesome !
CSS is not hard. I don't consider myself good at css, not at all, but give me a mockup and I can reproduce it, with a lot of Googling and trail-and-error. At least for me, though, what is really difficult is to make something from scratch without a mockup. It might be because I am not much of a visual thinker. I am a coder after all, not a designer. A professional designer might already have this mockup in her head. I don't.
So what I need to do is create the mockup in Photoshop first. There I can experiment, move stuff around, change colors, shadows, etc. When I am done, I reproduce it in css. I guess when you are either a very strong visual thinker or you are already very good at css, you don't need Photoshop. Otherwise I recommend you start with a mockup and then make a pixel-by-pixel reproduction of it. That way you can solely focus on the How, not the What. If you do that it's not hard at all, and you don't need a code academy for it. [That said I like the idea of a code academy for building a website from scratch for non-coders]
And you even admit it yourself without realising it!
Trial-and-error is no way to code something. Programming novices use trial-and-error. But saying CSS is easy when you're still trial-and-erroring stuff just shows how incredibly hard it is. It's admitting you don't know what you're doing. And that's CSS all over. Few people can use CSS to do exactly what they want and know what they're doing.
Everyone else just finds something that kind of works and do the same thing over and over.
It's only recently been the case that you can view the source of websites posted here on HN that aren't a mass of nested divs just to get the layout right.
If you can code, then you should really be able to write CSS... and if you can't code, I don't think any of these products are really targeted at you anyway.
Edit: tpyo
Will exclusive and multi-site license options follow?
Also, on your /sell page there's a heading that says sellers earn between 55 and 75% but in the text of that block it says the non-exclusive share is 35%.
Anyway, as I said below this is awesome and I wish you the best of luck.
As for the earnings text on the sell page, I'm working on cleaning up the wording there so that it better conveys what I mean.
And thank you!
Edit: Updated the earnings text
On stealing the css: your market are people who know the effort it takes to build something and are probably likely to pay $15-$50 for a big time saver.
Edit: Sorry to be annoying but the sign-in link has a padlock icon next to it which usually indicates a secure connection/SSL neither of which you are using.
Great concept btw.
Regarding the padlock icon: That was an item on my todo list that I moved to "not critical for launch." And then someone mentioned it. :)
How are you going to prevent people from stealing the themes instead of buying them? One can grab the full HTML and CSS from the preview views.
Great idea btw.
It sounded like a good idea so I decided to execute on it. :)
This is an awesome idea by the way. I love the choice on Theme Forest but I the flexibility of Bootstrap is brilliant too. I'm also using Bootstrap whenever I prototype anything and being able to just buy and use a theme later on would be incredibly useful (obviously it's not quite that simple, but it could be close). I will almost certainly be buying lots of themes from you assuming you get designs (which I'm sure you will!).
I'm surprised ThemeForest don't have a Bootstrap section yet actually...
I'm surprised that ThemeForest hasn't jumped on this yet either.
From a dev's POV - I won't believe you on the elegance & quality of the source unless I can see it, and that's very much what I'd be interested in paying for (an elegant/clean/flexible UI base). Obfuscating at all is somewhat like selling a fabulous custom car but hauling a dirty tarp over it before letting the prospective buyer get a closer look.
Besides, it's HTML & CSS. De-obfuscating (unless it's seriously mangled, which seems dangerous) is as easy as copying the DOM and composed CSS from Firebug, I imagine, or cut/pasting the files into a good editor and auto-formatting.
Or something; I can't say I've ever de-obfuscated a webpage before; when I check the source, if it's crap I don't keep reading. Which may be part of the point, here.
Seems like something that just punishes people who'd buy it in the first place like most anti-piracy schemes.
Good luck!
One way you could increase incentive to buy instead of steal is only show CSS on the preview, but download the LESS file on purchase (if the author used LESS). I'd certainly be more interested in a LESS file.
In the end, I wouldn't worry about it too much, like someone said, people who are gonna pay are gonna pay.
OT: Are you using some sort of "food ipsum" generator for the StackLayer theme? I love it.
Yes, the additional assets are the big gotchas (especially with themes that have text embedded in images) and I like the idea about including the LESS source. I'll get on adding that to the StackLayer theme!
By the way: Veggie Ipsum. It's awesome. http://veggieipsum.com/
Thanks!
Thanks.
This morning, I'm working on adding a grid framework to another theme I bought off of themeforest. That's the one thing I hate about themeforest is you can't see the "bones" of the theme before you buy. I've bought 4 or 5 themes off of theme forest with about 3/4 of them being of decent quality. With decent quality being the ease at which I can modify them for my own needs.
Shameless plug: I'm trying to get a new community project going, so please consider sharing this on there - http://swym.me/
I explained some more here - http://news.ycombinator.com/item?id=3579260
Basically, you know how people often ask on HN how did you make that? What stack did you use? It's the same thing, but the tags give you a fun way to find out about other projects built on the same technology. Plus, you might find other creative people you may not have found otherwise.
Perhaps have a free section? It would be a good way to get free traffic which you can use to upsell to paid versions.
Good thinking.
Perhaps send an e-mail to a couple of handpicked theme creators from one of the other sites to come over - maybe even convert some of the themes for free.
I have emailed a few handpicked designers already so I will see what the response is. :)
Best of luck with it.
Themes will be useful in solving that problem. Way to go.
However - wasn't the whole point of bootstrap to make it easier for developers to create their own stuff, thus avoiding the need to buy a template? If you want a templated site, just buy one from ThemeForest, because that's exactly what you're getting here except it's built around 'standardized' markup instead of the designer's own.
>>that's exactly what you're getting here except it's built around 'standardized' markup instead of the designer's own
That's kind of the point. :)
Good luck with it though.
Thanks!
Good luck!
Thanks and stay tuned :)
Bootstrap is open source. Most of these themes would be paid. (not good for me)
Don't have much in support of my point, but I would not use this service unless some really _amazing_ designs are put up.
Interestingly, you say it's "not good for you", but then you say you'd use the service if some "amazing" designs were available. I presume "amazing" designs would be good for you, hence you'll use it.
Not even sure what the point of your comment was, except to say "I don't pay for stuff" (with a hint of "everything should be open source" seeming to lurk underneath).
I'm working on a web application platform (coffeescript running concurrently across a cluster of nodes, basically). I'm still working on the backend, but once it is released publicly, I want to start building out a built-in frontend. To that goal, I'm planning to ship a web framework built in, and Bootstrap is the leading candidate right now.
I know popularly you buy themes which are collections of HTML and CSS and that they make it easy to have a nice layout without having to swipe a 37signals page-- you just change the content to suit what you want.
I see bootstrap coming from one end- a cohesive framework to make developing pages easier-- and themes being going a step further-- specific designs for everything but the content.
And I wonder if it wouldn't be a good idea to have a sort of theme architecture for bootstrap.
What I'm imagining is that themes could be specified, and developed in such a way that they could be traded as tar balls and quickly and easily used by projects. Much the way wordpress themes are standardized and plug into wordpress, these themes could be standardized and plug into bootstrap. Hell, the bootstrap page has an almost theme creator that lets you customize bootstrap. (http://twitter.github.com/bootstrap/download.html)
I'd love to have the ability to point my web platform at a github page, and have it suck in the latest version of an open source theme for people.
I'd love it if themes became a popular open source item. You may think this is a bad idea, but I see it as taking the framework idea and building another level on top of it. Sure, some people will just use stock themes, others will make custom themes.
... and a lot of people will learn web design by taking apart themes and understanding them.
Does a standard format for bootstrap themes make sense?
(Please don't flame me if I've missed something here- this is an idea, and I admit to not being a bootstrap expert.)
I'm thinking a theme would be a collection of one level higher things like buttons, menus, a picture showing widget, or whatever.
And each component would have no other dependancies other than bootstrap, hopefully.