31–40 of 87 posts
Although I've built WP themes and have "dabbled" in Rails (building a blog like everyone else) and consider myself more of a front-end guy, this seems like overkill to me. Not to mention most designers I know would look at this and roll their eyes.
This is awesome! I've often lamented how messy Wordpress is compared to Rails. Yet, there's nothing as mature and easy for anyone to use as Wordpress in Rails.
Rails is a framework, while frameworks do cool things, developers in any language are not always out to build a piece of software that's like a swiss army knife like Wordpress. The rails communitys' exuberance to simplify and automate everything in sight hasn't quite reached wordpress yet. In the mean time there's gems, I guess.
Earlier quoted context omitted.
ceol, that's almost correct. you need to keep the plugin also on your production server, but the compiled assets gets "baked", so wordpress just serves static files.
Gotcha. Thanks for your reply. Do you have any plans to include some sort of "conversion" functionality that turns Wordless themes into standalone themes that dont' require the Wordless plugin? I could see a lot of people who make and sell Wordpress themes using this like crazy, but the dependency might turn away most of them.
Shouldn't that be "stop writing WordPress themes like it's 2003"?
https://github.com/kriswallsmith/assetic
I've never understood why people were willing to jump through so many hoops building themes in WP's messy way.
As a comparison, here's a complete theme (based on the Twitter Bootstrap toolkit) for my current PHP-based project (self-promo, but illustrates the difference well IMO):
https://github.com/jbroadway/bootstrapped
One HTML file, Bootstrap + one short CSS file, zero mixing of PHP code. Most WP alternatives offer similar theming, either Mustache-based like the above is based on, or Twig, both of which are much much cleaner options IMO.
If you're going to use all the new hip tools (and take the time to learn how to use them), just go one step farther and stop using Wordpress.
Wordpress is far and away superior to any blogging platform available on Ruby. It makes wonderful sense to write Wordpress templates in a somewhat more productive environment than raw PHP, then compile them down into something which requires no dependencies on the actual server. This gets you all of the many, many benefits of Wordpress (great plugin support! huge community! deploys at any commodity web host! SQL vuln…
I've got a feeling most people writing Wordpress themes wont meet the requirement of having Ruby installed.
#capitalPdangit
> Ability to write Coffeescript instead of the boring, oldish Javascript; stopped reading right there.
Some may like that, but I want to write my PHP in PHP, and write my CSS in CSS, and write my JS in JS. I really never got why I would write one language in another language just to then use some tool to translate it (and if it gets a little complicated have to manually fix translation problems afterwards). Can someone explain please?