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

Design reply functionality to communication channel #541

Closed
bajiat opened this issue Oct 26, 2015 · 3 comments
Closed

Design reply functionality to communication channel #541

bajiat opened this issue Oct 26, 2015 · 3 comments
Assignees
Milestone

Comments

@bajiat
Copy link
Contributor

bajiat commented Oct 26, 2015

First version of communication channel between consumers and managers allows consumers to send feedback, request etc. about APIs and managers to view the feedback.

User Interface

The discussions will appear within the feedback container, as a flat list at the bottom (threaded replies may be added later). The discussion will be date sorted.

Comment input

There will be an text input for adding a reply, which can later be refactored to show a modal dialogue or similar.

Comment display

Once comments are submitted, they will be displayed in a card-like frame, with the comment, user name, user photo, and timestamp (in time-ago format):

Feedback Comments UI

Design example(s)

The following designs may be freely adapted for our purposes:

Collection

The feedback discussion will be stored in a separate collection, called FeedbackDiscussion.

Schema

The FeedbackDiscussion collection will have the following schema:

  • feedbackId - String - containing the ID of the related feedback document
  • authorId - String - containing the ID of the discussion item Meteor User ID
  • message - String - containing the message
  • createdAt - Date - the Datetime when the discussion document was created

Publication(s)

The following publication(s) will be useful:

  • relatedFeedbackDiscussion (feedbackId) - returns a collection pointer to feedback discussion documents that match the feedbackId parameter:
FeedbackDiscussion.find({feedbackId: feedbackId});

Subscription(s)

The publications will be used as template subscriptions:

  • relatedFeedbackDiscussion - will be used on the Feedback template to populate the discussion thread

Co-pilot: @frenchbread

@bajiat bajiat added the MVP2 label Oct 26, 2015
@brylie brylie self-assigned this Oct 26, 2015
@brylie brylie added this to the Sprint 15 milestone Oct 26, 2015
@brylie brylie added ready and removed planning labels Oct 26, 2015
@bajiat bajiat added planning and removed ready labels Nov 5, 2015
@bajiat bajiat changed the title Implement reply functionality to communication channel Design and implement reply functionality to communication channel Nov 9, 2015
@brylie brylie added ready and removed planning labels Nov 9, 2015
@bajiat bajiat modified the milestones: Sprint 16, Sprint 15 Nov 9, 2015
@brylie
Copy link
Contributor

brylie commented Nov 12, 2015

Work ongoing in feature/feedback-discussion branch.

@brylie
Copy link
Contributor

brylie commented Nov 12, 2015

@apinf/design @apinf/developers please review the issue summary. @kyyberi please also review. I will begin work on this feature soon.

@brylie brylie added in progress and removed ready labels Nov 12, 2015
@bajiat
Copy link
Contributor Author

bajiat commented Nov 13, 2015

@brylie Would it be possible to have a wireframe sketch to show how you are planning to combine / reuse the available designs you have found?

@bajiat bajiat changed the title Design and implement reply functionality to communication channel Design reply functionality to communication channel Nov 13, 2015
@bajiat bajiat closed this as completed Nov 19, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants