The Register-Guard’s 3rd party sub-theme.
At the RG, we’ve learned over the years that its best to have a super simple template for use with 3rd party systems.
- HTML4 strict (a lot of 3rd parties will frack with DTD, and I have yet to see any that use an HTML5 document type.)
- Simple CSS/HTML.
- NO styling of core elements/tags.
- Easy to sub-theme and extend.
- Easy to change container width.
This theme’s sole purpose is to wrap 3rd party conent. If one needs more project-specific CSS, for additional “theme” styles, then one should include/organize/version those via other means and link to this theme’s CSS via a style link in the
The Drone template uses the "Staging" OpenX ad group:
|Medium Rectangle 1||
Be sure to change this when applying template to 3rd party.
Click or scan:
Here’s a few ways to install this code:
- Download as a
- Clone it:
$ git clone https://github.com/registerguard/drone.git.
- Fork it and clone:
$ git clone firstname.lastname@example.org:USERNAME/drone.git.
Assuming you already have Grunt.js installed ...
Navigate to the local repo’s
$ cd drone/source/
Install Grunt tasks:
$ npm install
Test the development build:
$ grunt # "grunt dev" would also work.
Visit the development build:
Note: The above URL will depend upon your local development environment; for previewing my projects I use XAMPP.
At this point, you can modify any of the files, especially the ones found in the
To make life easier while developing, run:
$ grunt watch
watch command will run a development build any time these folders/file(s) change:
/source/Gruntfile.js /source/files/styles/**/* /source/files/templates/**/*
Once you’re ready to do a production build, run:
$ grunt prod
Push the production build to your GitHub repo.
Depending on your setup, you may need to pull the latest build to your production server.
Visit the production build locally:
Note: The production build’s asset files are absolutely linked to the production server; hence the need to get the latest files there before previewing the production’s HTML file and related assets.
Update production theme:
Finally, follow the appropriate steps to update the production build’s path on the various RG production systems/environments and/or languages.
Copyright © 2013-2014 The Register-Guard