I'm going to work on a Shopify theme, and I want to figure out how to run/edit it locally. I'd like to be able to the following, if possible:
Pull all the Shopify theme code from the site to my local computer (ideally a single command line tool)
Make edits locally, and run them locally or in a staging environment
Push all the edits to the main Shopify site, again using a command line tool
Is this at all possible?
There are quite a few workflows you can use here.
1. Task runners
If you're using either Gulp or Grunt locally for development, there are libraries out there that will upload your files to the store through API credentials of a Private App that you have to create. Most work by uploading the files you change, using a watcher.
grunt-shopify
grunt-shopify-upload
gulp-shopify-upload (it's my favourite since I use Gulp but has a known issue that sometimes it stops uploading files and you have to restart it).
2. Official Shopify Theme Kit
Theme Kit is a cross-platform CLI tool that was built by Shopify Employees. It can run on windows/linux/OS X. You can read more about it on Shopify Blog or download it directly. The alternative previously mentioned of Desktop Theme Editor is deprecated and has been replaced by Theme Kit.
3. Third-party SaaS Applications
Instead of watching for changes, these will work with a continuos integration workflow, where your latest push on a certain branch gets uploaded to the theme you've selected.
Beanstalk. More specific information can be found on their landing page for Shopify, here.
DeployBot. Their help article on Shopify has some information on how to get started.
Both options are from the same company. Here's a comparison of both they've did on their blog.
4. Third-party libraries
There's also an alternative not officially supported by Shopify which is a TextMate Bundle in case you use that OSX editor.
There's an unofficial extended cli similar to theme kit but with further functionality called Quickshot, which I've just found out based on Matt's response and seems pretty awesome. Some of the features they highlight are:
Supports uploading to multiple Shopify stores and themes
Easy to use configuration wizard
Uploads/downloads in parallel greatly reducing transfer times
Supports autocompiling scss locally before uploading to Shopify
Supports autocompiling Babel/ES6 into modules which are easily used by - Requirejs and others
Can use with .gitignore files or a custom .quickshotignore file.
Can download/upload Shopify Blogs, Pages and Products! Easily transfer them between stores! Even the metafields! And edit them locally in your favorite editor.
Shopify recently released Slate, a new tool for theme development.
https://github.com/Shopify/slate
As of 2020, Shopify has stopped support Slate so you can now use Themekit - https://shopify.github.io/themekit/
2022 update
Currently it is not possible to run Shopify locally. There are only solutions, mentioned in other answers to edit files locally and upload it to Shopify. It makes the development hard.
I am working on a solution to emulate Shopify locally making development similar to WordPress, React or Angular. So you will see changes immediately, even without reloading the page and without the need to upload files to Shopify each time.
You can read more here: https://link.medium.com/6SGd1kcVdnb
Juan's answer is spot on.
There's one more I know of which I believe is a little more advanced than Themekit (which I use) called Quickshot: https://quickshot.readme.io/v2.1/docs
Shopify have built a tool for Mac that allows you to develop your theme locally, and sync with your store https://apps.shopify.com/desktop-theme-editor
I don't know of anything for windows/Linux etc.
If you're looking for completely offline development, it's unfortunately not possible at this time. While the Slate/ThemeKit CLIs lets you code in your favorite text editor, an internet connection is still required because it likes to keep everything in sync at all times.
Install the state package by running the following commands:
npm install -g #shopify/slate
slate theme theme-name
I'm testing a desktop app being built in Electron. Since the app’s layout is CSS/HTML based, I was hoping to do simple layout modifications without access to the source material. Even if I can't see my mods in the running app, it would be useful to extract HTML/CSS/JavaScript templates, modify these and see the results in a browser.
Question 1: Is the above possible?
Based on this question I'm assuming app.asar could be what I'm looking for, but being on Windows 10, it seems that installing asar (and Node, NPM, Python and Visual Studio) just to unarchive files is discouraged.
Question 2: Can I access the files presumed to be inside app.asar without installing all the stuff mentioned above?
This has happened a few times already and it's pretty frustrating.
I make some changes to one of my Javascript files. Then I save the changes and proceed to test the build in IE.
All my changes are not reflected in the dynamic version of the file.
So far, I have fixed the problem by changing the file name and reincluding it in my bundle.
(The MS forums only tell me that I might be editing a wrong version of the file, which is not the case. See above.)
I am new to Windows so I figure there might be something I'm doing wrong...
Take a look at this solution: Force reload of JS and CSS files with ASP.NET MVC 3.
I'm searching for a good PDF viewer for Joomla, the problem is when there is a module in an article all the PDF viewers I tried so far show: {loadposition myposition} in place of that module.
Does anybody know a PDF viewer that will show the module.
I would also like it to have a header and footer option.
Thx.
I suspect that your extensions 'might' not be the sole source of your troubles.
Have you installed "Modules Anywhere" from nonumber.nl?
I recommend you try that first before assuming that the problem lies in your extensions.
Here is the appropriate link: http://www.nonumber.nl/extensions/modulesanywhere
Install it, and make sure the editor plugin is also installed and enabled (Modules Anywhere may perform these steps upon installation), then open up the content item you wish to inject your module into and use the module selection tool provided to you by the editor plugin.
After you perform this test, you can more reliably assume that your PDF related modules are the culprits.
Good luck!
If yes, is there a way to compile (NOT obfuscate) JS code for deployment in ChromeOS?
From quickly looking at the codebase using the Chromium.org Git browser, it appears that Google haven't gone out of their way to remove the "View page source" menu item from the version of Chrom(e|ium) shipped in Chrom(e|ium) OS.
Of course, there's nothing to prevent them from hiding the option in the UI, or removing the feature all together by #ifdef-ing it out, though.