watson-developer-cloud / tone-analyzer-nodejs

Sample Node.js Application for the IBM Tone Analyzer Service
https://tone-analyzer-demo.ng.bluemix.net/
Apache License 2.0
453 stars 273 forks source link

Suggested text changes #67

Closed kcheat closed 8 years ago

kcheat commented 8 years ago

Change top level sentence from this: image to this: Discover and understand how emotions are coming across, the social tendencies that are being expressed, and how your writing style is coming across in your content.

Remove the section under Choose Content (I don't think this is necessary because it is just reiterating the header Choose Content, and it doesn't really need to be clarified): image

Change the content of the Output from: image to this: Use the document level analysis to get a sense of the overall tone of the document, and use the sentence level analysis to identify the strongest tones of specific parts of the content.

Remove the inline help under Document Level and Sentence Level (this is now covered generally under the output): image image

Add inline help sections under Document level Emotion Summary, Language Summary and Social summary:

Remove raw score from the summary headings (does not really express clear info): image


jzhang300 commented 8 years ago

@kcheat @dezzie

Since we removed the Output paragraph altogether in issue #54, I'm thinking we can split the output description ("Use the document level analysis to get a sense of the overall tone of the document, and use the sentence level analysis to identify the strongest tones of specific parts of the content.") into their respective Document-level tone and Sentence-level tone sections.

There was also Document level inline help sections specified in issue #56. The way it's done here has more consistency.

How should we resolve these?

kcheat commented 8 years ago

@jzhang300 splitting it out into their respective Document-level tone and Sentence-level tone sections sounds good to me and I think both proposed methods of document level inline help solve the same issue so I am all for picking whichever one is easier to implement

dezzie commented 8 years ago

Ok, I took at stab at everything but the inline help for the graph headers, which we can do by monday

dezzie commented 8 years ago

closing this issue because it's covered in other issues or we're done editing the overall copy. Last bit that needs to be done are tooltips for graph headers, that issue is here #71