Last updated February 1, 2013.
Thanks for helping out DrupalCon by building a theme! We have created a process to streamline contributing to DrupalCon and give you credit on your Drupal.org profile for your work!
We will provide you with a public Drupal.org project called drupalcon_base in which to place your theme. We do not require you to use this as your actual base theme, but please take a look at the few things it does, it helps with identifying dev/staging sites for developers and themers.
Getting Started
If you prefer to develop locally, use the git instructions for drupalcon_base
If you want to build your theme on our systems here's what you need:
- A Drupal.org account
- An SSH key for Git
- A dev environment in the Drupal.org infrastructure (see Step 2 of the linked page)
- And you will need to be added as a maintainer of drupalcon_base, just let us know your Drupal.org username and that you are building the theme.
Once you have a dev environment set up, you can get started! To help familiarize yourself with Git, your first step should be to set up a subdirectory in which to place you theme (and base theme if needed).
- So, SSH into your dev environment :
- Change to the themes directory of your site:
- Delete the drupalcon_base folder that is already there:
- Use Git to clone in the latest copy of drupalcon_base:
- Change to the drupalcon_base folder:
- Create a folder to contain all of your theming files (base and sub-themes too), please name this folder the same as the domain of the DrupalCon site:
- Since Git cannot add an empty directory to the repo, we will add an empty .gitignore file to the directory:
- If you use
git statusnow, you will see the new directory as an untracked file: - We can then add all the untracked files to the repo at once:
- Now, a check of
git statuswill show us that the file is ready to be committed:[twardnw@devwww drupalcon_base]$ git status
# On branch 7.x-1.x
# Changes to be committed:
# (use "git reset HEAD <file>..." to unstage)
#
# new file: saopaulo2012/.gitignore - Now commit your change(s)! Please use clear and concise commit messages, including an Issue number if you have one:
- Last step, push your changes back to the remote repo:
- You can then look at the commit log for drupalcon_base to see your commit.
ssh yourusername@devwww.drupal.org
cd /var/www/dev/theme-saopaulo2012.redesign.devdrupal.org/htdocs/sites/all/themes
rm -rf drupalcon_base
git clone --recursive --branch 7.x-1.x twardnw@git.drupal.org:project/drupalcon_base.git
cd drupalcon_base
mkdir saopaulo2012
touch saopaulo2012/.gitignore
[twardnw@devwww drupalcon_base]$ git status
# On branch 7.x-1.x
# Untracked files:
# (use "git add <file>..." to include in what will be committed)
#
# saopaulo2012/
nothing added to commit but untracked files present (use "git add" to track) git add -A
git commit -m "Setting up SaoPaulo2012 theme directory"
git push -u origin 7.x-1.x
Helpful links
- Developing on Drupal.org servers
- Drupal.org Git documentation
- Request a development environment
- Git instructions for drupalcon_base
Need More Help?
You can send us a message or twardnw and drumm are in IRC most of the time, try the #drupal-association and #drupal-infrastructure channels