Skip to content
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.

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

Setup how data will be stored #5

Open
aubreypwd opened this issue Feb 5, 2017 · 1 comment
Open

Setup how data will be stored #5

aubreypwd opened this issue Feb 5, 2017 · 1 comment
Milestone

Comments

@aubreypwd
Copy link
Collaborator

aubreypwd commented Feb 5, 2017

Pending #6


  • Lists (with an initial list)
  • List items + data
@aubreypwd aubreypwd self-assigned this Feb 5, 2017
@aubreypwd aubreypwd added the BED label Feb 5, 2017
@aubreypwd aubreypwd added this to the 1.0 milestone Feb 5, 2017
@aubreypwd
Copy link
Collaborator Author

Should we use CPT's?

Pros

  1. WP_Query
  2. Post Meta easy to use
  3. Functions all around
  4. Ability to have non-UI management in the future
  5. Have a UI for CRUD
  6. Import/Export
  7. Easy to work on w/ Developers
  8. Don't have to design/re-design tables/$wpdb

Cons

  1. Slow ¯_(ツ)_/¯
  2. Have to clean up Admin (e.g. not show menu items, disable editing, etc)
  3. Not a post, not published data (need to lock down, but easy to do)
  4. Possibly hundreds of todos in lists, possibly hundreds of lists, how does that impact WP_Query?
  5. Easy for other plugins to poll data (is this a con?)

@efuller #4 in cons was really interesting. Do you think your app would paginate at all?

@aubreypwd aubreypwd removed their assignment Aug 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant