If it's in Moodle, we translate it. Really — not just strings.
Book chapters
Every chapter title and HTML body. Images, tables, lists, embedded media preserved.
Pages
Page titles and full content including inline formatting.
Labels
Section labels, inline descriptions, introductions.
Quizzes — fully
Question names, question text, general feedback, every answer option AND per-answer feedback. No truncation.
H5P interactives
H5P package JSON walked and translated at the leaf level — drag-text, blanks, multi-choice, timeline, all of it.
Wiki pages
Both the cached rendered content and the underlying wiki_versions row, so edits don't revert.
Lessons
Lesson page titles, content, answers and responses. Branching preserved.
Feedback surveys
Feedback items including pipe-delimited answer options ("Yes|No|Maybe" stays structurally identical).
Sections + course meta
Section names and summaries. Course fullname, shortname, summary on the course landing.
Moodle 4.0 and newer. And Moodle-compatible LMSs.
Moodle 4.0 – 5.x
Full support, default target. The post–question-bank-refactor architecture is what we were built for.
Moodle 3.9 – 3.11
Supported with a legacy adapter. Quoted case-by-case — usually +15% on the base price.
Totara, IOMAD, Moodle Workplace
Same schema, same pipeline. Let us know which one and we'll handle the specifics.