Skip to content

Remove version badge and add store generator guide #12

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Oct 18, 2017
Merged

Remove version badge and add store generator guide #12

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions _app/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# <%= projectName %> [![built with choo v4](https://img.shields.io/badge/built%20with%20choo-v4-ffc3e4.svg?style=flat-square)](https://github.com/yoshuawuyts/choo)
# <%= projectName %>

Choo-cli created a directory structure that [we've found to be optimal](https://yoshuawuyts.gitbooks.io/choo/content/guides/designing-for-reusability.html) for slim
applications and reusability.
Expand All @@ -8,7 +8,7 @@ assets/ images and fonts, if you have any
elements/ standalone application-specific elements
lib/ generalized components, should be moved out of project later
pages/ views that are directly mounted on the router
scripts/ shell scripts, to be interfaced with through `npm scripts`
stores/ stores that are used in pages and elements
client.js main application entry; programmatic manifest file
package.json manifest file
```
Expand All @@ -26,6 +26,11 @@ Elements
$ choo generate element my-element
```

Stores
```bash
$ choo generate store my-store
```

## npm scripts

Choo-cli was made for generating choo projects and code, and leverages npm scripts
Expand Down