theme

I find on some Drupal sites that I want to see information all the time behind the scenes, but I don't want the client to see. I added simple code to allow me to do just that. While it is true that I can use the Devel or Devel Themer modules, there is some information that I want which is not provided by Devel, so creating my own custom code works. This code can be embedded into a block, module, or in just the page.tpl.php (or any page template suggestions).

Now, to make things simpler in this tutorial, I embedded inline CSS, but you can obviously add this to any .CSS file.

global $user;
$username = $user->name ;
if($username=="developer")
{
// Generate all your Drupal and PHP variables
$nid = arg(1);
$alias = drupal_get_path_alias();
// Print out your HTML div tag with inline CSS or CSS class attribute
echo ('

Developers Only:

Radix is a base theme for Panopoly with Bootstrap and SASS goodies.

Features

• Built for Panels and Panopoly
• Flexible and Responsive layouts from Panopoly Theme
• Components and plugins from Twitter Bootstrap
• Grid system. (Demo)
• Responsive Panels out of the box with Radix Layouts
• SASS awesomeness

Demo

• Demo

Themes based on Radix

• Sizzle: comes with responsive install screens
• Chef: starter theme for the restaurant distribution. (Demo)

Contrib Modules

Disable debugging features and replace default logo

Next, we will disable the debugging features of Omega subthemes and replace the channelAustin logo with your logo:

1. Click on Appearance in the Admin Toolbar
2. Find the Community Media Theme and click Settings
3. Click debugging in the list of vertical tabs
4. Uncheck Enable the debugging (placeholder) blocks for the selected roles and Enable the grid overlay for the selected roles
5. Now towards the bottom of the form, find the Logo image settings
6. Either upload a logo or link to an existing logo. The logo will preferably be a transparent PNG, but a GIF or JPG will also work.
7. Click Save configuration

Remove Secondary Menu from theme settings

The secondary menu (the User Menu that includes My Account & Log Out) should always be disabled from the theme settings. Instead, if you wish to use the User Menu, place the User Menu block in the region where you want that menu to appear. This is how to do it:

1. Click on Appearance in the Admin Toolbar
2. Find the Community Media Theme and click Settings

Installing sass and Compass for editing CSS

Community Media Theme is now using sass, a more efficient way to write CSS. The files to edit are the .scss files in the /sass sub-folder. These will then be compiled to the normal .css files that are presented to the browser. To do this you will need Compass installed on your server.

1. To install Compass you will need to have Ruby installed. If it's not installed on your server, the easiest way (if you are on Linux) is to install RailsReady: https://github.com/joshfng/railsready
2. After that, run sudo gem install compass
3. Then go to /sites/all/themes/cm_theme/cm_theme_zen and run compass watch. Any changes you make in a .scss file will now be compiled to .css.

The following pages only apply to the 3.x version of Omega.

The following pages will explain what Omega 3.x is, how it works and outline established best practices for getting started with your own Omega based subtheme. Please start at the beginning as Omega's approach to theming is different than other themes. If you assume too much you may find complications in understanding how to use Omega. Looking for Omega 4.x documentation? Go here.

If you are just getting started using Omega, please do yourself a favor; follow the logical progression of this handbook. Start here means start here. If you skip ahead assuming too much you will likely encounter complications that you could have avoided by understanding the basics from the beginning. Each page below is a distinct concept and they are intentionally ordered in such a way as to walk the user through getting started to being fully informed as quickly and thoroughly as possible.

Drupalize.Me offers a free video overview of Omega 3.x... Omega 3.x Overview

Omega 4.x documentation

Please be patient. Documentation for 4.x will be added as development on the 4.x version continues. Join us in IRC #drupal-omega to express your interest in participating. All are welcome.

Be aware that the 4.x version has no final release, yet. Documentation will likely be scarce until we are closer to a stable release.

Should I use 3.x or 4.x?

Q: Are you new to Drupal?
A: If you answered yes, then use 3.x. It has a stable release, is fully documented and there is a ton of community support available to help you if you have issues.

Q: Are you an expert? Q: Do you like experimental code?
A: If you answered yes and you want to play with the new code then go ahead and give 4.x a spin. The assumption here is that you are aware there is no stable 4.x release. With that in mind, go for it and by all means create issues so we can work to make 4.x ready for prime-time.

This issue is a good description of the changes in 4.x