Roadmap

This is a "living roadmap," which we will adapt based on user feedback!

The following milestones are grouped into categories and roughly ordered by priority within each category, though note that we are following a shotgun-based approach as per our Project Philosophy.

Codex Milestones

• Package for user downloading We have a downloadable, compiled app, with a pre-packaged and compliled 'hello world' extension.

• Create UI strategy For now, perhaps just serif font, black on white, hide or decorate line numbers, etc.?

• Project standards to support initially ORG plaintext project extracted from Paratext? Use a USJ underlying representation for Paratext export?

  • Support plaintext project with ORG verse referencing (i.e., eBible corpus projects) |-- project | |-- scripture | | |-- matthew.txt | | |-- mark.txt

    | |-- resources | | |-- my_resource.pdf | | |-- another_resource.md

  • Support USJ project with extensible metadata and Paratext export

• Determine whether it is easier to implement language diagnostics in an RCL custom rich text editor, or else adapt the display of the native VS Code editor to function or simply look more like a rich text editor

• Implement audio mode PoC (cf. Multimodality)

Translator's Copilot Milestones

• Implement initial Chat with Resources functionality

• Curate initial offline and online source text resources for Greek/Hebrew Insights

• Create initial orchestrated translation Quality Checking functionality Quality checking functionality will be a language server extension for text content analysis.

  • Basic scripture checking (e.g., verse order, etc.)

  • Greek Room spell checking and normalization

  • (?) UnfoldingWord TranslationCore Notes checks

  • Abstract functionality into shared repository with SIL/ScriptureForge team

• Implement initial Translation Drafting functionality

General Project Milestones

• Non-public documentation of translators interested in testing

• Create translator-feedback and testing workflow