Apr 5 - Apr 16, 2022

Report on iteration Apr 4, 2022 — Apr 15, 2022 (includes all issues completed before Apr 18, 2022).

This iteration we made progress on the remaining multilingual functionality and other features needed to publish Startwords issue 3. We didn’t close a lot of points on the Geniza project because the major work going on at this point is prototyping and beginning to implement the new transcription functionality, and sketching out design ideas for the public display and interaction of images with transcription and translation content. Our rolling development velocity is 4.67, due to the low number of points completed in the last two iterations (3, 4). We expect this to pick up once we move out of the transcription prototyping phase and finish work on the Startwords issue.

Demos

---

Active projects

• geniza (4 points, 6 issues)
• startwords (7 points, 7 issues)

Releases

Velocity

Development

4 points, 10 issues. Rolling velocity: 4.67

Design

7 points, 3 issues. Rolling velocity: 8.33

---

Closed issues by project

• geniza (4 points, 7 issues)
  • design (4 points, 3 issues)
    • External links page design revisions 🚫 wontfix, 🗺️ design
    • Revise the new order of content on the doc detail page and ensure the backend aligns with the interface (2) 🗺️ design
    • Revise the styling of fields and labels and notes on the doc detail page (2) 🗺️ design
  • development (0 points, 4 issues)
    • generate a report on google docs transcriptions 🛠️ chore
    • transcription prototyping 🛠️ chore
    • Implement the site header for the Hebrew site
    • Implement pagination for the hebrew site
• startwords (7 points, 8 issues)
  • design (3 points, 2 issues)
    • Design a way to switch the language displayed in the main nav sections of the website (3) 🗺️ design
    • Adjust/propose solutions for purple part of the site nav to accommodate space for the translations of "issues" wontfix, 🗺️ design
  • development (4 points, 6 issues)
    • As an editor, I want to document issue contributors once for translated issues so that I don't have to duplicate information or risk it getting out of sync. (1)
    • feature article opening line preview needs to accommodate a wider range of text lengths
    • As a spanish reader, I want the main navigation to acommodate "issues" in translation so that the translated word fits and displays properly. (1)
    • As a Spanish reader, I want navigation and paratext in my language so that I know how to use the site. (1)
    • As a reader, when reading the issue details page I want to know which language(s) each article is available in, so that I can identify translated content and default language is explicit. (1)
    • adjust spacing for article layout on homepage and issue detail page

---