A community-centred learning platform designed to help people teach language, share stories, preserve cultural knowledge, and connect learners across generations.
Heritage language learning often lives across classrooms, homes, community gatherings, recordings, and individual memories. The platform is intended to bring those experiences into one respectful learning environment.
The product direction prioritizes flexible teaching methods, community roles, oral learning, stories, and the ability to reflect how each community chooses to organize and share knowledge.
Connect vocabulary and grammar to stories, conversation, place, family, and lived cultural meaning.
Create pathways for elders, knowledge keepers, teachers, parents, youth, and independent learners to contribute and learn.
Planned experiences recognize that teaching, learning, approving, organizing, and preserving content are different responsibilities.
Follow guided learning paths, practise at a comfortable pace, and bring language into everyday family life.
Build lessons, organize cohorts, guide activities, and understand where learners may need more support.
Contribute stories, pronunciation, context, and community knowledge through clear review and permission workflows.
Manage programs, roles, content visibility, learner access, and community-specific governance.
These capabilities describe the current product direction and will be refined with pilot communities.
Combine text, images, audio, video, downloadable resources, activities, and assessments into structured pathways.
PlannedSupport pronunciation, listening comprehension, repetition, and voice-based learning within each lesson.
PlannedPresent stories with speaker context, translations, transcripts, related vocabulary, and community-approved visibility.
PlannedSeparate authoring, teaching, review, approval, administration, and learner access according to community needs.
PlannedHelp educators understand participation, lesson completion, assessment progress, and learning-path momentum.
PlannedPrioritize responsive learning and efficient media delivery for learners using phones or less reliable connections.
PlannedThe product direction treats permissions, attribution, review, and culturally appropriate access as first-class design questions. Final governance capabilities will be shaped with participating communities and documented in product terms.
Define who can create, review, publish, update, and retire community content.
Support different visibility rules for learners, families, instructors, members, or approved groups.
Keep speaker, contributor, source, usage, and cultural context connected to material.
Minimize personal information and design secure, age-appropriate participation options.
Communities can organize learning around proficiency, topics, age groups, family use, seasonal programs, or their own framework.
Choose a pathway that matches goals, level, and available learning time.
Build understanding through language, voices, stories, images, and cultural context.
Reinforce learning with repetition, activities, reflection, and guided feedback.
Carry language into family, community, teaching, and everyday conversation.
The LMS is in an early product stage. Meridian is looking for organizations and educators willing to validate priorities, workflows, governance needs, and the learning experience.
Understand teaching models, learner needs, content practices, access rules, and success measures.
Develop course, media, user-role, progress, and foundational administration capabilities.
Test real learning journeys with pilot groups and improve usability, governance, and reporting.
Prepare implementation, support, privacy, accessibility, and onboarding materials for wider adoption.
Not yet. It is in development, and the page describes the current product direction rather than a finished feature set or committed release date.
That is the intent of the pilot process. Meridian wants to validate language-learning formats, roles, permissions, governance, reporting, and accessibility with participating organizations before broader release.
Multilingual content and interface flexibility are part of the planned direction. The supported scripts, language pairs, and authoring workflows will be confirmed through technical discovery and pilots.
The product direction prioritizes configurable roles, approval, attribution, access controls, privacy, and clear product agreements. Specific safeguards and hosting arrangements will be documented before a pilot handles real community content.
If your organization teaches or supports a heritage language, Meridian would like to understand what an LMS must do—and what it must respect—to be genuinely useful.