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

View only items being published verses all campaign items #147

Open
clarkepaul opened this issue Sep 17, 2019 · 0 comments
Open

View only items being published verses all campaign items #147

clarkepaul opened this issue Sep 17, 2019 · 0 comments

Comments

@clarkepaul
Copy link

A campaign can get very large (some get to about 100 pages based on customer feedback), and therefore the campaign gets loaded with linked items like files and blocks. It would be good for the CMS user to be able to view only the items in which will be getting published as part of the campaign or have the ability to view all items in the campaign (as we have now). This will allow users to more easily to review the changes being published and get a better idea of the effect of the campaign to the end customer.

This could be in the form of initially only showing the effected items and being able to "View all pages already published" for each type of thing in the campaign. Another way is to have a view options at the top to say whether you want to view all items or just items which will be published.

This should go through some UX discussions on an approach prior to being developed.

AC

As a CMS user viewing a campaign, I can choose to view all items within a campaign or only view the things which are going to be published, so I have an easier time reviewing and making the call whether to publish or not.

@clarkepaul clarkepaul changed the title Ability to show items getting published verses items which are uneffected View only items being published verses all campaign items Sep 17, 2019
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