-
Notifications
You must be signed in to change notification settings - Fork 35
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
Milestone
Comments
bajiat
changed the title
Implement reply functionality to communication channel
Design and implement reply functionality to communication channel
Nov 9, 2015
Work ongoing in feature/feedback-discussion branch. |
@apinf/design @apinf/developers please review the issue summary. @kyyberi please also review. I will begin work on this feature soon. |
@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
changed the title
Design and implement reply functionality to communication channel
Design reply functionality to communication channel
Nov 13, 2015
This was referenced Nov 13, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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):
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 documentauthorId
- String - containing the ID of the discussion item Meteor User IDmessage
- String - containing the messagecreatedAt
- Date - the Datetime when the discussion document was createdPublication(s)
The following publication(s) will be useful:
relatedFeedbackDiscussion (feedbackId)
- returns a collection pointer to feedback discussion documents that match the feedbackId parameter:Subscription(s)
The publications will be used as template subscriptions:
relatedFeedbackDiscussion
- will be used on the Feedback template to populate the discussion threadCo-pilot: @frenchbread
The text was updated successfully, but these errors were encountered: