- Basically when the code is ready, you merge it in to master (development is done on the “development/feature-branch” )
- When the code is merged, you push it to central repository github/bitbucket
-Then you need to setup continuous deployment (google that, and “git web hooks”)
- What happens is that your continuous deployment service detects that the code has been pushed to the master, pulls the code from the repository and replaces to old code.
- If you have unit tests for the code it runs the tests , and deploys only if all tests pass.
And that’s it
Someone mentioned Site Origin Page Builder.
I’ve just checked out that thing, and it is awesome.
And if I understand correctly it is free for commercial use , provided that you don’t bundle it with the theme. You can use TGM to tell the user to download it automatically from the WordPress plugin repository.
And the performance of “multipurpose ultra responsive” themes. Some of those themes are loading megabytes of data. And they are unusable on smartphones and tablets, sure they are “responsive” in the browser, but on mobile device they can’t even be loaded. And “retina ready” themes that are loading 1000px+ width images in to 150×150px thumbs, on regular pixel density systems/ screens.
@roxigo – That is very interesting framework I see that it’s new ( first commit is less than a day old) , but we can assume it’s ready for production? ThemeFuse uses it?
Safari for windows has been discontinued. And market share is non existent. calc() works in IE9 except when you try to position background images with it. Official Twenty Fourteen theme is using calc().
I believe that they are using iframes so the page is never “really” reloaded.
They do it after the theme is put up for sale, so the reviewers never see that.