WordPress Boilerplate is a simple starting point which includes WordPress as a submodule, the required configurations and a dummy plugin & theme structure.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
uploads
wordpress @ e2ac39a
wp-content
.gitignore
.gitmodules
.htaccess
README.md
wp-cli.yml
wp-config.php

README.md

WordPress Boilerplate

WordPress Boilerplate is a simple starting point which includes WordPress as a submodule, the required configurations and a dummy plugin & theme structure.

Motivation

Typically, WordPress installations are a spaghetti of the WordPress core, plugins, themes and what have you. This makes upgrading WordPress a pain. The point of this boilerplate is to keep the WordPress core and everything else cleanly separated. This is achieved by using git submodules and some config hacking and Apache redirects :)

Installation

Clone the repository:

git clone --recursive git://github.com/Darep/wordpress-boilerplate.git

And remove this origin repository from your working copy:

cd wordpress-boilerplate
git remote rm origin

Add your new origin repository to your working copy:

git remote add origin <url_here>

Upgrading Wordpress

After installing this boilerplate, keeping Wordpress up-to-date via git is pretty easy.

Go to the submodule directory:

cd wordpress

Fetch the tags from git:

git fetch --tags

Checkout the version you want to upgrade to (e.g. git checkout 3.7.1):

git checkout <tag>

Commit your Wordpress upgrade:

cd ..
git commit -m "Updating wordpress to <tag-name>"

Author

Antti-Jussi Kovalainen. Twitter, GitHub, homepage

Contributors

  • Jasper van Wanrooy (jappievw) : Readme refactoring, Upgrade instructions, gitignore fixes, WP 3.7 security config info

Contributing

Contributions are most welcome! And well-tested and documented contributions are more welcome than others ;)

  1. Fork the repository
  2. Create a branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create a pull request

License

Licensed under the MIT license.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.