Our Hoping to Accomplish List

Nobody has claimed this yet.

Migrated from the new skeleton's README to here, since these are things I think we'd ideally like to be able to `composer install` into any of our 3.0 projects.
- [ ] auto test running
- [ ] auto code sniffing
- [ ] auto builds
- [ ] auto deploy to stage
- [ ] one-click code rollback

Some of this may necessitate the creation of a different repo from the CakePHP-Shell-Scripts project. Some of these things (if they mean what I think they mean) are stuff we used to accomplish with grunt. We either need to move the existing Gruntfile, package.json and associated node scripts into the new skeleton and tweak(/improve) as necessary to fulfill some of the goals, or develop an alternative approach.

Personally, I'd like to not necessarily _need_ the node+npm+grunt stack. Instead I think we could use Cake Shells for some of this, and use a stand alone "watcher" program like [kicker](https://github.com/alloy/kicker) to execute them on file change. That may be more tooling that we want to rewrite at the moment though...

The last few are going to require coordination on the production hosting end of things too and may be more long term goals, but I'd love to pursue them.

To this list I would add:
- [ ] auto-publishing code coverage reports.
- [ ] auto-publishing generated documentation.

_(I actually wrote a tool for this that remains completely untested currently: [beporter/docs-manager](https://github.com/beporter/docs-manager).)_ See also: #56

This is a broad roadmap rather than a single implementation task. Start by reviewing the existing Gruntfile, package.json, associated node scripts, and the referenced #56 issue; the listed goals also require production-hosting coordination. Done requires breaking the wishlist into scoped tasks with an agreed approach for testing, builds, deployment, rollback, coverage, and documentation publishing.

Written by the indexing model from the issue text.