[pmwiki-users] disabling standard markup etc.

[Hans]

Thursday, March 8, 2007, 5:51:19 PM, Simon wrote:

> To get your CSS to override existing CSS it will help if you change to,
> as follows,
> the order of these lines in your template.

>   <!--HeaderText-->
>   <link rel='stylesheet' href='$SkinDirUrl/pmwiki.css' type='text/css' />

> This ensures that your skin CSS overrides the pmwiki css
> I believe that this should be done in the standard release.

> The order CSS is processes should I think be
> 1) local in page CSS (which I believe should be reduced to a minimum -
> moved into css files)
> 2) the template CSS (pub/skins/myskin/pmwiki.css)
> 3) skin specific CSS
> 4) cookbook recipe specific CSS
> 5) pub/css/local.css

If you are changing the skin template, I suggest you read
http://www.pmwiki.org/wiki/Cookbook/SkinGuidelines#CSS

We had  a long discussion a while ago about this, and the result was
the order of css loads outlined on the page above.
In particular skin css overrides recipe css, and local css overrides
skin css. PmWiki core css should be loaded first, so it can be
overidden by any subsequent customisation (recipes, skin, local
admin).

I don't understand why you want to load pmwiki.css at all, unless you
use the pmwiki skin. The pmwiki core css styles are loaded by pmwiki
in any case. These are styles which are important for functional
display. The styles from pmwiki.css should be handled/replaced as
suited by the skin.


Hans