component-app-seed

[Amjad Masad]

I've been hacking on a few small component apps recently and I use this repo as my starting template. I've noticed some confusion about structuring apps using component on this forum, so in addition to the repo I wrote a small guide in the Readme to get started. There are also links to example apps towards the end.

Let me know if something looks wrong or could be better.

[Amir Abu Shareb]

that's awesome! you might want to implement that as a command instead, so you can do `$ component seed`

[Amjad Masad]

oh this would be much easier use, thanks amir!

--
You received this message because you are subscribed to the Google Groups "component" group.
To unsubscribe from this group and stop receiving emails from it, send an email to componentjs...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Jonathan Ong]

that `component create -l` thing is cool. 

should we officially support structuring putting all your locals in a single folder? i think most of us do this anyways, and to me this is one of the biggest benefits of component (versus the actual package manager stuff, which is meh to me). it would also improve the learning curve

ex doing `component create -l boot` should create a `boot` component in the first path in `/component.json`. 

[Amjad Masad]

that `component create -l` thing is cool. 

should we officially support structuring putting all your locals in a single folder? i think most of us do this anyways, and to me this is one of the biggest benefits of component (versus the actual package manager stuff, which is meh to me). 

agreed, in addition to the package management, the ability to manage my own code and break up my app into components (made up of js, css, html) is one of the main reasons I started using component.

it would also improve the learning curve

the hardest thing to learn starting out is how to create my app and what's the best workflow. component.io repo was helpful but it does some weird things.

ex doing `component create -l boot` should create a `boot` component in the first path in `/component.json`. 

I think it makes sense. But you'd want it to be opt-out

[Jonathan Ong]

yeah, i'm assuming you don't specify a folder like lib/boot. but then that might be too much magic since you won't be able to do `component create -l boot` and create a boot folder in the top folder (why would you want that?)

[Ian Storm Taylor]

i think i’d rather have it be simple and modular and just have a `component create` just create a component file. if we wanted, `—private` could give you useful private defaults. and then you can just cd in `/lib` instead of it guessing a path