Unique publication instance #168
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I won't have time to work on this, feel free to pick it back up. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Just want to record the fruit of our session last week with @blishen @akash1810 @jonathonherbert and @JustinPinner
We adopt a "forking" model:
a piece of content can only belong to one platform: this is because changes in the article made for that platform (which happens more often that not) cannot be reflected in the other instances. This is both true when a fork is for another platform or for the same platform as a reissue.
in reflection, adding platform-specific annotations and content can quickly make the UI very complex and hard to understand and pushing that complexity "upwards" seems like a more realistic approach at the beginning: it is far easier to add a "fork/switch" UI.
at the moment we don't track parent/child/sibling relationships in CAPI, but this can easily be added if necessary.