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
Scaffolds and cf CLI Meta issue #7
Comments
@nkbt Now that the boilerplates are starting to shape up, are you interested in working on this? |
By all means, always wanted to build one for myself =) |
Great. I've created the Scaffold conventions doc. Feel free to take on the build tooling at your convenience. |
This is looking great so far. I will be a little busy the next couple days but I plan on helping out! |
👍 |
https://twitter.com/sethetter/status/618779021526970368 This is worth calling out. My primary problem with yeoman is the ecosystem signal to noise ratio. It got so bad, when I thought about scaffold solutions and realized we could probably just wrap yeoman, the idea of even having the project associated with yeoman mentally was bad enough it was worth starting from scratch.
I think the answer is that the CLI should have first class search and discovery for curated scaffolds, and no search/discovery for community scaffolds. If people want to search past the cf whitelist, they can use npm search, Google, or GitHub search. We're not yeoman and we're not npm, where you search for needles in a giant haystack. We're a tool for eliminating choices, not adding to them. |
👍 |
@nkbt It's been a while since we saw any activity here. Where are we on turning prod-module-boilerplate into a cf scaffold? |
The base for cf package is merged now, so we can go further... It's been a
pretty busy time anyway :).
|
CLI
cf
which can be installed globally. Packages that depend on it should install it locally as adevDependency
.API
If
cf
is invoked with missing arguments, it should:build
Create a new package from a Cloverfield scaffold. Scaffolds should be cached locally. See Scaffold Conventions
Usage
cf build <scaffold-name>
TODO:
cf
commands. Each command should describe its purpose, usage, each argument, and descriptions for each argument. Those args requirements and descriptions can be used for interactive help.(https://github.com/spion/blue-tape)
cf-package
based on prod-module-boilerplatecf-react-app
based on universal-react-boilerplatecf-react-component
to generate stateless, reusable UI component (needs boilerplate - check out the react-transform-boilerplate for hot reload ideas)The text was updated successfully, but these errors were encountered: