Yeah I really see what you mean about the nesting issues. It would get really complex.
We should probably start a whole thread about his concept. I have no doubt others would find it interesting and useful too. Please feel free to start it (as I think the discussion so far belongs to you) :)
Edit; I wasn't contributing to this thread (sorry):
This is a nice Node setup: http://www.otreva.com/shopify-desktop-theme-editor-windows-linux/
It is possible to have multiple developers working on a theme if required also, if you have a local environment in source control you can configure instances using the theme ID from unpublished themes and preview them independently (very nice!).
I'll certainly pick up the shopify-shortcodes, Thanks Ryan, this was my biggest issue, a shop stopper for us, really didn't want to revert to WooCommerce.
My main issues beyond that are:
- that the development environment does not work locally. I can understand the reasons for no local copy as this is a proprietary e-commerce system and you don't want to give away the shopify. A no-commerce version that can be run locally would be very useful, at least for those familiar with Ruby, Rails and Git. It could use an API to talk to the real or sandbox shop to test the commerce side.
- The Desktop Theme tool (Shopify Theme app) doesn't seem to upload changed files (OS X 10.9.5) and insists on bizarre names for my themes. The online tool works better, especially with the version history. Is the command line tool still available?
- no idea how I integrate SCSS compile with this, do I need to do it with `sass --watch ...` or is there some Rails magic going on behind the scenes.
Hi Peter. This probably isn't the best place to ask for help on things. It's a thread about useful resources for those building themes.
I think you would probably be best using the command line tool. But be aware that you are going to need to use the themes 'real' names for that (in the form of the unique identifying code given to each theme). These may also seem like "bizarre names" to you, but are in fact quite logical.
I'm sure you will be able to find the answers to your questions in these forums. There is a lot of good information for those getting started.
A local dummy shop 'app' would be great. I've often thought about how useful that would be. But the need isn't huge.
Thanks for the quick reply.
Actually I'm not looking for help, I've resolved all those issues already using these forums, Stack Overflow and blogs by people like you and Ryan. I'm currently playing around with the Minimal theme, but will probably try either your Foundation based theme or Timber for my next attempt.
The lack of built in shortcodes and custom fields is annoying, but is easily answered (at least for those with Rails and Symfony-Twig experience) by the ease of creating templates. Shopify templates are a breeze compared to WordPress or Joomla.
I understand why Shopify uses the "bizarre" names internally, but the desktop tools should let me call the theme whatever I want locally. I've solved this by just wrapping that directory in one with a mnemonic name.
On further searching I see plenty of people complaining about lack of sync on OS X Mavericks. Is this being addressed, or is there a fundamental problem with this OS?
Also the lack of any local test environment is a frequent question. Most professional developers feel very uncomfortable modifying a live system. As our client's shop is far from ready to launch this isn't a problem, I can just use the online theme editor which is far superior to the WordPress theme editor. I will take a look at the command line tools.
On restarting with the Timber theme, the issues with syncing using the Shopify Theme desktop tool have resolved themselves. And that looks like a great starter theme as well. It shares a lot with my favourite Joomla template, the JoomlaFuture OneWeb template which also uses SASS and the CSSWizardry grid.
Awesome! Yeah definitely give Ryan's shortcodes a go. That in combination with Timber (or Foundation, whichever you prefer, or even a mix of both, like I use) and Metafields and you can do some pretty awesome stuff.
Quick pro-tip... set up a development store or 2 for editing your themes. That way you aren't modifying live themes on live stores. OR... better still... copy the live theme in the live store and preview that while editing that theme (don't publish it until you are ready).