Discovery - Spanish - Policy Pages
https://www.edx.org/es/edx-terms-service [1 point]
https://www.edx.org/es/edx-privacy-policy [3 points]
https://www.edx.org/accessibility [2 points]
Discovery Acceptance Criteria
Confirm technical direction and create a story (or set of stories) to capture the following ACs:
VERIFY the learner is able to view the Privacy, T&C and Accessibility Policies in Spanish, when s/he has set their language preferences in Spanish.
VERIFY the learner sees the Spanish version regardless of language pref selection method (spanish URL, anonymous cookie, logged in language pref).
VERIFY the learner is shown the Spanish versions of these pages, regardless of where they access these pages. E.g. via:
learner clicks on the links in the footer (mktg & lms)
learner clicks on the links in an email
learner clicks on the links in the registration page
learner clicks on the links in the help submission form.
Note: all of these use cases should direct link to spanish content, but will redirect as other pages do today if spanish is detected.
We should move all 3 of these pages into React
Should be relatively easy to port since it's just content.
Additional work required to remove the existing policy page and setup appropriate redirects
Clean up all Drupal remnants
A11y policy is a backbone page
TOS is a React page
Get the existing translations for these pages and verify that gettext is the best solution.
Thank you Alasdair!
On Mon, Mar 5, 2018 at 2:09 PM, Alasdair Swan (Jira) <
usually just by adding "Discovery" to the title & updating the "Discovery ACs" to capture: 1) discovery work needed and 2) output of the actual implementation story/stories, with clarified ACs.
I just did that for this ticket. How does it look? Are we ready to add a point value & bring this discovery story into our sprint?
yes, how do you convert a story to a discovery story?
Hi I've attached the three translations! Are we converting this story to a discovery story, to confirm technical direction?