agaric/agaric-coop
10
1
Fork 0
Code Issues 102 Pull requests Projects Releases Packages Wiki Activity

A site visitor can view pages translated into Spanish. #160

New issue
Open
opened 2019-01-03 15:57:52 +00:00 by mlncn · 24 comments
mlncn commented 2019-01-03 15:57:52 +00:00 (Migrated from gitlab.com)
Copy link

Acceptance Criteria

Given that I am a site visitor,
when I visit a page that has a Spanish translation,
then I ...

Given that I am a site visitor,
when I view the footer I see linked text stating "Navegue agaric.coop en español."
then when I click the link I am taken to the Spanish version of the website.

Pages to translate:

Note that we can also translate parts of our LinkedIn profile into Spanish, likely making us much more discoverable: https://www.linkedin.com/company/2220527/admin/?edit=true

Work remaining

  • Enable multilingual in Drupal 8 / Drutopia
  • Write the translations
  • Commit multilingual configuration to code
  • Restore Services translation
  • Review the translations
  • Adopt policy/plan to keep translations up-to-date
## Acceptance Criteria Given that I am a site visitor, when I visit a page that has a Spanish translation, then I ... Given that I am a site visitor, when I view the footer I see linked text stating "Navegue agaric.coop en español." then when I click the link I am taken to the Spanish version of the website. Pages to translate: * https://agaric.coop/about * https://agaric.coop/services * https://agaric.coop/training Note that we can also translate parts of our LinkedIn profile into Spanish, likely making us much more discoverable: https://www.linkedin.com/company/2220527/admin/?edit=true ## Work remaining * [x] Enable multilingual in Drupal 8 / Drutopia * [x] Write the translations * [ ] Commit multilingual configuration to code * [ ] Restore Services translation * [ ] Review the translations * [ ] Adopt policy/plan to keep translations up-to-date
mlncn commented 2019-01-04 14:17:42 +00:00 (Migrated from gitlab.com)
Copy link

We can also get listed on Planeta Latinoamericano - https://www.drupal.org/planeta - for when we write a blog post en español.

We can also get listed on Planeta Latinoamericano - https://www.drupal.org/planeta - for when we write a blog post *en español*.
mlncn commented 2019-01-07 14:53:53 +00:00 (Migrated from gitlab.com)
Copy link

@freudenberg has offered to translate to German also after we do that.

@freudenberg has offered to translate to German also after we do that.
mlncn commented 2019-01-18 04:53:16 +00:00 (Migrated from gitlab.com)
Copy link

@gnuget minor question, but shouldn't fields like these be translatable?

config/sync/field.field.node.case_study.field_summary.yml  
config/sync/field.field.node.people.field_summary.yml  
config/sync/field.field.comment.comment.comment_body.yml
@gnuget minor question, but shouldn't fields like these be translatable? ``` config/sync/field.field.node.case_study.field_summary.yml config/sync/field.field.node.people.field_summary.yml config/sync/field.field.comment.comment.comment_body.yml ```
mlncn commented 2019-01-18 07:05:17 +00:00 (Migrated from gitlab.com)
Copy link

I agree with David that when there's only one language you can switch to, it makes sense to show the language you can switch to. Unfortunately, no one else is taking that approach in the navigation menu (when placed there, it's a dropdown starting with the current language).

And it just looks weird undistinguished in the menu, especially when it comes first:

menu-translation-agaric

(Plus there's the bug of it showing on the child menu.)

My recommendation is that we make sure automatic language negotiation is working, and banish the language switch to the footer, at least until we have a lot more stuff translated.

Can be a sentence in the footer like this (but proper spanish, maybe cambie a español?):

"Navegue agaric.coop en español."

Relevant UX research/opinion

Translating menu items

@gnuget could you document the next steps, in particular how to translate menu items? Is that config or content or 'it depends'

I agree with David that when there's only one language you can switch to, it makes sense to show *the language you can switch to*. Unfortunately, no one else is taking that approach in the navigation menu (when placed there, it's a dropdown starting with the current language). And it just looks weird undistinguished in the menu, especially when it comes first: ![menu-translation-agaric](/uploads/adb4b35cd102653fed8f3f057daf4f63/menu-translation-agaric.png) (Plus there's the bug of it showing on the child menu.) My recommendation is that we make sure automatic language negotiation is working, and banish the language switch to the footer, at least until we have a lot more stuff translated. Can be a sentence in the footer like this (but proper spanish, maybe cambie a español?): "Navegue agaric.coop en español." ## Relevant UX research/opinion * http://www.flagsarenotlanguages.com/blog/best-practice-for-presenting-languages/ * ![ScreenshotABNAMROBank-langage-switcher](/uploads/e8b32256d48313cc2169f8098f826334/ScreenshotABNAMROBank-langage-switcher.png)(via [ux.stackexchange](https://ux.stackexchange.com/questions/54813/what-is-the-best-way-to-display-language-changing-option)) * Write language names in the language, https://ux.stackexchange.com/a/37020/96595 * Users able to find language links in footers, https://ux.stackexchange.com/a/93226/96595 ## Translating menu items @gnuget could you document the next steps, in particular how to translate menu items? Is that config or content or 'it depends'
gnuget commented 2019-01-18 16:43:33 +00:00 (Migrated from gitlab.com)
Copy link

@gnuget minor question, but shouldn't fields like these be translatable?

I think so, but I just focused on what I was going to translate (the blog posts), but yes we can start marking other things as we need them.

My recommendation is that we make sure automatic language negotiation is working, and banish the language switch to the footer, at least until we have a lot more stuff translated.

Ok.

@gnuget could you document the next steps, in particular how to translate menu items? Is that config or content or 'it depends'

Ok

> @gnuget minor question, but shouldn't fields like these be translatable? I think so, but I just focused on what I was going to translate (the blog posts), but yes we can start marking other things as we need them. > My recommendation is that we make sure automatic language negotiation is working, and banish the language switch to the footer, at least until we have a lot more stuff translated. Ok. > @gnuget could you document the next steps, in particular how to translate menu items? Is that config or content or 'it depends' Ok
cedewey commented 2019-01-25 18:09:30 +00:00 (Migrated from gitlab.com)
Copy link

assigned to @cedewey

assigned to @cedewey
cedewey commented 2019-01-25 18:18:02 +00:00 (Migrated from gitlab.com)
Copy link

changed title from {-Translate key pages of the site into Spanish-} to {+A site visitor can view pages translated into Spanish.+}

changed title from **{-Translate key pages of the site into Spanish-}** to **{+A site visitor can view pages translated into Spanish.+}**
cedewey commented 2019-01-25 18:18:02 +00:00 (Migrated from gitlab.com)
Copy link

changed the description

changed the description
cedewey commented 2019-01-25 18:18:18 +00:00 (Migrated from gitlab.com)
Copy link

assigned to @gnuget and unassigned @cedewey

assigned to @gnuget and unassigned @cedewey
gnuget commented 2019-01-29 22:57:47 +00:00 (Migrated from gitlab.com)
Copy link

About us:

https://agaric.coop/es/acerca-de-nosotros

https://agaric.coop/about-agaric

About us: https://agaric.coop/es/acerca-de-nosotros https://agaric.coop/about-agaric
gnuget commented 2019-01-29 22:58:16 +00:00 (Migrated from gitlab.com)
Copy link

marked the checklist item Enable multilingual in Drupal 8 / Drutopia as completed

marked the checklist item **Enable multilingual in Drupal 8 / Drutopia** as completed
gnuget commented 2019-01-29 22:58:17 +00:00 (Migrated from gitlab.com)
Copy link

marked the checklist item Write the translations as completed

marked the checklist item **Write the translations** as completed
gnuget commented 2019-01-30 18:22:07 +00:00 (Migrated from gitlab.com)
Copy link

Services:
https://agaric.coop/es/servicios

Trainings:
https://agaric.coop/es/capacitacion

Services: https://agaric.coop/es/servicios Trainings: https://agaric.coop/es/capacitacion
gnuget commented 2019-01-30 18:22:15 +00:00 (Migrated from gitlab.com)
Copy link

assigned to @cedewey

assigned to @cedewey
gnuget commented 2019-01-30 18:22:24 +00:00 (Migrated from gitlab.com)
Copy link

unassigned @gnuget

unassigned @gnuget
mlncn commented 2019-01-30 19:01:28 +00:00 (Migrated from gitlab.com)
Copy link

Excellent.

I mean, Excelente.

Excellent. I mean, Excelente.
cedewey commented 2019-01-31 00:56:11 +00:00 (Migrated from gitlab.com)
Copy link

@gnuget

Configuration I changed (which I know I shouldn't do and will properly only do on my local site and commit to code from now on).

  • Added spanish translation to Contact webform
  • Made Landing Page content type translatable
  • Made paragraphs translatable
  • Disabled translation for Paragraph field (eg: Body Paragraph)
@gnuget Configuration I changed (which I know I shouldn't do and will properly only do on my local site and commit to code from now on). * Added spanish translation to Contact webform * Made Landing Page content type translatable * Made paragraphs translatable * Disabled translation for Paragraph field (eg: Body Paragraph)
cedewey commented 2019-01-31 00:56:50 +00:00 (Migrated from gitlab.com)
Copy link

changed the description

changed the description
cedewey commented 2019-01-31 00:56:55 +00:00 (Migrated from gitlab.com)
Copy link

assigned to @gnuget

assigned to @gnuget
cedewey commented 2019-01-31 00:57:02 +00:00 (Migrated from gitlab.com)
Copy link

unassigned @cedewey

unassigned @cedewey
mlncn commented 2019-02-02 04:29:29 +00:00 (Migrated from gitlab.com)
Copy link

@gnuget sorry for adding to this thread that really we should have closed before @cedewey switched up the configuration, but... one more thing to take into consideration.

Seems we want to avoid anything reporting its language type as undefined ('und').

International Targeting | Language > 'und' - unknown language code (HTTP headers)
HTTP header provided URLs and alternate URLs in an unknown language code 'und'.

Google Search Console sent out this alert:

Message type: [WNC-659602]
Search Console

Incorrect hreflang implementation on https://agaric.coop/

To: Webmaster of https://agaric.coop/,

Google has detected that some pages on your site have implemented the rel-alternate-hreflang tag incorrectly. In particular, there seems to be a problem with incorrect language and region codes, or incorrect bi-directional linking (if page A links with hreflang to page B, there must be a link back from B to A as well). Google uses the hreflang attributes to serve the correct language or regional URL to the right users in search results.

Until you correct the errors on the hreflang links, your website will not benefit from additional language or region targeting.
Fix this problem now:

Find incorrect hreflang implementations

Use the examples provided in the International Targeting feature in Search Console to get a sample of pages with incorrect hreflang implementation.

See Error Report
Need more help?

  • Learn more about how to use hreflang for language and regional URLs.
  • Ask questions in our forum for more help - mention message type [WNC-659602].

With these links:

@gnuget sorry for adding to this thread that really we should have closed *before* @cedewey switched up the configuration, but... one more thing to take into consideration. Seems we want to avoid anything reporting its language type as undefined ('und'). > International Targeting | Language > 'und' - unknown language code (HTTP headers) > HTTP header provided URLs and alternate URLs in an unknown language code 'und'. Google Search Console sent out this alert: > Message type: [WNC-659602] > Search Console > > Incorrect hreflang implementation on https://agaric.coop/ > > To: Webmaster of https://agaric.coop/, > > Google has detected that some pages on your site have implemented the rel-alternate-hreflang tag incorrectly. In particular, there seems to be a problem with incorrect language and region codes, or incorrect bi-directional linking (if page A links with hreflang to page B, there must be a link back from B to A as well). Google uses the hreflang attributes to serve the correct language or regional URL to the right users in search results. > > Until you correct the errors on the hreflang links, your website will not benefit from additional language or region targeting. > Fix this problem now: > > Find incorrect hreflang implementations > > Use the examples provided in the International Targeting feature in Search Console to get a sample of pages with incorrect hreflang implementation. > > See Error Report > Need more help? > * Learn more about how to use hreflang for language and regional URLs. > * Ask questions in our forum for more help - mention message type [WNC-659602]. With these links: * https://www.google.com/webmasters/tools/i18n?siteUrl=https://agaric.coop/&hl=en&pli=1 * https://support.google.com/webmasters/answer/189077?hl=en * https://productforums.google.com/forum/?visit_id=636846783308628855-1433028678&p=community&hl=en&rd=1#!forum/webmasters
gnuget commented 2019-02-24 21:08:18 +00:00 (Migrated from gitlab.com)
Copy link

Ok, I'm going to work on this the next week.

Ok, I'm going to work on this the next week.
cedewey commented 2019-06-27 22:45:03 +00:00 (Migrated from gitlab.com)
Copy link

@gnuget I've translated the homepage, services, initiatives, and training pages. The homepage especially is worth double checking that the translation is correct.

The three blocks across the bottom are custom blocks that can be edited at https://agaric.coop/admin/structure/block/block-content .

However, I don't see a way to translate them.

@gnuget I've translated the homepage, services, initiatives, and training pages. The homepage especially is worth double checking that the translation is correct. The three blocks across the bottom are custom blocks that can be edited at https://agaric.coop/admin/structure/block/block-content . However, I don't see a way to translate them.
cedewey commented 2020-04-13 14:44:16 +00:00 (Migrated from gitlab.com)
Copy link

unassigned @gnuget

unassigned @gnuget
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
bbb-test
D9-upgrade
drush-9-aliases
provision-dewey
No results found.
Labels
Clear labels   
A11y

Accessibility-related issues

  
Automated Testing

   
Contributable

Issues with work that can (potentially) be contributed back to Drupal or other FLOSS projects.

  
Contributed

Tag issues where we have contributed work back to FLOSS projects (replace Contributable tag; the Contributed tag can be removed once the contribution is recorded in a blog or something.

  
Decision

An issue that requires a decision be made.

  
Design

Issues that should include a UX/design work or review.

  
Development

   
Drutopia

Issues related to Drutopia features or infrastructure, or are potential Drutopia enhancements (with tag Contributable).

  
Feature Request

   
IndieWeb

Anything related to interlinking web sites in a broadly IndieWeb fashion, see https://indieweb.org/

  
Infrastructure

   
Marketing

   
Needs documentation

When an issue has uncovered something that should be documented in a user guide or the project wiki or anywhere else outside the issue queue.

  
status::Abandoned

An issue that has been abandoned and will not be completed.

  
status::Blocked

An issue that is blocked for a reason outside Agaric's control.

  
status::Deploy

An issue that has been tested and is ready to be deployed.

  
status::Doing

   
status::Done

   
status::In Review

An issue that has been completed and is ready for a code and/or design review.

  
status::Needs Clarification

   
status::Test

An issue that has been completed and is ready to be tested.

  
status::To Do

An issue that is an agreed priority and has all information needed to be completed.

  
type::Bug

   
type::Task

   
type::User Story
No labels
A11y
Automated Testing
Contributable
Contributed
Decision
Design
Development
Drutopia
Feature Request
IndieWeb
Infrastructure
Marketing
Needs documentation
status::Abandoned
status::Blocked
status::Deploy
status::Doing
status::Done
status::In Review
status::Needs Clarification
status::Test
status::To Do
type::Bug
type::Task
type::User Story
Milestone
Clear milestone
No items
No milestone
Post-Launch
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: agaric/agaric-coop#160
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?