Comments on: typography.css in concrete5 themes

By: admin

admin — Sat, 05 Nov 2011 14:20:36 +0000

@Andy Frahm this fix with the timestamp is for web developers who need to debug and immediately see the changes in typography.css of the theme they are working on. It just prevents the browser from caching typography.css. There is absolutely no need to keep that workaround forever, so it's not a problem if the core upgrade overwrites that edit. But if you for some reason need to keep that workaround forever, you can simply copy the files from /concrete/blocks/content/ to /blocks/content/ and make the changes there.

By: Andy Frahm

Andy Frahm — Wed, 02 Nov 2011 18:53:37 +0000

Anything you edit in the main concrete folder will need to be updated with every new release. There must be a better way.

By: pthalacker

pthalacker — Wed, 17 Feb 2010 19:45:20 +0000

I am missing something. Should I remove classes from main.css and put them in typography.css and then include typography.css in my theme template? Do I have to remove the basic elements from the default tinyMCE skin to have them appear in the editor, or will putting them in typography take precedence over the default editor skin?

By: Johannes Link

Johannes Link — Sun, 27 Dec 2009 14:39:55 +0000

If not all of your CSS-Settings of typography or your basic settings are used in the editor, you can modify
concrete/js/tiny_mce/themes/concrete/skins/default/content.css
and remove some of those css styles (i.e. body,pre,td,h1,h2,h3,h4,h5,h6).
Then it takes those of your typography.css (which must reside in your theme root!)

By: Chris Seymour @ c5mix.com

Chris Seymour @ c5mix.com — Fri, 11 Sep 2009 16:13:21 +0000

Thanks for the timestamp tip with fixing the caching of typography.css. That was driving me nuts and couldnt figure out how to clear the cache. Great tips!