Launch retro and brainstorm

[allcaps]

Attendees:

• @saevarom,
• Tumi Þorsteinsson
• @Scotchester
• @allcaps
• @thibaudcolas (notes are added)

Superpowers

• Large group
• Good range of skills
• Clear goal
• Created a lot of value for clients
• Icelandic and German translations validate the guide.
• Multilingual team
• We kept it simple
• Good comms on Slack
• People committing some serious time on short notice
• GitPod worked really well

Weakness

• Wagtail Localize seems less stable than expected
  • Orphaned translations is a problem
  • We need to keep access to obsolete strings in the UI.
  • Translation is using hash of source and translation combined, that seems to be the issue.
• Wagtail Localize sync feature is great feature we can't do without.
• Too many pages are marked as outdated
• We need a roadmap
• Invite community to translate
  • We need to have a language moderators (publish rights) for each language.
  • Language moderators can only be created by administrators.
  • But how do we choose these people?
• Invite Transifex translators to join Wagtail Guide
• Idea, to upload/download POs to/from Transifex
• How are screenshots created? How to do the same for other language?
• Didn’t really have enough time to rework the content
• What’s Explanations again?

Sidekicks

• We are all sidekicks! Yeah!
• How do we onboard translators?
• We need more original content
  • Have a plan / list of topics.
• Have more distinct writing styles per Diataxis section.
• More translator teams, various languages
• Translators team?
• Setup for automated translations?
• A documentation team?
• A ready-to-go demo site w/ the right features set up & demo data
• Always-available live demo site

Features (wish list)

• Download assets view that provides periodic downloads
• Guide as part of the Wagtail Site (slimmed down) → Package 
  • Have a ‘register help page’ hook for third party packages to hook into the same guide?
• Auth views to create accounts.
• Model for image translations -> @allcaps
• Automated screenshots
• Percy for visual diff https://percy.io/
• What about contrib packages? → Document first
• Have a list of third-party packages, and point to their USER documentation.
• Message Transifex contributors and invite them to help with the guide
• Scripting & translating screenshots 

Actions

• @allcaps Discovery of translatable image models
• @allcaps Look into downloads of content+media as starting point for loading into a custom guide. 
• Onboarding new translators.
• Add create account form.