| Multiexcerpt include macro | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Excerpt |
|---|
With Linked Project Spaces, administrators can safely and efficiently push content from a source project space to multiple other project spaces. This approach is particularly useful for complex content that requires frequent updates and rigorous testing to quality and effectiveness. With the detailed exception-handling process, the overall result is a more efficient and streamlined process for pushing and syncing content while maintaining project safety and integrityan “upstream” project space is identified where all original development work takes place, including the source application and data models. By linking project spaces, you can push this to downstream project spaces where users access this released content. |
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
The first step in using linked project spaces is establishing relationships between an upstream project space and one or many downstream project spaces. Please see below for understanding what these terms mean. With Linked Project Spaces, an “upstream” project space is identified where all original development work takes place, including the source application and data models. By linking project spaces, you can push this to downstream project spaces where users access this released content.
Terminology
An upstream project space is the development environment where the master applications and data models are created. These upstream project spaces are linked to downstream project spaces. When the development work in the upstream project space is complete, the content is transferred or pushed to downstream project spaces for release.
...