The riff-team-api provides a REST (http) and websocket interface for Riff teams.
Build tool, components, development tools, deployment...
The article by Conroy Whitney makes a very good point (because it supports my thinking going in? :-) ) that organizing by function first, feature second is problematic in the long run, and it is better to organize feature first, function second.
However for the initial pass at this project, I think I will stick with the organization suggested by the feathersjs developers as created by the feathersjs CLI.
Once some actual implementation is working, thought should be given to upending everything and reorganizing before too much code exists and that becomes a herculean task.
Use index.js files ONLY as aggregators, as Conroy Whitney suggests and
put all logic in a file with a more descriptive name.