Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dynamically get Trailpacks from npm #6

Open
jaumard opened this issue Jan 9, 2016 · 1 comment
Open

Dynamically get Trailpacks from npm #6

jaumard opened this issue Jan 9, 2016 · 1 comment

Comments

@jaumard
Copy link

jaumard commented Jan 9, 2016

It can be nice to have default Trailpack family, and have a category "default" with Trailpacks retrieve from npm.

Or retrieve all Trailpacks from npm and parse keywords (or put a trailpackCategory field under package.json for trailpack) and show them directly on the right category.

Example :
I make a new web server trailpack, I just have to add trailpackCategory : 'webserver' and it will automatically appear on "Web server" category on TrailsMix.

That can be cool :)

@nogtini
Copy link

nogtini commented Apr 12, 2016

Definitely a cool idea, and I think having these Trailpacks "pre-categorized" will go a long way towards getting a solid mental model of the Trails ecosystem beyond their effectiveness in automating the UI.

We are already diagnosing branding for each "type" of Trailpack, so having each Trailpack type made explicit through its configuration will be very useful as a reference.

@tjwebb

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants