[pmwiki-users] pmwiki skin

[shout at joshleepictures.com]

>> When I put on my designer's hat […]
> If one does not want to allow that I say change the default template
> for your site.

Being a professional web designer, I would never use any of the premade PmWiki skins (for obvious reasons, such as brand uniqueness). That said I think, the css should go where it makes the most sense architecturally (for the CMS and its recipes).

From a web development point of view it does not seem to make much sense to me to have the core CMS and its extensions (recipes) overrule custom css. For once the custom css writer will eventually come up with a way to overrule the preset css (!important). And the recipe writer will never be able to supply a css that works for all color and layout variants of a skin (or all skins and it potentially user customized variations for that matter).

I think we will all agree that especially this is a question of coding paradigms, whether you want the ‘user’ (user as in the one using the software, not the recipient of the website) to have that much freedom. Put in simple terms, should a user be allowed to come up with a css that styles the PmWiki skin (which essentially is a flexible with skin with a fixed width left column) into something totally different (e. g. a single col white on black theme with the 'menu' column positon-fixed at the bottom)?

Take care, Josh


On Aug/26, 2012, at 2340 , Hans Bracker wrote:

> 
> Sunday, August 26, 2012, 9:24:16 PM, tamouse wrote:
>> When I put on my designer's hat, I tend to disagree with you -- I have
>> found it frustrating when recipe writers force a style decision that I
>> haven't been able to override in my skin design (which is where I want
>> most of those decisions made).
> 
> If you are concerned about that and design your own skin,
> you can load your skin css after <!--HTMLHeader-->
> in  the skin template, to avoid css changes by recipes.
> 
> But for the default PmWiki skin I think it is right that the css gets
> loaded before <!--HTMLHeader-->, in order to allow customisations
> via recipes and config.
> 
> If one does not want to allow that I say change the default template
> for your site.
> 
> 
> 
> Best regards,
> Hans   
> www.softflow.co.uk
> 
> 
> _______________________________________________
> pmwiki-users mailing list
> pmwiki-users at pmichaud.com
> http://www.pmichaud.com/mailman/listinfo/pmwiki-users