Drupalcamp Site Archive

Getting your site archived

It's really simple to get your site archived and listed in the Drupalcamp archive, it's a two step process:

Create a static copy of your site

There are comprehensive instructions on how to create a static copy of your existing site on Drupal.org, but the goal here is to end up with a static site contained in a folder somewhere.

Important things to note:

  • You should not use any special htaccess rules or tricks.
  • You should make sure there's an 'index.html' at the root of your static site's folder structure.
  • There should be no forms on the site, like search forms or registration forms.
  • You should add a simple message to the top of the site saying that the site has been archived.

Getting the site hosted and added to the archive

We use Github to host the sites, mainly because its really easy to set up and free! All you need to do is add your static site to a new github repo, and then ask us to fork it, provide some extra details for the archive listing and we can add your site. These steps are outlined in detail below.

Adding your site to github

Log in to or create a Github account and create a new public repo in github.

Now you will need to add all your static files to that repo and push them up to Github. The top level directory of your repo should have an index.html file at least. You will want to push into a branch named: gh-pages.

Additionally you will need to create an empty file at the top level of your repo called: .nojekyll, this will stop Github from processing your static site and ensure that all your files will be available.

After a few minutes you should be able to view this site at: username.github.com/reponame. Verify that the site looks correct and that all the files have uploaded etc.

Getting listed in the archive

As we need to ensure that sites served from our domain are secure and are correctly archived, we will fork the repo you created, and point the desired domain at our github repo.

To start this process, open an issue against our Drupalcamp archive repo and include the following information:

  • The name of your Drupalcamp as you'd it to appear in the archive.
  • A link to he repository on github that you created above.
  • The date when the camp started, e.g. 17 September 2012.
  • The desired subdomain to host the archived camp site on. This should follow this syntax: {region}-{year}-{month}.drupalcamparchive.org, if there is likely to be only one camp in that region in that year, then you may omit the {month} part. E.g. oxford-2012.drupalcamparchive.org or brighton-2012-06.drupalcamparchive.org.
  • A small 'blurb' about the Drupalcamp for the listing page. This should be no more than 50 words. See the current archive for inspiration.

After you've posted the issue we'll review your request and if you're site is accepted then we'll fork your repo into our account, and add you to the archive listing.

Making changes after archival

If you discover issues with the static site then you should fork our copy of the repo and then fix then and issue a pull request and we'll review your request and take it from there.