v2 considerations

[ryanve]

How we can make v2 even better than v1? Feedback wanted on this and other ideas you have =)

• .min file: Is there still value in providing a minified file in the repo or are most people using build tools?
• .mq: Are you using this method? It feels a bit out of the scope of this module. We could remove it and recommend actual.is as an equivalent alternative
• element: Do we want to continue to support collection elements or only native elements?
• cushion: Do we want to continuing supporting cushion as a 2nd argument or is there a more expressive way we can do this?
• structure: I'd like to replace grunt with npm scripts and use a flat directory structure like I've done in some of my other projects: eol, fm, cxn
• linting: I'd like to replace jshint with eslint
• pages: Coinciding with the structure change I plan to change the default branch to gh-pages so that a playground and test area can be made available on ryanve.github.io/verge

[illarionvk]

I vote:

• Keep .min file
• Remove .mq method
• Only native elements
• Keep the cushion option
• Flat directory
• ESLint
• Pages as default branch

Thanks for creating and maintaining this library!

[ryanve]

@illarionvk cool—thanks for the detailed input!