mcLogioraRelease candidate

A modular multilingual foundation for WordPress.

An open-source WordPress product that brings translation relations, language-aware URLs, editor workflows, and operational boundaries into one reviewable product surface.

Read documentation GitHub

WordPress.org submission is outside this page's scope; no public directory URL is claimed yet.

Category: WordPress Product · Multilingual · Open Source
Version: v0.16.0
Distribution: Release candidate · WordPress.org submission pending
Compatibility: WordPress 6.5+ · PHP 7.4+ · Tested up to 7.1
License: GPL-2.0-or-later
Role: Product architecture, engineering, qualification, documentation

Evidence layer

What was built and why it matters

Context

mcLogiora is an independently authored WordPress multilingual foundation with explicit translation relations, language-aware URLs, REST, WP-CLI, and public product documentation.

Problem

A multilingual site needs content relationships, editorial intent, URL state, metadata, and review behavior to stay coherent as content changes.

Constraints

Manual translation remains the baseline. Suggestions are optional and provider-aware, while relation changes must not silently delete, publish, or rewrite source content.

Approach

The product makes languages, relations, translations, strings, media metadata, and import/export packages visible as bounded WordPress workflows.

Engineering

The implementation combines WordPress-native integration with documented PHP functions, authenticated REST routes, WP-CLI commands, diagnostics, portable packages, and explicit lifecycle states.

Observable evidence

The public product page identifies version 0.16.0, a release-candidate line with WordPress.org submission pending.
The local product surface includes real Translation Manager, language, string, URL, suggestion, status, and compatibility screens.
The public documentation and repository provide the review path for product behavior and developer-facing surfaces.

Commercial relevance

This connects directly to WordPress engineering and product work where localization, editorial control, compatibility, and maintainable extension points have to coexist.

Relevant services

Product & SaaS Engineering Engineering Partner

Overview

Translation is treated as product behavior.

Language manager

Translation relations

Language-aware URLs

String and media workflows

REST and WP-CLI

Portable packages

System status

Explicit safety boundaries

The product question

A multilingual site is not a language switcher

The difficult part is keeping content relationships, editorial intent, URLs, metadata, and review state coherent as the site changes. mcLogiora treats those as first-class WordPress data and workflows rather than a thin translation overlay.

The engineering boundary

Every action should be visible and reversible

Manual translation remains the baseline. Suggestions are a separate, opt-in assistant layer; they do not score, publish, mutate files, or run on background traffic. That boundary keeps provider support useful without making the site depend on a remote service.

The release posture

A foundation that can be reviewed

The 0.16.0 line carries the developer and operations surfaces alongside the core translation workflows: REST and WP-CLI access, portable packages, system status, Site Health diagnostics, documentation, and a qualified WordPress 7.1 compatibility statement.

Capabilities

Clear boundaries, deep WordPress integration.

Translation in the editing workflow

Create, link, unlink, review, and update translations for posts, pages, supported public post types, taxonomies, media metadata, strings, menus, and supported widgets without silently changing the source.

Relations with an explicit lifecycle

Translation groups and items use deliberate relation and review states. Unlinking removes the relation only; it does not delete, trash, or rewrite content.

URLs that respect language state

Translated content can use language directories and its own slug. Missing translations remain a normal 404 rather than quietly serving the source language.

Optional suggestions with human control

Bring your own OpenAI, Anthropic, Google Gemini, or DeepL credential when needed. Suggestions are off by default, one field at a time, previewed before apply, and never publish automatically.

Developer surfaces that stay bounded

Read-only mclogiora_ functions, authenticated REST routes for languages, relations, and translations, documented hooks, and WP-CLI commands make the core usable without coupling every workflow to the admin UI.

Portable import/export safety

Deterministic packages support dry-run planning, additive atomic apply, rollback, and stale-plan protection. Import/export transport itself is not exposed as a public REST route.

Product surface