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

Content Creator: CMS User Experience #245

Open
joshkimmell opened this issue Aug 11, 2016 · 6 comments
Open

Content Creator: CMS User Experience #245

joshkimmell opened this issue Aug 11, 2016 · 6 comments
Labels

Comments

@joshkimmell
Copy link

joshkimmell commented Aug 11, 2016

As a Content Creator, I will have an intuitive user experience, so that I can successfully manage my content.


Stories to create

General - Nick

  • Wayfinding
    • Let user know they are logged in (display name in header) #217
    • Make sure user knows what page/section they are on (breadcrumbs, affordance on main nav) #95 + #219
  • Messaging (alerts around content related to user) #171 + #172
  • First time user experience (what do I do?) #237
  • Display user name of content creator/editor on all content #234
  • Date format could be more human readable (Thu Jul 28 2016 20:12) #239
  • Should we be more specific for the "Date" column? Maybe "Last edited" or something. #239
  • Search Content Creator: Search #291 [EPIC]

Login - Nick

  • Forgot password #148
  • Receive an email when I am added to Punchcard #149 + #167
  • Request access #206 + #207
  • Failed login (no error message) #225

Create content - Nick

  • Content types list (provide more context and allows users to perform their tasks from this screen. what could the user do here, without having to drill down another level) Content Creator: Understand content types and take action #249
  • Content form
    • What should the hierarchy be on this page? Currently, the main form and the sunrise/sunset portion share equal weight. Is that right? What happens with more complex content types.
    • What fields are required? Need some visual affordance. Content Creator: Visual affordance for required fields #271
    • Discuss + explore: Save vs Save and continue (autosave) vs Ready to publish (publish could happen here as well as the revisions list view)
  • What happens to content once it goes into the approval workflow? Does it lock? Can you pull that content back?
  • Where can you see a list of all the content you are currently working on? (dashboard?) #228
  • Do we need a place to comment when users create/edit of content? #232
  • Add character limits on form elements #193

Edit content - Nick

Archive content - Nick

Revisions - Miranda

  • Discuss the locking content on content: Dev story - #170; user story - #304
  • How can the revision history / conversation not get lost when you make a new revision? #223
  • What happens when something is approved, does that content and all the revisions for it change in some way? Can you still edit it? Does that become a new "revision" or a new piece of content? #170 - needs more stories
  • If you create a revision but make no edits - should the save and publish option not be available? - seems to be related to issue #221 - where it addresses saving a revision, sending a revision into a workflow or canceling the creation of a revision.
  • - [ ] When you create a new revision, what revision of the content does it use? (uses latest version)
  • DIFF - compare revisions and edits in content (like GitHub does) - also listed under Approval section #224
  • A way to recall a submission for approval #230
  • Saving a revision without sending into workflow #221

Approval - Miranda

  • The approve screen needs some work. Discuss having a way to display the "diff" between what was already there and what was changed. Content creator diff: #224 for diff; Editor/Approver UI + Diff #233
  • Approval actions: Approve / Reject - is that the only actions we need? "Request revisions"? "Comment"? #233 - Connected this to the approval screen/UI issue Editor/Approver: Interface for reviewing/approving content #233.
  • As an approver or content creator, how do you know if there is a change to your content? (dashboard? notifications?) Content creator: #171 Approver/editor: #172
  • If a piece of content is waiting for approval, can you notify the "approver" again? (send reminder) #235
  • Need an approval log or area for approvers to approve and review items - connected to #233
  • Need a way to keep track of comments across multiple revisions - see issue created for Content Creator #223

Users - Miranda

  • Send email to new users that are created - Core Developer Issue #149
  • Users shouldn't be able to edit themselves #163 - might need to update this story with this issue, though Scott's story seems to touch upon it already
  • How are the roles defined & created? - May need to add to this user admin issue #163
  • How does a user know what role is best for that user? Can we display what each role does? Maybe can link or flesh out #163
  • Username of item creator should show up in content list so everyone can see who created what item - linking to existing story about displaying content creator's email - could potentially be one and the same, or added to that issue #234
  • Edit + Delete current don't work (bug) #166
  • Will users from different teams exist in different orgs/groups/depts within the CMS?
  • What types of content will users from different teams be able to see? Will all users be able to see everything?
  • Allow users to change their own passwords #247
@joshkimmell joshkimmell changed the title Watson Designer: UX Stories Designer: UX Stories Aug 11, 2016
@joshkimmell joshkimmell changed the title Designer: UX Stories Content Creator: CMS User Experience Aug 11, 2016
@joshkimmell joshkimmell removed the stub label Aug 15, 2016
@ineedsubstance
Copy link
Contributor

@joshkimmell I think you added this, but I'm not sure what it means.

screen shot 2016-08-16 at 11 11 10 am

@joshkimmell
Copy link
Author

It means we need the ability to "delete" a piece of content, from the user's perspective.

@ineedsubstance
Copy link
Contributor

Wouldn't sunset accomplish this?

@joshkimmell
Copy link
Author

no... it will still remain in the list of content. For instance, Conversation and Watson Conversation API... which one is the right one? Allen wrote one and I wrote the other. I guess a temporary solution would be to title it something like "Conversation - DO NOT USE", but the list will get long and cluttered. The story doesn't need to say "Archive".

@ineedsubstance
Copy link
Contributor

ok, so you are saying delete it for the content creator. got it. thanks.

@ineedsubstance
Copy link
Contributor

ineedsubstance commented Aug 16, 2016

I will flesh out that story. Seems like something we would only want certain users to be able to do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants