forked from WhiteHouse/fortyfour
-
Notifications
You must be signed in to change notification settings - Fork 0
vynsynt/fortyfour
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
FORTYFOUR BASE THEME -------------------- Fortyfour theme is a work in progress. Our vision is for Fortyfour to become a starter theme for White House sites to encourage reusability of existing design assets and code and to provide a consistent look and feel across sites. Sites should be able to easily reuse generic designs and layouts provided by Fortyfour. Sites can also subtheme Fortyfour to implement designs without starting from scratch. Fortyfour is not a working, stand-alone theme yet. It's more of a proof-of-concept. A few themes in active development at the White House (like Petitions44) are working to "back into" using Fortyfour as a basetheme, moving site-specific markup and logic out of template files (e.g. page.tpl.php) into theme functions and preprocessors. Then, where possible, we are moving template files out of site specific themes and into Fortyfour. Ideally, we will have site-specific subthemes like Petitions44 inheriting most (or all) templates from Fortyfour. Then the site-specific themes will simply (1) choose from among available regions in Fortyfour, (2) include some custom CSS and graphics, and (3) implement their own preprocessors in template.php as needed. Fortyfour includes a few "superheader" and "superfooter" type elements. By default these elements include static markup from whitehouse.gov. These are included to make sites look like "subsites" of whitehouse.gov. They can all be easily enabled or disabled on the Fortyfour theme settings page (and on settings pages of subthemes of Fortyfour). To override any of these elements, copy and paste the corresponding template file(s) into your own subtheme: - fortyfour-footer.tpl.php - fortyfour-header.tpl.php - fortyfour-mainnav.tpl.php - fortyfour-subfooter.tpl.php Fortyfour is a subtheme of Zen 5. You can subtheme Fortyfour the same way you would create a subtheme of Zen. Just declare fortyfour as the base theme in your theme's info file (base theme = fortyfour). The rest is the same as building a theme with Zen. Here are Zen's instructions for building a theme with Zen: BUILD A THEME WITH ZEN ---------------------- The base Zen theme is designed to be easily extended by its sub-themes. You shouldn't modify any of the CSS or PHP files in the zen/ folder; but instead you should create a sub-theme of zen which is located in a folder outside of the root zen/ folder. The examples below assume zen and your sub-theme will be installed in sites/all/themes/, but any valid theme directory is acceptable (read the sites/default/default.settings.php for more info.) Why? To learn why you shouldn't modify any of the files in the zen/ folder, see http://drupal.org/node/245802 *** IMPORTANT NOTE *** * * In Drupal 7, the theme system caches which template files and which theme * functions should be called. This means that if you add a new theme, * preprocess or process function to your template.php file or add a new template * (.tpl.php) file to your sub-theme, you will need to rebuild the "theme * registry." See http://drupal.org/node/173880#theme-registry * * Drupal 7 also stores a cache of the data in .info files. If you modify any * lines in your sub-theme's .info file, you MUST refresh Drupal 7's cache by * simply visiting the Appearance page at admin/appearance. * 1. Setup the location for your new sub-theme. Copy the STARTERKIT folder out of the zen/ folder and rename it to be your new sub-theme. IMPORTANT: The name of your sub-theme must start with an alphabetic character and can only contain lowercase letters, numbers and underscores. For example, copy the sites/all/themes/zen/STARTERKIT folder and rename it as sites/all/themes/foo. Why? Each theme should reside in its own folder. To make it easier to upgrade Zen, sub-themes should reside in a folder separate from the base theme. 2. Setup the basic information for your sub-theme. In your new sub-theme folder, rename the STARTERKIT.info.txt file to include the name of your new sub-theme and remove the ".txt" extension. Then edit the .info file by editing the name and description field. For example, rename the foo/STARTERKIT.info file to foo/foo.info. Edit the foo.info file and change "name = Zen Sub-theme Starter Kit" to "name = Foo" and "description = Read..." to "description = A Zen sub-theme". Why? The .info file describes the basic things about your theme: its name, description, features, template regions, CSS files, and JavaScript files. See the Drupal 7 Theme Guide for more info: http://drupal.org/node/171205 Then, visit your site's Appearance page at admin/appearance to refresh Drupal 7's cache of .info file data. 3. Choose your preferred page layout method or grid system. By default your new sub-theme is using a responsive layout. If you want a fixed layout for your theme, delete the unneeded responsive-sidebars and responsive-sidebars-rtl css/sass files and edit your sub-theme's .info file and replace the reference to responsive-sidebars.css with fixed-width.css. For example, edit foo/foo.info and change this line: stylesheets[all][] = css/layouts/responsive-sidebars.css to: stylesheets[all][] = css/layouts/fixed-width.css Why? The "stylesheets" lines in your .info file describe the media type and path to the CSS file you want to include. The format for these lines is: stylesheets[MEDIA][] = path/to/file.css Alternatively, if you are more familiar with a different CSS layout method, such as GridSetApp or 960.gs, etc., you can replace the "css/layouts/responsive-sidebars.css" line in your .info file with a line pointing at your choice of layout CSS file. Then, visit your site's Appearance page at admin/appearance to refresh Drupal 7's cache of .info file data. 4. Edit your sub-theme to use the proper function names. Edit the template.php and theme-settings.php files in your sub-theme's folder; replace ALL occurrences of "STARTERKIT" with the name of your sub-theme. For example, edit foo/template.php and foo/theme-settings.php and replace every occurrence of "STARTERKIT" with "foo". It is recommended to use a text editing application with search and "replace all" functionality. 5. Set your website's default theme. Log in as an administrator on your Drupal site, go to the Appearance page at admin/appearance and click the "Enable and set default" link next to your new sub-theme. Optional steps: 6. Modify the markup in Zen core's template files. If you decide you want to modify any of the .tpl.php template files in the zen folder, copy them to your sub-theme's folder before making any changes. And then rebuild the theme registry. For example, copy zen/templates/page.tpl.php to foo/templates/page.tpl.php. 7. Modify the markup in Drupal's search form. Copy the search-block-form.tpl.php template file from the modules/search/ folder and place it in your sub-theme's template folder. And then rebuild the theme registry. You can find a full list of Drupal templates that you can override in the templates/README.txt file or http://drupal.org/node/190815 Why? In Drupal 7 theming, if you want to modify a template included by a module, you should copy the template file from the module's directory to your sub-theme's template directory and then rebuild the theme registry. See the Drupal 7 Theme Guide for more info: http://drupal.org/node/173880 8. Further extend your sub-theme. Discover further ways to extend your sub-theme by reading Zen's documentation online at: http://drupal.org/documentation/theme/zen and Drupal 7's Theme Guide online at: http://drupal.org/theme-guide
About
7.x base theme for White House sites
Resources
Stars
Watchers
Forks
Packages 0
No packages published