{"action":"created","issue":{"url":"https://api.github.com/repos/deconst/deconst-docs/issues/46","labels_url":"https://api.github.com/repos/deconst/deconst-docs/issues/46/labels{/name}","comments_url":"https://api.github.com/repos/deconst/deconst-docs/issues/46/comments","events_url":"https://api.github.com/repos/deconst/deconst-docs/issues/46/events","html_url":"https://github.com/deconst/deconst-docs/issues/46","id":70439987,"number":46,"title":"Support Private, Public/Private, and Public content types","user":{"login":"kenperkins","id":730664,"avatar_url":"https://avatars.githubusercontent.com/u/730664?v=3","gravatar_id":"","url":"https://api.github.com/users/kenperkins","html_url":"https://github.com/kenperkins","followers_url":"https://api.github.com/users/kenperkins/followers","following_url":"https://api.github.com/users/kenperkins/following{/other_user}","gists_url":"https://api.github.com/users/kenperkins/gists{/gist_id}","starred_url":"https://api.github.com/users/kenperkins/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kenperkins/subscriptions","organizations_url":"https://api.github.com/users/kenperkins/orgs","repos_url":"https://api.github.com/users/kenperkins/repos","events_url":"https://api.github.com/users/kenperkins/events{/privacy}","received_events_url":"https://api.github.com/users/kenperkins/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/deconst/deconst-docs/labels/discussion","name":"discussion","color":"009800"},{"url":"https://api.github.com/repos/deconst/deconst-docs/labels/feature","name":"feature","color":"207de5"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-04-23T15:23:32Z","updated_at":"2015-04-24T18:49:01Z","closed_at":null,"body":"Invariably, there are a few types of content that we need to support. To set context, there are 3 known types of content:\r\n\r\n- Entirely public content\r\n- Entirely private content\r\n- Content with interleaved public and private content\r\n\r\nBoth of the entirely public and private content types are relatively straight-forward. The Interleaved content is a bit more challenging. Common use cases for this kind of document might include being able to annotate the documentation for internal support users.\r\n\r\nRegardless of feature changes to support the above, there's an orthogonal question about whether we should be single or multi instance for nexus, in both the production systems, but also for multiple environments on the same instance.\r\n\r\nIdeally, all of the discrimination of whether a piece of content is public, private, or public/private should come from the preparer to eliminate complexity from deconst proper from having to filter.\r\n\r\nFor example, if a piece of content is public/private at the content source layer, the preparer for that content should be able to POST the public/private version to either a standalone instance of deconst, or POST it to the current instance with a flag. The preparer might then filter out the private content, and POST another copy of the content to the public instance (or with a flag for public content).\r\n\r\nDoing all of this filtering/discriminating at the preparer level keeps the logic within the content service simpler.\r\n\r\nThoughts?"},"comment":{"url":"https://api.github.com/repos/deconst/deconst-docs/issues/comments/96032495","html_url":"https://github.com/deconst/deconst-docs/issues/46#issuecomment-96032495","issue_url":"https://api.github.com/repos/deconst/deconst-docs/issues/46","id":96032495,"user":{"login":"kenperkins","id":730664,"avatar_url":"https://avatars.githubusercontent.com/u/730664?v=3","gravatar_id":"","url":"https://api.github.com/users/kenperkins","html_url":"https://github.com/kenperkins","followers_url":"https://api.github.com/users/kenperkins/followers","following_url":"https://api.github.com/users/kenperkins/following{/other_user}","gists_url":"https://api.github.com/users/kenperkins/gists{/gist_id}","starred_url":"https://api.github.com/users/kenperkins/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kenperkins/subscriptions","organizations_url":"https://api.github.com/users/kenperkins/orgs","repos_url":"https://api.github.com/users/kenperkins/repos","events_url":"https://api.github.com/users/kenperkins/events{/privacy}","received_events_url":"https://api.github.com/users/kenperkins/received_events","type":"User","site_admin":false},"created_at":"2015-04-24T18:49:01Z","updated_at":"2015-04-24T18:49:01Z","body":"So I talked with @steveortiz some more about this topic, and we're both convinced that separate deployments are the safer way to go, at least for now.\r\n\r\nA big motivator is that fact that we'll have to have separate deployments of nexus for staging environments, so why not make internal just another deployment."}}