{"action":"created","issue":{"url":"https://api.github.com/repos/royboy789/helium/issues/15","labels_url":"https://api.github.com/repos/royboy789/helium/issues/15/labels{/name}","comments_url":"https://api.github.com/repos/royboy789/helium/issues/15/comments","events_url":"https://api.github.com/repos/royboy789/helium/issues/15/events","html_url":"https://github.com/royboy789/helium/issues/15","id":90743878,"number":15,"title":"De-emphasizing Posts","user":{"login":"ChaseWiseman","id":999301,"avatar_url":"https://avatars.githubusercontent.com/u/999301?v=3","gravatar_id":"","url":"https://api.github.com/users/ChaseWiseman","html_url":"https://github.com/ChaseWiseman","followers_url":"https://api.github.com/users/ChaseWiseman/followers","following_url":"https://api.github.com/users/ChaseWiseman/following{/other_user}","gists_url":"https://api.github.com/users/ChaseWiseman/gists{/gist_id}","starred_url":"https://api.github.com/users/ChaseWiseman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ChaseWiseman/subscriptions","organizations_url":"https://api.github.com/users/ChaseWiseman/orgs","repos_url":"https://api.github.com/users/ChaseWiseman/repos","events_url":"https://api.github.com/users/ChaseWiseman/events{/privacy}","received_events_url":"https://api.github.com/users/ChaseWiseman/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-06-24T17:53:23Z","updated_at":"2015-06-24T17:57:45Z","closed_at":null,"body":"I love what I'm seeing of this project so far. Very exciting!\r\n\r\nI think this would be a great opportunity to eliminate Posts as the central object/content type of WordPress. As most of us know, a lot of core components like pages, nav menus, attachments, etc... are just implementations of the original post component, which makes sense given WordPress' blog platform origins.\r\n\r\nI feel that going forward it would make sense to stick with a more general _Content Type_ or _Content Component_ model, with _Posts_, _Pages_, and _Media_ being optional component implementations."},"comment":{"url":"https://api.github.com/repos/royboy789/helium/issues/comments/114958360","html_url":"https://github.com/royboy789/helium/issues/15#issuecomment-114958360","issue_url":"https://api.github.com/repos/royboy789/helium/issues/15","id":114958360,"user":{"login":"jacobsantos","id":314942,"avatar_url":"https://avatars.githubusercontent.com/u/314942?v=3","gravatar_id":"","url":"https://api.github.com/users/jacobsantos","html_url":"https://github.com/jacobsantos","followers_url":"https://api.github.com/users/jacobsantos/followers","following_url":"https://api.github.com/users/jacobsantos/following{/other_user}","gists_url":"https://api.github.com/users/jacobsantos/gists{/gist_id}","starred_url":"https://api.github.com/users/jacobsantos/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jacobsantos/subscriptions","organizations_url":"https://api.github.com/users/jacobsantos/orgs","repos_url":"https://api.github.com/users/jacobsantos/repos","events_url":"https://api.github.com/users/jacobsantos/events{/privacy}","received_events_url":"https://api.github.com/users/jacobsantos/received_events","type":"User","site_admin":false},"created_at":"2015-06-24T17:57:45Z","updated_at":"2015-06-24T17:57:45Z","body":":+1:\r\n\r\nAs I said with the WP Customizer component. You shouldn't have specialized types that duplicate members across types. You should have a type that has the common members or an implementation that allows arbitrary values that can be used in specialized types.\r\n\r\nMeaning, you have a Content type that Pages, Attachments, etc where it makes sense and use the implementation in that Content type to fulfill the contract of the type requirements.\r\n\r\nThe idea should be to allow growth of types, while using less code and reusing as many components as possible."}}