3 ms·
I'm not a Ruby developer, so I can't comment if this makes it easier for someone who lives in both Rails and Wordpress, but as someone who has to occasionally m
by ceol 15y ago
I'm not a Ruby developer, so I can't comment if this makes it easier for someone who lives in both Rails and Wordpress, but as someone who has to occasionally make a custom Wordpress theme and has no experience in Rails, this looks like a lot of complexity just to put together a theme. However, I could see this being very nice for someone whose time consists mostly of Wordpress themes, and you obviously put a lot of work into it, so I don't want to write it off. It's cool you were able to make such a feature-rich Wordpress plugin.
Just to make sure: the production/live machine doesn't need the Wordless plugin, correct? Basically you use the Wordless plugin on the dev machine then just distribute the created theme directory like normal? Or am I off-base?
- steffoz 15y agoceol, 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.
- ceol 15y agoGotcha. 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.
- steffoz 15y agoWell, there's not a "conversion" tool in the near roadmap. But you can somewhat easily drop this plugin inside a theme, require it and bundle everything together.