In the “CSS” tab of the Admin interface, select “Remote” as the source for the CSS file and enter the remote URL into the interface.

After you click “Submit” you will be asked the context where you want the remote CSS file used (Globally, Layout Specific, Group Specific, File Specific).

Only users with full administrative privileges may specify a remote CSS file.

DOMBlogger does not allow a resource to have two different domain names depending upon whether it is being served over HTTP or HTTPS. The path to the external resource must be identical regardless of the protocol being used.

The CMS also does not allow inclusion on insecure resources on a secure web page. If the remote source for your external style sheet does not provide the file over HTTPS as well as HTTP, the style sheet will not be loaded on pages DOMBlogger serves as SSL. This apparently is a problem with some Content Distribution Networks (such as the Amazon Cloudfront CDN with a CNAME URL).

If that is a problem for you, I am sorry, but a secure page has no business including resources from an insecure server. Browsers will often notify users of the problem, and users are right to shy away from secure pages that contain insecure resources.

You may define one custom style sheet that is global in nature. It will be served with every web page under control of the DOMBlogger Content Management System.

This is the file you use to define styles you want applied everywhere. For example, you can have this file automatically place smart quotes around the contents of a q node in the context of a p node:

p q:before {
 content: '\201C'; }
 p q:after {
 content: '\201D'; }

He said I do not know who took the cookie from the cookie jar but I knew it was him.

The CSS applies the quotation marks, they are not in the HTML source.

The Global CSS file is always loaded after any CSS files that are part of DOMBlogger itself and before any CSS files associated with the other contexts.

There may be some cases where you need to apply over over-ride a style when a specific layout template is used.

For example, you may want to apply custom fonts to one specific layout but keep the default specified fonts for other layouts. This is done through a layout specific CSS file.

The Layout specific CSS is loaded after the Global CSS file.

You may have some styles you only want to apply to documents that fall into a certain grouping, such as blogs.

I recommend against using this, for site consistency purposes it is better not to have different styles apply to different groups of documents. You may however do so if you choose.

Any Group specific CSS files are loaded after any Layout specific CSS files.

Finally, you may have a CSS file you want to have applied to a specific web page. If defined, it will always be last CSS file applied to a web page.

In most cases, it is usually better to define page specific styles in your Global CSS file unless you are really sure you will not want to use the same style on a different web page.

To add your style sheets to the CMS, use the “CSS” tab in the admin interface.

For the Global CSS style sheet, you will only be able to upload a file replacing any existing Global CSS or edit an existing Global CSS file on-line using our very basic web based text editor (basically a textarea node).

Only users with full administrative privileges may modify or replace the Global CSS file.

For Layout, Group, and Page level CSS files, you also have the option of selecting an existing file to apply in a new context. For example, if you have a style sheet already applied to the “Condition” layout and you also want it applied to the “Yosemite” layout, you may choose that file from a drop down menu of existing Layout CSS files. This paragraph is confusing and needs to be rewritten.

Only users with full administrative privileges may modify or replace a Layout specific CSS file. Group or Page specific CSS files may be modified by lower level content providers if a user with full administrative privileges has authorized it.