History of TemplateChangelog
just some quick notes:
!!! tidy up and separate navbar links
use <ul><li> to be in accordance with w3c and wcag recommendations and it also allows for amazing styling possibilities using css
* tools --> move to the bottom of the page (???)
** lock / unlock
** export
* tabs --> move to the top of the page
** edit
** history
* sorting --> remain just above the table
__where do the structure and backlinks dropdowns belong?__
!!!reducing number of divs
the number of divs used in tikipro is still a bit excessive. perhaps we can find a couple more places where these can removed / changed to something else:
<div class="box">
<div class="boxtitle">foo</div>
<div class="boxcontent">bar</div>
</div>
could become:
<div class="box">
<h3>foo</h3>
<p>bar</p>
</div>
would allow for same amount of styling freedom. the only downside is that <p> doesn't allow block elements in xhtml, which means that we have to close off </p> before adding divs and lists
!!! tidy up and separate navbar links
use <ul><li> to be in accordance with w3c and wcag recommendations and it also allows for amazing styling possibilities using css
* tools --> move to the bottom of the page (???)
** lock / unlock
** export
* tabs --> move to the top of the page
** edit
** history
* sorting --> remain just above the table
__where do the structure and backlinks dropdowns belong?__
!!!reducing number of divs
the number of divs used in tikipro is still a bit excessive. perhaps we can find a couple more places where these can removed / changed to something else:
<div class="box">
<div class="boxtitle">foo</div>
<div class="boxcontent">bar</div>
</div>
could become:
<div class="box">
<h3>foo</h3>
<p>bar</p>
</div>
would allow for same amount of styling freedom. the only downside is that <p> doesn't allow block elements in xhtml, which means that we have to close off </p> before adding divs and lists