Authors using git: what do you store in your theme's repo?

I’ve been using git to track my projects for a while, but just the code usually. I’m curious if other authors are tracking more in their repos. Possibilities:

• Code (HTML, CSS , JS, etc)
• Production assets (icons, logos, fonts, etc)
• Source assets (PSD, Fireworks PNG , AI)
• Media files (photographs, video)
• Documentation / Read Me
• Other stuff

What does your folder structure look like?

I’m curious how you keep your products organized and versioned during development. Share your workflow below. The more detail the better.

We use svn for everything, but with two repositories instead of one. One for the framework, and one for the actual theme files. This means we can update both of them independently

I must admit that our developer has all the know-how. I’m just learning how to use it

For templates, we use a single git repo which stores all files, assets, psds and docs. A git hook automatically updates preview whenever a new commit is pushed and a build script creates the upload zip by replacing commercial images with placeholders and uploads it to Envato using ftp.

For wp themes, we use 2 repos: one for the theme, other one for the framework referenced as submodule. Framework repo has a different branch for each theme, this way we can easily merge bug fixes/features add across different themes.

A build script extracts strings for translation, creates pot file and then theme.zip/download.zip

// folders layout
css
demo // demo xml
docs

// framework submodule
framework 
framework/php
framework/js
framework/images
framework/css

images
js
languages
Licensing

// download/theme zips, screenshots, not tracked
package
package/upload_info
package/screenshots

psds
theme
theme/php
theme/compressed

BF

@pixelentity that’s clever!

I’m also curious about the topic as my themes versioning is currently in big mess and I want to organize it better. Are you using services like beanstalk or it’s your own git server?

purethemes said
Are you using services like beanstalk or it’s your own git server?

@ pixelentity — What build tool do you use?

My typical theme directory looks like this:

# Wireframes, drawings, etc before working on design in the browser
/concept/assets
/concept/layout
/concept/pages

# Database backups
# Archive of customizations done for buyers for easy reference
# Diffs between platform releases
/dev/backup
/dev/customization
/dev/diffs

# All the theme documentation
/documentation

# The editable PNG, PSD, AI files for assets used in the site
/source

# The ThemeForest icons and preview images
# The ZIP packages that are uploaded to ThemeForest
/themeforest/preview
/themeforest/releases

# Where all the production code/img/css/etc is
/web-root

@ purethemes — I’m using GitHub.

GravityDept said
@ pixelentity — What build tool do you use?