Repository Formats

Migration & Conversion

Door43 Developer Documentation

Build applications with Door43's comprehensive Bible translation resources. This documentation provides everything you need to integrate unfoldingWord's ecosystem of aligned Bible texts, translation helps, and quality assurance tools.

Built for the Open Components Ecosystem community - enabling interoperable Bible translation applications with shared, reusable components.

🎯 New Here? Start with Getting Started

Getting Started - Essential foundation for understanding the Door43 ecosystem

Before diving into technical implementation, understand why these resources exist and how they help Bible translators worldwide. This foundation will make all the technical guides much more meaningful and help you build better applications.

Recommended first read: Why unfoldingWord Translation Resources - Learn the mission and see real-world translation scenarios.

🎯 Find What You Need

By Resource Type

ResourceWhat It ContainsFormat Guide
Bible TextsUSFM Scripture (UHB, UGNT, ULT, UST)Bible Text Guide
Translation NotesVerse-level translation guidanceTranslation Notes Guide
Translation WordsBiblical term definitionsTranslation Words Guide
Translation QuestionsQuality assurance questionsTranslation Questions Guide
Translation AcademyTranslation methodology trainingTranslation Academy Guide
Open Bible Stories50 key Bible storiesOpen Bible Stories Guide

By Technical Task

TaskPrimary GuideSupporting Guides
API AuthenticationDoor43 API Guide-
Repository DiscoveryDoor43 API GuideRepository Formats
Content ProcessingRepository Format GuidesunfoldingWord Guide
Format ConversionMigration GuidesRepository Formats
Word-Level AlignmentunfoldingWord GuideBible Text Guide
Cross-Reference LinkingTranslation Words Links GuideTranslation Words Guide

By Experience Level

🚀 Quick Start by Use Case

Building a Bible Reading App?

1. Read: Why unfoldingWord Resources → Understand the ecosystem
2. Implement: Door43 API Guide → Get data from repositories  
3. Handle: Bible Text Format Guide → Display USFM content
4. Add: Translation Notes Guide → Show verse-level helps

Time: ~4 hours | Difficulty: Intermediate

Creating a Translation Editor?

1. Study: unfoldingWord Developer Guide → Learn resource architecture
2. Implement: Door43 API Guide → CRUD operations for content
3. Handle: All Repository Formats → Support multiple resource types
4. Add: Migration Guides → Convert between formats

Time: ~2-3 days | Difficulty: Advanced

Converting Resource Formats?

1. Identify: Repository Formats → Determine source format
2. Choose: Migration Guide → Find specific conversion guide
3. Convert: Follow step-by-step instructions
4. Validate: Test converted resources

Time: ~4-8 hours | Difficulty: Intermediate

Building Automation Tools?

1. Learn: MCP Instructions → Understand automation patterns
2. Implement: API Reference for MCP → Optimize for batch operations
3. Deploy: Repository Analyzer → Automated content analysis

Time: ~1-2 days | Difficulty: Advanced

📚 Documentation Sections

Getting Started

Understand the ecosystem and mission

Developer Guides

unfoldingWord Developer Guide

Complete technical specification of the resource ecosystem

  • Resource architecture and alignment system
  • Cross-resource relationships and dependencies
  • Advanced integration patterns

Door43 API Developer Guide

Practical API implementation patterns

  • Authentication and repository access
  • Common workflows and use cases
  • Performance optimization strategies

Repository Formats

Handle specific resource types

  • Resource Container - Standard unfoldingWord formats (Bible texts, translation helps)
  • Scripture Burrito - Alternative Bible resource format
  • Tool-Generated - translationCore and translationStudio formats

Migration & Conversion

Convert between formats

  • Resource Container → Scripture Burrito conversion guides
  • Format-specific migration instructions

Automation & MCP

Automated processing and analysis

  • MCP instructions for AI systems
  • Batch processing and repository analysis

Common Implementation Patterns

Basic Resource Access

1. Authenticate with Door43 API
2. Discover repositories by language/organization
3. Detect resource specification (RC/SB/Tool)
4. Process content according to format guide

Multi-Resource Applications

1. Load Bible text as primary content
2. Overlay translation notes for verse guidance
3. Link translation words for term definitions
4. Add translation questions for quality checks

Format-Agnostic Processing

1. Detect resource specification automatically
2. Route to appropriate format handler
3. Extract content using specification patterns
4. Present unified interface to application

🆘 Need Help?

Common Questions

Recommended Learning Path

Most developers start here: Getting StartedDoor43 API Developer Guide - understand the mission, then learn practical implementation patterns.

🔗 External Resources