urosm
/
ikiwiki
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Arguing more

master
desci 2016-04-15 08:24:38 -04:00 committed by admin
parent 65095203f5
commit 8eb3a06f1e
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/themes/discussion.mdwn vendored
View File

@ -35,6 +35,12 @@ links to the actual theme. -- [[anarcat]]
>>> version of `page.tmpl` containing only the features you personally
>>> need, but the `page.tmpl` in ikiwiki should be comprehensive. --[[smcv]]
>>>> I've tried to make the least changes possible in [this page.tmpl file](https://notabug.org/iikb/ikiwiki-theme-bootstrap/raw/master/templates/page.tmpl), but I couldn't overcome the suckness of bootstrap itself.
>>>> I am aware of alternatives to bootstrap, but it seems that every one of them would require some changes in the `page.tmpl` to work as expected.
>>>> I think it is realistic to have a bootstrap (or other superb, fantastic css frame*lazy*work) without a `page.tmpl`,
>>>> but I also think there should be other way around the chaos of each and every [[available theme|theme_market]] having it's own installing proccess.
>>>> Other argument I have is: could we have a theme-contrib, like the [[plugins]] have? This would require the mantainer to implement the new features in their themes.
---
I have a question.