Skip to content
This repository has been archived by the owner on Nov 2, 2020. It is now read-only.

Re-work to be component/feature organized #7

Closed
aubreypwd opened this issue Aug 21, 2018 · 3 comments
Closed

Re-work to be component/feature organized #7

aubreypwd opened this issue Aug 21, 2018 · 3 comments

Comments

@aubreypwd
Copy link
Owner

This was an idea given to me by a coworker, e.g.:

  • feature-name/
    • assets/
      • js/
      • css/
    • class-feature-name.php
    • vendor/

The idea is that the folder feature-name could be moved around to other plugins using this same platform. E.g. bug-spray could be easily added to another project just by copying the folder (which has all it's things) to the plugin on another projects and loaded into the class-app.php and run it's hooks/etc.

Maybe hooks could be auto loaded now which would do all the things.

@aubreypwd aubreypwd added this to the 2.0.0 milestone Feb 1, 2019
@aubreypwd aubreypwd changed the title Re-work to be component organized. Re-work to be component/feature organized Feb 1, 2019
@aubreypwd
Copy link
Owner Author

Let's also name the folder components/ instead of features/ (but also allow features/ for backwards compatibility).

@aubreypwd
Copy link
Owner Author

See #13

@aubreypwd
Copy link
Owner Author

Marking as dup of better #13

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant