Separate components from service/features about wpkickstart HOT 3 CLOSED

Per a call with Eric, this structure may work with more modern PHP frameworks:

Eric's point is that service in the PHP community and components also works for the same thing. My pushback was that a "component" should have one class, but the way I'm doing it you could use multiple classes, so we went with component.

Ping #7 and #10

from wpkickstart.

Some notes after talking to Jeremy:

• features is usually a name for testing things in PHP community
• components could also be packages (not as in a name, but as in a concept, and should be installed like so via composer). Note, the structure would allow for it, we would need to get composer to install things there
• Expecting a src/ folder (not sure I would want to do that)
• Directory structure is not deep enough (we're intentionally steering away from deep structures to reduce complexity)

from wpkickstart.

• The official name for "components" can be components/ but maybe make this filterable so someone can name it somethings else?
• The official name for "features" should be services/ but can also be called features/ for backwards compatibility
• The includes/ folder should be renamed to app/ as in #11

So what you end up with is:

• services|features/ (can either name services/ or features/ but services/ is what's right be default)
  • name/ (e.g. migrate-subsite)
    • class-name.php (e.g. class-migrate-subsite.php)
• components/
  • name/ (e.g. cli)
    • class-name.php (e.g. class-cli.php)
• app/
  • class-app.php (always this name for the app() function)

Note some interesting changes w/ Namespace thinking:

• components/ should be namespaced independent of the plugin framework so they can be mobile
  • Document this in the folder that they should be attached by their root namespace or using a use statement in-file
• services/ should be namespaced the same as the rest of the plugin framework

from wpkickstart.