Page 3 of 3
Re: Next Theme
Posted: Sun May 10, 2015 1:52 pm
by kybernator
OK, considering all your points, and the fact that responsiveness (and, at the same time, accessibility, which often go hand in hand) is quite important to me, it might be wisest not to use tables. Thank you for the explanations.
Re: Next Theme
Posted: Sun May 10, 2015 2:01 pm
by yellowled
kybernator wrote:OK, considering all your points, and the fact that responsiveness (and, at the same time, accessibility, which often go hand in hand) is quite important to me, it might be wisest not to use tables.
Semantically, an ordered list might make sense. The list items of that ol could contain a description list.
Code: Select all
<ol class="plainList">
<li><dl>
<dt>Datum</dt>
<dd>DD.MM.YYYY</dd>
<dt>Uhrzeit</dt>
<dd>HH:MM</dd>
...
</dl>
</li>
...
</ol>
(plainList is a class that come with the s9y core and removes the item numbering and the padding on the left of the ol or ul.)
However, that might be a bit over the top and hard to handle with a WYSIWYG editor.
YL
Re: Next Theme
Posted: Sun May 10, 2015 2:10 pm
by kybernator
yellowled wrote:However, that might be a bit over the top and hard to handle with a WYSIWYG editor.
Especially since CKEditor "im Auslieferungszustand" eats up description list markup - but that can be overcome
Re: Next Theme
Posted: Thu Jun 18, 2015 8:45 am
by u1amo01
Maybe you know this already, maybe not: if there is no user.css in the next theme directory, s9y will use the user.css of 2k11 instead (if there is one).
Solution maybe the same as noted in the clean-blog thread: just put a epmty user.css into the next directory. (works with clean blog, not tested yet with next)
Re: Next Theme
Posted: Thu Jun 18, 2015 7:34 pm
by yellowled
u1amo01 wrote:(works with clean blog, not tested yet with next)
It will work with Next as well. The whole user.css thing is no longer specific to themes, it's in the core now.
YL