Comments for Jay George

Comment on #4 Setting up MAMP + Dropbox by Tej

Tej — Wed, 25 Jan 2012 00:39:00 +0000

Brilliant works a treat, thanks for the tip!

Comment on #2 Using The HTML5 Build Script With A WordPress Theme – Part 2 Of 2 by Adam Kochanowicz

Adam Kochanowicz — Tue, 24 Jan 2012 01:44:00 +0000

I’m surprised I’m the only one to point this out.

I get a “Build success” when I follow these instructions, but every single file it tries to minify/compress gives the error

“java.io.FileNotFoundException: /Users/adamkochanowicz/Documents/veganfm/wp-content/themes/twentyeleven/publish/publish/[filenamehere]”

What could be causing this? Why is it looking in “publish/publish”?

this comes after “[echo] Minifying any unconcatenated css files…”

Comment on #1 Using the HTML5 Build Script with a WordPress Theme – Part 1 of 2 by Chris

Chris — Thu, 12 Jan 2012 17:24:00 +0000

Quick root to your local user are is:

cd ~/location/of/boilerplate/build

Comment on #2 Using The HTML5 Build Script With A WordPress Theme – Part 2 Of 2 by Using the H5BP build script with WordPress « Theo Pak

Using the H5BP build script with WordPress « Theo Pak — Tue, 13 Dec 2011 01:45:31 +0000

[...] Solution The best solution so far seems to be editing the build.xml file, as suggested by Jay George. This way, all your markup will reference the relative path within your theme, and then when the [...]

Comment on #3 Publishing Your Build Script’d WordPress Theme by Anonymous

Anonymous — Mon, 14 Nov 2011 18:57:00 +0000

While rsync, git or svn is ideal for pushing versioned changes to a server (and git and svn are also keen for collaborative code editing as well), sometimes the server technology is a giant question mark when designing a website on WordPress or any other app framework.

Some times I will have a client with an existing hosting solution who needs a WordPress theme implemented and designed, while others don’t have any hosting solution or a propietary one like Business Catalyst.

In either case, unless it’s an SVN or a good shared web host, I will usually not have command line/shell access on the final production server. Since we don’t have shell access I can’t fully rely on GIT or SVN or even rsync. FTP is archaic but it is universally supported. I can’t justify a client spending on a VPS if they will have limited resource usage just so I can use SVN or GIT to control my changes.

Comment on #2 Using The HTML5 Build Script With A WordPress Theme – Part 2 Of 2 by Stephen Fairbanks

Stephen Fairbanks — Fri, 11 Nov 2011 18:07:00 +0000

Doesn’t the stylesheet need to be in the main root directory if WordPress is to use it?

Comment on #1 Using the HTML5 Build Script with a WordPress Theme – Part 1 of 2 by Richard Westenra

Richard Westenra — Wed, 02 Nov 2011 17:46:00 +0000

Thanks for the quality content. However, some written instructions/notes would be much preferred over the videos, so I can skip through to the relevant bits. Thanks!

Comment on #2 Using The HTML5 Build Script With A WordPress Theme – Part 2 Of 2 by Javier

Javier — Fri, 28 Oct 2011 14:59:00 +0000

As Stephen said the new build script replaces the style.css name with a hash so it’s no longer named style.css, this can easily be changed in the build.xml file but what I’m more interested to know is how to keep the top comment block in the style.css since it’s necessary so WP detects the theme.

Comment on #3 Publishing Your Build Script’d WordPress Theme by Jay

Jay — Mon, 24 Oct 2011 08:43:51 +0000

Hey Thanos,

I haven’t used the Build Script for months now (I just use W3 Total Cache instead), but I think you are right yes, you should always ftp the header and footer because of the references.

Comment on #3 Publishing Your Build Script’d WordPress Theme by thanos samarinas

thanos samarinas — Fri, 21 Oct 2011 10:15:00 +0000

Hi Jay, thanx for the post. Maybe I am wrong but:

Wouldn’t you always want to ftp your header.php and footer.php in order to update the references of the new css and js files after you run the build script?

Thanx,
Thanos