Skip to content

Support npm's forthcoming Ecosystems and Collections #64

@unscriptable

Description

@unscriptable

Follow-on from #59. See http://blog.npmjs.org/post/94662089625/the-future-of-the-npm-website-lets-map-this-road

Seems like we need to do the following when the new npm-www is ready:

  1. register an npm Ecosystem
  2. prompt existing extension and starter authors to indicate that their packages belong to the the "rave" ecosystem
  3. Create docs / instructions for authors about how to be included in the "rave" ecosystem
  4. Encourage authors to create npm Collections based on their starters (and extensions in some cases?)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions