I think the best way is to create Theme Options and let the administrator decide which page is each one, with a dropdown for example. This way you can get the selected page no matter the environment.
Mark Jaquith maintains a git repo of WordPress, synced with the SVN every half hour. https://github.com/markjaquith/WordPress He also describes how to work with WP in git here: http://markjaquith.wordpress.com/2011/05/26/developing-on-wordpress-using-git/
More then likely it is personal preference. Some people like the workflow introduced by SVN, and some just don’t like the distributed model of Git. Some like the way commits, branches, tags etc are handled in one revision control over another. It could also be that they where using SVN before Git was stable enough … Read more
I set up every environment with a fresh WordPress installation. Then I do an initial commit from my local dev and start working there with Gitflow Workflow. Then I deploy the develop branch to the staging environment and the master branch to the live site. I ignore all the uploads in wp-content/uploads. Every instance will … Read more
It seems unorthodox but I added my user to the _www group: $ sudo dseditgroup -o edit -a ‘whoami’ -t user _www Finally, I gave write privileges to the group: $ sudo chmod -R g+w /path/to/dir That seems to work, but like I said seems like a weird solution to add my user to the … Read more
In a nutshell there are two basic approaches to this: Build elsewhere and upload (in one way or another) result to the target server Do everything right on target server There is variety of solutions that will do either of this or some mix of the two. The simplest possible way for the conditions you … Read more
How to run subversion and staging environments when running WordPress
Underscore Based Theme File Permissions in Git
Git Hosting for WordPress SVN Plugin Repository [closed]
WordPress Core files not being ignored by Git