How kadirermantr/multilify works
Multilify is a WordPress multilingual-content plugin. Its principal workflow is configuring languages, entering per-language translations and slugs in the editor, then serving those translations at language-specific URLs. The README also documents language switching, browser detection, translation progress and SEO language metadata. The main class is a large, partly unsampled implementation, so the graph groups several runtime responsibilities under that exact source path; uncertain internal call wiring is omitted.
Main entry points: class-multilify.php Language settings · multilify.php Plugin bootstrap · admin-page.php Settings screen · meta-box.php Translation editor
Components 16
Plugin entry
- Plugin bootstrap
multilify.php
Language administration
- Language settings
includes/class-multilify.php - Settings screen
includes/views/admin-page.php - Admin interactions
assets/js/multilify-admin.js
Translation and routing
- Translation editor
includes/views/meta-box.php - Translation handling
includes/class-multilify.php - Translation metadata
includes/class-multilify.php - Localized URL routing
includes/class-multilify.php
Visitor experience
- Localized page output
includes/class-multilify.php - Language switcher
includes/class-multilify.php - Browser detection
includes/class-multilify.php - SEO language metadata
includes/class-multilify.php
Other components
- Site administrator
- Visitor
- WordPress
- WordPress database
Connections 19
- WordPress → Plugin bootstrap: loads plugin
- Plugin bootstrap → Language settings: initializes
- Site administrator → Language settings: manages languages
- Language settings → Settings screen: renders settings
- Settings screen → Admin interactions: uses interactions
- Language settings → WordPress database: stores language options
- Language settings → Translation editor: provides editor
- Site administrator → Translation editor: enters translations
- Translation handling → WordPress database: saves translations
- Translation handling → Translation metadata: updates metadata
- WordPress → Localized URL routing: routes requests
- Localized URL routing → WordPress database: resolves translated slugs
- Localized page output → WordPress database: reads translations
- Visitor → WordPress: requests page
- WordPress → Localized page output: serves page
- Visitor → Language switcher: chooses language
- Visitor → Browser detection: visits site
- Browser detection → WordPress database: remembers choice
- Localized page output → SEO language metadata: sets language metadata