diff options
author | spalax <spalax@web> | 2014-04-16 10:57:08 -0400 |
---|---|---|
committer | admin <admin@branchable.com> | 2014-04-16 10:57:08 -0400 |
commit | e511073db7bb5d217d76f212e8967b335a7be695 (patch) | |
tree | 325169ad965a81f68b2c7b14ef33444be5dac232 /doc | |
parent | f8b840d74eeb0b6514e3e6302afbe6d640d9c6d1 (diff) | |
download | ikiwiki-e511073db7bb5d217d76f212e8967b335a7be695.tar ikiwiki-e511073db7bb5d217d76f212e8967b335a7be695.tar.gz |
Comment
Diffstat (limited to 'doc')
-rw-r--r-- | doc/todo/concatenating_or_compiling_CSS.mdwn | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/todo/concatenating_or_compiling_CSS.mdwn b/doc/todo/concatenating_or_compiling_CSS.mdwn index ed3f2e846..e0715e730 100644 --- a/doc/todo/concatenating_or_compiling_CSS.mdwn +++ b/doc/todo/concatenating_or_compiling_CSS.mdwn @@ -108,3 +108,18 @@ extension would have to be locked-down. Perhaps it's better to implement this without that feature initially. --[[smcv]] + +> Although I understand the need to improve CSS inclusion, I wonder why you are +> proposing concatenating CSS rather than including them as several `<link +> type="text/css" href="FILE.css" rel="stylesheet">` lines +> in the header: unless I am missing something, I see this as far more simpler +> than concatenating them. +> +> This would imply that a template variable `CSS` is added to the page +> template, to be filled with those lines. +> +> Whatever solution is used, I agree that such a thing would be useful: +> adding CSS (rather than replacing the existing one) should be easier. +> +> -- [[Louis|spalax]] + |