convert grid to list

[ianstormtaylor]

first stab at #37 — http://cl.ly/image/2t3E0s3k1N2K

[juliangruber]

can we make it less whitespacey? The wiki IMO is so nice because you see a lot on one page. You can save space by using fonticons for license, stars and keywords, so they can go in one line.

[ianstormtaylor]

I'm down. It actually was before I converted the table to be right-aligned. Hey @visionmedia what do you think about dropping the keywords row? I feel like keywords is just for robots, not actually useful to humans reading through these packages.

[ianstormtaylor]

Newest revision: http://cl.ly/image/431X3X462m24

[ianstormtaylor]

Mobile support: http://cl.ly/image/150Y3s151r3x

[ForbesLindesay]

:+1: For removing keywords - they're just for searching and categorising. I really like that latest version.

[buschtoens]

Love it.

[tj]

sweet looks good :D I have a branch changing up the other stuff a bit but ill merge this over

[buschtoens]

Uhm, maybe we could add keywords like this.

[tj]

@silvinci i like that, i agree that keywords are not really all that useful, but regardless I like the space it fills up and that it keeps the contrast going :D

[juliangruber]

Keywords are nice for searching also...but they break the reading flow a bit where they are in the last screenshot.

[buschtoens]

Really? I think it looks more stable, since everything is lined up nicely. But we could fade in the keywords on :hover too. Google would still see them.

[juliangruber]

Hmm you're right, you only need to vertically scan the titles, vertically scanning descriptions doesn't happen. I think with some fading applied it will look rad!

[ForbesLindesay]

Doesn't google see them even if they're not visible? e.g. in a <div style="display: none;">?

I agree it doesn't add that much noise, but there's no reason that a description couldn't/shouldn't run to two lines, and if they don't add anything they shouldn't be there.

One reason they perhaps should be there is if we made them clickable and made clicking on them filter the list to only modules with that tag.

[ianstormtaylor]

doesn't google see none of this since its ajaxed in? :p

clickable keywords sounds potentially cool

[ForbesLindesay]

At some point we could make the initial load statically include the first "page" of results for google's benefit?

[buschtoens]

@ianstormtaylor That's a pretty valid point :D And +1 for clickable keywords. @ForbesLindesay +1 for static stuff. I think Google would ignore style="display: none;", but .keywords { display: none; } should work. Anyway, clicking keywords is useful.

[buschtoens]

Also, this.

[ianstormtaylor]

would be cool id component.io was a good example of sharing components with the server, if that's something that wants to happen.

we could use all the google juice we can get.. since we're competing against a pretty generic word

[tj]

@silvinci I think that sort of thing was before the days of pushState, not sure, need to look into that some more

[tj]

and thanks @ianstormtaylor this is rad

[ianstormtaylor]

of course! if there are other css duties, happy to take some on. was thinking about the sidebar next, but didn't wanna get too into getting the data required for it

[buschtoens]

Yup, pushState replaces the URL rewriting part (I suppose) but the app would need to serve the corresponding content for these URLs. (#31)

[tj]

haha yeah the component pages are really terrible, just wanted to get something up quick