[TYPO3-dev] indexed search: where is the css template?

[Christopher]

Hi,

On 3/14/06, Martin Kutschker <Martin.Kutschker at n0spam-blackbox.net> wrote:
> Kai Laborenz schrieb:
> > Michael Stucki schrieb:
> >
> >> The template validates successfully even though it uses tables in some
> >> places (which I don't consider to be a bad thing for a result list).
> >>
> >> If you don't like it, feel free to make a better suggestion.
> >
> >
> > tables may be ok for search results but definitely not for forms and not
> > the way, they were used in this template.
>
> But "only" with accessibilty in mind. Just because I use CSS for styling,
> doesn't mean I have to fiddle with CSS for layout. And tables have no
> impact (if you take care which attributes you use) on the validity of the
> document.


If the template ships with a good default set of styles, you won't
have to 'fiddle with css for layout'. But I find this comment a little
irksome; as someone who builds Typo3 sites, I _BEG_ all developers to
just MARK UP THE DATA.

Pay no attention _whatsoever_ to design when you are designing
extension (or core!) output. Mark up the data the best way you
can--use the most appropriate html you can conceive--and if you don't
like to 'fiddle with css for layout', then submit the markup to the
community--or to me directly if you want me to put my money where my
mouth is--for styling.

Extension output should be extremely generic--any built-in design
ideas are eventually going to cause problems for people whose design
ideas are different. It's much easier to use css to style html that
has no preconceived design ideas than it is to style html that's
inherited a strong opinion about its appearance from the person who
coded it...


> I suggest to add a table-less template as an add-on. Dropping the table
> alltogether might break the CSS of existing sites.

+1. No need to break existing sites.


-Christopher