-
Notifications
You must be signed in to change notification settings - Fork 1
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
[Transferred from Web repo] Update to strings on Oppia.org (Learner Pages) #157
Comments
Hi @SanjaySajuJacob, thanks for proposing this as a good first issue. I am removing the label for now and looping in @DubeySandeep to approve the label. It will be added back if approved. Thanks! |
Hi Team, I would like to fix this issue. Please assign this issue to me. |
Hey, I would like to work on this. Kindly assign me to this issue. |
@seanlip is the fixes for curated lessons fine? |
For technical contributors: this needs some clarification from the UX Writing team first. Please don't start working on it yet. @danapj thanks for filing the issue! Some questions of clarification:
Please let me know if you need clarification on any of the above questions. Thanks! |
@hemantmm Yup I moved it to a different project since this is mostly content fixes and not technical. |
@seanlip ok thank you for the information |
Hi @seanlip, is this on the UXW board for us to review the strings, including your comment from 2.10.2023? |
Hm, I think this issue got orphaned and I added it here because I was trying to clean up all the orphaned issues and assign them to projects. I believe that this issue was originally part of a website audit. I'd say it's up to you whether you want the dev team to proceed with these changes (in which case they might benefit from some clarification), or close this in favour of a subsequent full audit. |
@seanlip I think it's worth tackling this early! It could be good prep for the audit. I'll assign a writer to look into this! |
Hi @seanlip @tamiorendain, here's the first draft for the updated strings. If I remember correctly, Tami, you mentioned there being some crossover with other tickets/UX writers. Let me know if these requests need to be done alongside other projects.
Heading: Body:
Heading: Body: CTA
Heading: Body: Revision: This course teaches the basic building blocks of math. Each topic builds on the last, starting with simple topics, then progressing to more advanced lessons. Start at the beginning or dive into a specific topic! Heading: Body:
Heading: Body: Search icon: Help text:
Body:
Body:
Body:
Body:
Body: Tables, justification, and screenshots can be found here for further context: |
Thanks @davishedrick! I took a look and I think the changes are along the right lines, particularly the platform-level ones. For the topic content, note that there is a 240-character limit on descriptions (so e.g. the Percentages one is now too long). I made some of the updates:
Re next steps, I think what I'd suggest is making updates as needed and going through the revisions with @tamiorendain. Once everything looks good to both of you, I can start looking into how to get these applied to the site (some may be direct fixes and some may involve filing issues on the tech team's GitHub). Thanks a lot for taking a look into this, appreciate it! |
Hi @davishedrick and @seanlip, just took a look and will leave suggestions here! Let me know what you think. @davishedrick great job on these! Most of my suggestions are for simplicity or to integrate the character limits. Let me know what you think of the thoughts and suggestions below. Questions for @seanlip - can we clarify terminology on this page? So far, I'm seeing:
THOUGHTS AND SUGGESTIONS:
|
@tamiorendain These additions are great, thanks! Good catch on the sentence fragment @seanlip. My only question is what the "*" is used to denote here and if it's intended to be user-facing. |
@davishedrick As I mentioned in the meeting, the asterisks mean nothing - they are a formatting error LOL. I've removed them! I think this is ready to go @seanlip! Unless anything else is needed, I'm marking it done on our end |
Sorry for the late reply on this.
The structure for course/topic is correct. Internally we have also referred to a "course" as a "classroom" or "subject". I'm open to better names for all of these. Does UXW want to weigh in on that? One note is that it would be nice to keep "Topic" if possible since that term is being used all over the place, but it would be great to understand what you all think. The term "course", on the other hand, can easily be changed. Each topic (like Fractions) has lessons and practice questions. The lessons typically combine to form a story, which is why they are also called chapters. For example, the Place Values topic has 5 lessons, which combine to form the story about Jaime: https://www.oppia.org/learn/math/place-values/story. The community library is actually a lesson library, not a topic library. Each card on that page leads to a single lesson. A topic, on the other hand, is represented by a page like this: https://www.oppia.org/learn/math/place-values/story -- and includes lessons, practice questions, and revision cards / study guides. This is not the case for the links on the community library. I hope this clarifies, but please let me know if you have any questions about the above @tamiorendain and @davishedrick. Could you also please confirm whether this affect any of the copy in this comment? |
Some additional thoughts about the copy:
Also, I have updated points 5-10 on the website (note: I think in point 5 that "subjection" should be "subtraction"). So in subsequent comments feel free to omit those -- thanks! |
Ahh good insight @seanlip. I think we should keep the terminology as it is for now, but I'd love to have a wider UXW conversation about terminology (and this falls nicely in line with our goal to create a terminology library) That being said, let's continue with:
cc: @davishedrick for visibility! |
Thanks @tamiorendain! Couple questions about the most recent versions: For point 3, re the last sentence, is it better to keep it in or omit it? Tech team can do either so I would defer to UXW to make the call here. For point 4, I just realized, unlike all the other topics, that it's not actually clear at the outset what this topic teaches. Is it possible to change the content (not just style) of the blurb to give students a better understanding/example of what they will actually be able to do after completing the corresponding lessons, similar to the other ones? Applying discounts or calculating profits would probably be common examples, but feel free to use others as well. |
@seanlip There is only so much we can do to simplify the concept of percentages. I think "parts of a whole" is clearer. The phrasing here is simpler: "parts of something," but it comes at the cost of being more vague. Ill defer to you and Tami on the final phrasing. Additionally, while not as specific as "applying discounts or calculating profits" these examples: "managing money, calculating scores, and tracking progress," show the application without tying down the concept of percentages to a specific domain (managing money). |
A percentage describes a small part of a bigger amount, like how many questions you answer correctly on an exam. You might use percentages when managing money or tracking progress. In this topic, you'll learn how to apply percentages to real-life situations and how to convert them into fractions and decimals. |
@tamiorendain Thanks, the new suggestion for percentages looks good, but it exceeds the length limit of 240 characters! Possible to make it shorter? |
@seanlip @tamiorendain What about: A percentage describes a small part of a bigger amount, like how many questions you answer correctly on an exam. They're useful for managing money or tracking progress. Learn to apply percentages in real life and convert them into fractions or decimals. |
Handed to PM! |
Hi @davishedrick and @tamiorendain, that text is 253 characters. There's a limit of 240 though. I've moved this back to "In Progress" since the above makes it not implementable yet. |
Oh wow, apologies @seanlip. I fed it to chatgpt to check, probably not the best idea. Here's an updated version. It's below 240 I promise. A percentage describes a small part of a larger amount, like how many questions you answer correctly on an exam. Learn to convert them into fractions or decimals and use them in real life, such as managing money or tracking progress. CC: 233 |
Thank you @davishedrick, handing back to PM |
Thanks! Made the changes. Also applied some small edits: "A percentage describes a part of a larger amount, like how many questions you answer correctly on an exam. Learn to convert them into fractions or decimals and use them in real life, such as when managing money or tracking progress." (added "when" near the end, and dropped "small" because that suggests the student doesn't answer many questions correctly on the exam :P ) I have one final question though. In the other topic descriptions, the tone used is more "inviting" -- e.g. see #157 (comment), all of them are like "In this topic, you will learn how to do X". For Percentages, it's more like a command: "Learn how to do X.", so that stands out a bit when compared to the others. Wanted to check if that difference is intentional? If not then should we find a way to standardize them? Thanks! Also listing the final updates here in a single place for easy reference for when I file the dev issue:
|
@seanlip you're right to point out that the more standardized these course descriptions are, the better. However, the reason percentages opens with "Learn how to..." instead of "In this topic, you'll learn how to" was purely a determination based on character count. I think using the precious character count to focus on what the percentages lesson content will be is better than making sure we are consistent on phrasing. That being said, I took another stab at it and here's what I came up with: A percentage represents a small part of a larger amount, like the questions you get right on a test. In this topic, you'll learn to convert them into fractions or decimals and use them in real life, like managing money or tracking progress. With all of the back and forth on this specific description, I don't think we're gonna get much better than this. Let me know what you think. |
Thanks @davishedrick -- good point re the character count. I think it's OK to keep the previous one, since "use them in real life, like managing money or tracking progress" sounds a bit off to me. I have made the updates! |
**Describe the Issue **
This issue is being filed on behalf of the UX writing team to update some of the strings on select pages of the site (learner facing pages).
1 / Dropdown on the navbar


- Change "Ways to learn more" to "Community Library"2/ Page: https://www.oppia.org/learn/math


- Text above the search bar -- Change it to "Explore more lessons in our Community Library." - Can we remove the green search icon on the right? There's no need to have two.3 / Page: https://www.oppia.org/learn/math/addition-subtraction/story

4 / Page: https://www.oppia.org/learn/math/multiplication/story

5 / Page: https://www.oppia.org/learn/math/division/story

6 / Page: https://www.oppia.org/learn/math/exprs-and-eqns/story

7 / Page: https://www.oppia.org/learn/math/fractions/story

8 / Page: https://www.oppia.org/learn/math/ratios/story

9 / Page: https://www.oppia.org/learn/math/percentages/story

Thanks! Let me know if there are any clarifications.
The text was updated successfully, but these errors were encountered: