On Mon 12 Mar 2012, Kake L Pugh kake@earth.li wrote:
Yep! The plan is to put CSS classes in one of the divs (probably the "content" one) for each category (and locale?) that the page is in. So for example the Jam Factory page would have something like:
<div id="content" class="cat:baby_changing_facilities cat:free_wifi cat:pubs cat:restaurants cat:wifi loc:park_end_street loc:west_central">
and then in your CSS you can style any of those classes individually.
Looks good to me (my CSS is out-of-date -- I'm assuming classes with ':' in are generally understood by browsers?). Having these classes would also mean we could do something like having big clear icons for things that you might want to see at a glance eg 'has disabled access', 'has baby changing facilities', etc.
Aside: Owen has observed that there are two (or possibly more) different types of category: 'is X' (eg 'Cafes') and 'has X' (eg 'Baby Changing Facilities'). I briefly wondered whether it would make sense to name them accordingly, before realising that I was about two steps away from suggesting that any node+category should be parseable as subject+predicate+object & that if I did that you would probably have to kill me.
On the other hand, we could then differentiate between the use of 'Cafes' to mean 'is a cafe' (eg G&Ds) and 'has a cafe' (eg Waterstones). If we cared.
[Goth/Gay guides etc]
I think it's best done elsewhere.
Goodgood. Are you happy to delete them or should we wait & see if anybody else on here objects?
Jx