LeraLink Team

Years of research, publishing, and creative work should not have to start from scratch when an organization adopts a new platform. LeraLink’s Import Machine brings existing knowledge into a structured, multilingual publishing environment—from Word documents, Markdown files, and web articles to entire books, collections, and scholarly publications imported by DOI or JATS XML. It converts content into editable Pieces while retaining, where available, headings, images, tables, footnotes, references, and essential publication metadata. Original works and their translations can become different language versions of the same Piece; longer manuscripts can be divided into individual Pieces and subsequently organized into books, dossiers, or other publications. Authors, editors, and publishers retain control over attribution, rights, editorial decisions, and publication. For independent publishers, research institutions, newsrooms, and cultural archives, this means bringing an existing body of knowledge into LeraLink without manually reconstructing every article, citation, or chapter—and making that knowledge ready for continued collaboration, translation, and publication.

An investigative story rarely begins as an article. It begins with documents, interviews, evidence, competing accounts, and weeks or months of collaborative work. By publication day, the newsroom may have accumulated hundreds of files, multiple drafts, fact-checking notes, translations, and related stories. The final article reveals only a fraction of the knowledge produced. LeraLink offers a structured publishing environment for the knowledge behind the story. Journalists and editors can develop content collaboratively, organize sources and related materials, and publish interconnected works across languages. Its modular architecture allows a major investigation to become a series of articles, explanatory pieces, thematic collections, or other publications without treating every output as an unrelated document. For a multilingual newsroom, different language editions can remain connected within the same knowledge structure. For an investigative project, published findings can be related to their sources and subsequently developed into follow-up reporting. LeraLink does not replace secure investigative communication, source-protection procedures, or specialized evidence-management systems. Those require their own safeguards. Its value lies in the editorial and publishing stages: helping media organizations turn accumulated research into coherent, reusable, multilingual public knowledge. One investigation may produce dozens of valuable findings. Your publishing system should help you develop and publish them without losing their connections.

An independent journal may have only five editors and twenty contributors, yet still need to manage submissions, reviews, revisions, author credits, multilingual editions, references, and professional publication. The usual solution is a collection of disconnected tools: email for submissions, Word or Google Docs for editing, spreadsheets for tracking decisions, and WordPress or another system for publishing. Every handoff creates work, and the editorial history becomes increasingly difficult to follow. LeraLink brings editorial collaboration and structured publishing closer together. Authors can develop works within a shared publishing environment, while editorial roles and review processes support the preparation of content for publication. Articles, chapters, books, and other knowledge materials can be organized within the same underlying content architecture, with support for multilingual versions, sources, and contributor attribution. Its modular structure also makes published knowledge more useful beyond its original format. A carefully edited explanation or research finding can become part of another publication without being recreated from scratch. LeraLink is particularly relevant to independent scholarly journals, cultural magazines, specialized presses, and emerging editorial projects seeking a professional digital publishing environment without assembling every function from unrelated services. Its scholarly publishing capabilities are still evolving, so journals with formal indexing, preservation, and specialized standards requirements should evaluate the available workflows carefully. Small publishers deserve professional editorial infrastructure without unnecessary organizational complexity.

An organization may publish hundreds of reports, articles, and research papers yet struggle to answer a simple question: what have we already established about a particular issue? Traditional search often returns documents containing matching words. But relevant knowledge may appear under different terminology, across several languages, or within a small passage of a much larger publication. Finding the document is not necessarily the same as finding the knowledge. LeraLink addresses this problem through structured content, semantic search, and relationships among concepts, entities, and sources. Instead of treating every publication as an isolated container, its architecture allows smaller knowledge units to become discoverable within a connected body of work. Consider a research institute investigating educational inequality. A reader looking for school exclusion may also need findings concerning disability, language barriers, or institutional discrimination, even when those exact words do not appear in the search query. Semantic discovery can help reveal such connections. Their relevance, however, still depends on the quality of the underlying sources, metadata, and contextual interpretation. For publishers, research institutions, and knowledge-intensive organizations, the long-term value of a knowledge library depends partly on whether its contents can be found, understood, and meaningfully connected after publication. Knowledge that remains difficult to discover is knowledge whose potential remains underused.

An organization considering a new publishing platform rarely starts with an empty library. It may have hundreds of articles, research reports, books, translations, and documents accumulated over many years. Moving them raises a question that goes well beyond transferring files: what happens to the knowledge surrounding them? A publication has an author, a date, a source, perhaps several versions, and relationships to other works. It may have accumulated citations and incoming links. If migration preserves only the visible text, much of that context can disappear. LeraLink approaches content organization through structured knowledge units, sources, metadata, multilingual variants, and relationships among works. Its import and migration capabilities are being developed to help organizations bring existing materials into this structure rather than reproduce them as isolated pages. The distinction matters, but migration should not be mistaken for automatic preservation. Metadata quality, original identifiers, internal references, language relationships, copyright permissions, and URL redirects require careful assessment. The extent to which these elements can be preserved depends on the source system, available data, and supported migration tools. For publishers, research institutions, archives, and cultural organizations, a successful transition should preserve as much intellectual continuity as possible while improving how existing knowledge can be organized, discovered, maintained, and reused. An archive represents years of accumulated intellectual work. Its migration deserves the same care as its original creation.

WordPress is an established and highly extensible publishing system. For a conventional website, magazine, or blog, it may be entirely sufficient. But a professional or a research publication often manages something more complicated than pages and posts: evolving works, multiple contributors, editorial decisions, references, translations, and relationships among publications. Consider an independent research journal that also publishes books, policy briefs, and educational materials. WordPress can display these outputs, often with additional plugins and external services. Yet the underlying knowledge, its development history, and its relationships across formats may remain distributed among separate files and systems. LeraLink takes a different architectural approach. It organizes content into identifiable, reusable knowledge units that can become part of larger works. Its publishing environment brings together structured authoring, multilingual content, editorial workflows, and the organization of related knowledge. This makes it particularly relevant to publications whose materials continue to evolve after their initial release. For a publication primarily concerned with maintaining a conventional website, WordPress remains a reasonable choice. For one seeking to build a multilingual, interconnected, and continuously developing body of knowledge, LeraLink offers an alternative highly worth evaluating.

A research organization may write in Google Docs, organize materials in Notion, publish through WordPress, distribute updates through a newsletter service, and manage translations in separate files. Each tool may perform its task well. The difficulty begins when the same knowledge must move between them. A corrected paragraph may need updating in several places. A translated report may fall behind its original. A publication may lose its connection to the sources, editorial decisions, and earlier versions from which it emerged. The organization gradually spends more effort maintaining information across tools than developing the knowledge itself. LeraLink approaches this problem through a shared knowledge architecture. Its reusable knowledge units, called Pieces, can be organized into publications, collections, learning materials, and multilingual projects without treating every output as an unrelated document. Authoring, organization, editorial processes, and publication can operate within the same environment. This does not make every specialized tool unnecessary. It changes the starting point: instead of maintaining knowledge separately in each application, an organization can build and manage a connected body of knowledge from which different outputs emerge. The potential savings extend beyond software subscriptions. They concern duplicated work, fragmented institutional memory, and the long-term cost of keeping knowledge coherent.

First, the main text of each independent Piece or Block is analyzed. Artificial intelligence extracts up to 20 important concepts or entities that are genuinely present in the text and have an importance score of at least 0.5. Recognized names are identified through exact vocabulary matching. New names are first searched in the global LeraLink knowledge registry and then, if necessary, in Wikidata. Using the context of the text, the model determines the correct identity among the retrieved options; cases with confidence of at least 0.85 are automatically confirmed, while ambiguous cases remain for human review. In the next stage, the system measures the presence and importance of each concept across the entire knowledge corpus of the same institution: mention frequency relative to text length, presence density, placement in the title, summary, and headings, key definitions, and semantic proximity. The multilingual bge-m3 model, with 1024-dimensional vectors and cosine similarity, is used to measure semantic neighborhood. Connections between Pieces are also derived from shared concepts and entities, vector proximity, references, authorship relationships, and publication structure, and are stored with weights and evidence. Finally, LeraLink produces three levels of knowledge for each concept: a valid general definition, a contextual description based on evidence from the institution's knowledge corpus, and an integrated account. As the knowledge corpus expands significantly, these descriptions are reconstructed while human revisions are preserved. The result is a dynamic multilingual knowledge graph whose semantic connections are traceable and reviewable.

You can either write your text or fill in the content of a different block type. Once you’re satisfied, you can publish it, keep it private, or share it only with your platform’s members. You can add footnotes, references (both bibliographical and external links), and formatting options like highlighting, bolding, and italicizing. You can also change the block type from the toolbar or even the original language of your block. 

An Institution is an independent institutional page within LeraLink. It represents a distinct part of an organization that needs its own public identity and its own way of presenting knowledge. For example, one organization may create separate Institutions for its research center, graduate school, publication unit, public education platform, or community initiative. Each can have its own landing page, content, and knowledge structure while still belonging to the same larger organization. Institutions are modular. They can be created and shaped according to the structure and needs of each organization. An Institution is therefore not necessarily a separate legal organization. It is the public-facing space through which an organizational unit presents its identity, activities, and knowledge in LeraLink.

LeraLink organizes knowledge through a set of connected levels, from public institutional spaces down to small reusable units of knowledge. The structure is: Institution → Program → Dossier → Series → Volume → Composition → Piece → Block An Institution is the top-level public-facing space in this structure. An organization can create more than one Institution for different parts of its work, such as a research center, school, publication, community, or educational initiative. Within an Institution, knowledge can be organized into Programs, Dossiers, Series, Volumes, and Compositions. A Composition brings Pieces together into a meaningful work, such as an article, chapter, lesson, or similar structure. A Piece is the smallest meaningful and reusable unit of knowledge. Each Piece is made of one or more Blocks, such as text, images, quotations, audio, video, or other content elements. This structure allows organizations to present complex bodies of knowledge while keeping individual knowledge units small, reusable, and connected.

An Entity is a clearly identified person, organization, place, concept, event, work, or other subject connected to knowledge in LeraLink. Entities help LeraLink understand what a Piece or Source is about. For example, a Piece about Paulo Freire may be connected to the Entity Paulo Freire, the concept Critical Pedagogy, and the work Pedagogy of the Oppressed. Entities can be connected to many Pieces and Sources. This creates a shared network of knowledge and helps users discover related material across different projects, languages, and formats. Unlike a keyword or tag, an Entity has its own identity and can carry structured information and relationships.

A Source is the original material that supports, informs, or provides evidence for a Piece or a Block. A Source can be a book, article, research paper, chapter, report, website, lecture, podcast, video, dataset, archive, or another type of reference. Pieces can be linked to one or more Sources. This helps show where the knowledge comes from and makes it easier to verify, explore, and reuse responsibly. A Source is not the same as a Piece. The Source is the reference material; the Piece is the smaller unit of knowledge created, extracted, summarized, explained, or connected from it. Linking Pieces to Sources helps keep knowledge traceable and transparent.

A Block is the basic content element used inside a Piece. A Block can be a paragraph, heading, quotation, image, audio clip, video, list, embed, or another content type. Several Blocks can be combined to form one Piece. A Piece represents a meaningful unit of knowledge. A Block represents how that knowledge is structured and presented. For example, one Piece may contain a short explanation, an image, and a quotation. These are three separate Blocks inside the same Piece. Blocks make it easier to edit, arrange, reuse, and display content in different formats while keeping the Piece as one coherent unit.

A Piece is the smallest meaningful unit of knowledge in LeraLink. A Piece can contain an idea, explanation, argument, example, quotation, image, audio, video, or another form of useful knowledge. It should be small enough to reuse, but complete enough to make sense in context. Each Piece has its own identity. It can be connected to sources, translated into other languages, reviewed, updated, linked to other Pieces, and placed in different structures. A Piece does not belong permanently to one article, lesson, or course. The same Piece can be reused in different contexts without being recreated. This makes knowledge in LeraLink modular, traceable, flexible, and easier to maintain.

A Content Management System (CMS) is mainly designed to create, organize, and publish content such as web pages, articles, posts, or media. LeraLink is designed around knowledge rather than pages. In a typical CMS, content is usually created for a specific page or publication. In LeraLink, knowledge is stored as smaller, independent pieces that can be connected, translated, reviewed, reused, and placed in different structures without being copied. A CMS helps you manage content. LeraLink helps you manage the relationships, meaning, reuse, and development of knowledge. This makes it possible to use the same knowledge in different articles, guides, courses, collections, or learning experiences while keeping its identity and history intact.

A Learning Management System (LMS) is mainly designed to deliver and manage courses. It usually organizes learning around fixed structures such as courses, modules, lessons, assignments, and enrolled learners. LeraLink starts from a different point: the knowledge itself. In LeraLink, knowledge is created as small, reusable pieces that can exist independently of any single course. The same piece can be translated, reviewed, connected to other knowledge, reused in different learning paths, or included in several projects without being duplicated. An LMS usually asks, “How do we deliver this course?” LeraLink also asks, “How can this knowledge remain useful, connected, reusable, and accessible across different languages and contexts?” LeraLink can support courses and structured learning, but the course is only one possible way of organizing the knowledge.