website

[yoshuawuyts]

What should the website convey? Right now I've heard talk about adding more badges, but maybe it'd be good to think about what purpose the site should serve. From my needs I'd expect it to have at least the following information per project:

• Project name
• Project description (!)
• NPM version
• Node compat version
• Link to NPM
• Link to GitHub
• Link to possible documentation page

What am I missing from the list?

[jonathanong]

a lot of the badges already give that stuff. i.e. most like to a relevant page.

[rlidwka]

Website is basically used to quickly look up which builds are failing. :)

Project description is missing though, see #2.

[Fishrock123]

Project name Project description (!) Link to GitHub Link to possible documentation page

Name will link to the project (github), all docs are going to be in the readme.

NPM version Node compat version Link to NPM

Those are all badges.

Short descriptions seem like the only thing missing. The list should be as concise and wall-of-text-less as possible, imo.

[jonathanong]

hmmm i kind of like it without descriptions. nice and straight to the point. the module names should generally reflect what the module does anyways.

[yoshuawuyts]

If you go with no descriptions, there's no need to have two interfaces for the site (user-facing + dashboard). A table layout as-is should be just fine then, I think.

[Fishrock123]

People can just click the links.. right?

sigh

[dougwilson]

lol

[jonathanong]

okay i'll close this for now :D site works decently well already. open a new issue if someone has a better design