Pull in all the wiki stuff?

[vweevers]

This is.. well, awesome, and could very well replace the levelup modules wiki page.

We could then also list compatibility with levelup@2 and/or abstract-leveldown@2.

And then put it on the website! :)

[MeirionHughes]

I didn't even know that was there, and I probably wouldn't have made this if I had known. Guess it might get more use if its an open-repo for people to add stuff and correct it.

Makes sense to go over everything to and list compatibility.

[vweevers]

Is there a way to automatically make badges like this?

[vweevers]

Had a look at the shields.io service. It's relatively easy to add new badges. For example the npm license badge queries the npm registry to get the license field from package.json.

In the same vein, a badge like https://img.shields.io/npm/dep/leveldown/abstract-leveldown.svg could request https://registry.npmjs.org/leveldown/latest to get the version range of abstract-leveldown.

[vweevers]

And color it green if up to date, orange if minor outdated, red if major outdated.

[MeirionHughes]

Ah okay cool, nice. 👍

[vweevers]

I also see a possibility here to explain the ecosystem, from easy to advanced.

I.e. put level at the top, saying "the main entry point for beginners - bundles levelup, encoding-down and leveldown". Then list levelup, with a description that conveys levelup is the glue, without undermining level. Then the stores, encoding-down, custom encodings, etc. End with the really low-level, half-compatible, gut-wrenchingly monkey-patched stuff.

It'll still be a succinct list. With a little bit of order and assuming each linked module has a good opening paragraph in their readme (encoding-down is currently lacking), it can be like a story. Helpful to both beginners and mad scientists.

Can later spruce it up with recipes, talks, popular dependents, what have you.

[vweevers]

WIP: https://github.com/Level/awesome/tree/more-awesome

[ralphtheninja]

Very nice. Maybe we could "refactor" out all the dependency badges out to the awesome repo?

[vweevers]

Maybe we could "refactor" out all the dependency badges out to the awesome repo?

Hmm not sure. In fact I'm not even sure awesome should have any badges. Might be too distracting, now that I look at it on GitHub

[vweevers]

No, scratch that thought. It's quite valuable here. For example the level-js badges clearly indicate it's outdated - and essentially say "you have to know what you're doing" but also "we need some help here :)". When evaluating different modules it's nice to have this overview.

[MeirionHughes]

Shame you can't get rid of the titles from each of the badges; they're somewhat redundant if you add the title to the table column.

I do like having an automated way to figuring out what is and isn't compatible / maintained.

[vweevers]

Shame you can't get rid of the titles from each of the badges; they're somewhat redundant if you add the title to the table column.

Very true, I looked everywhere but couldn't find an option that does this. It is possible if you add a logo instead of a label, but this currently requires adding a base64-encoded SVG to every badge

[MeirionHughes]

close...

this is with ?label=  on the end

super nice work taming the links in the markdown btw. 👍

looks like getting rid of that left bit would need a PR and the issue is still open: https://github.com/badges/shields/issues/343

[vweevers]

3

[vweevers]

To add (after #3):

• [x] Storage backends
• [x] Layers
  • [x] encoding-down
  • [x] deferred-leveldown
  • [x] cachedown
  • [x] subleveldown - note: incompatible with level(up) v2! Perhaps add this under plugins instead, with a levelup compat badge
• [x] Plugins
  • byteup: "prefer to use bytewise directly"
• [x] Encodings
  • [x] bytewise
  • [x] charwise
  • [x] protocol-buffers
  • [x] lexicographic-integer-encoding
• [x] Modules
  • [x] Write-streams
  • [x] Maybe a separate category for indexing & map/reduce
• [x] Replication
• [x] Complete databases
• [x] ORMs
• [x] Tools
• [x] Applications (separate page)

[vweevers]

@MeirionHughes do you think plugins like your levelup-async-iterator should peer-depend on levelup to express compatibility? We can then also derive badges from this

[vweevers]

Added a note to the wiki.