Next Theme
-
- Regular
- Posts: 135
- Joined: Sat Sep 22, 2012 10:15 pm
Re: Next Theme
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
Semantically, an ordered list might make sense. The list items of that ol could contain a description list.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.
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>
However, that might be a bit over the top and hard to handle with a WYSIWYG editor.
YL
-
- Regular
- Posts: 135
- Joined: Sat Sep 22, 2012 10:15 pm
Re: Next Theme
Especially since CKEditor "im Auslieferungszustand" eats up description list markup - but that can be overcomeyellowled wrote:However, that might be a bit over the top and hard to handle with a WYSIWYG editor.
Re: Next Theme
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)
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
It will work with Next as well. The whole user.css thing is no longer specific to themes, it's in the core now.u1amo01 wrote:(works with clean blog, not tested yet with next)
YL