Vicunav Plugin Core

Shared foundational capabilities for the Vicunav WordPress plugin ecosystem.

Status

The foundational public contract 1.0.0 is fully implemented in plugin version 0.1.0. The plugin is installable and provides its shared content, settings, security, and REST capabilities without depending on a specific theme or business vertical.

Responsibilities

vicunav-plugin-core owns reusable platform capabilities that do not belong to a presentation theme or to a business vertical. Its contracted area includes shared WordPress content types, common settings infrastructure, reusable security utilities, and the base REST namespace for the ecosystem.

The repository owns the Vicu\Core PHP namespace. Its versioned public API, signatures, compatibility rules, and loading order are defined in docs/contrato-publico.md.

Public capabilities

• Vicu\Core\PostType, an abstract base for code-owned WordPress post types.
• Shared vicu_faq and vicu_testimonial post types with REST support.
• Vicu\Core\Settings::get() and extensible tabs under the Vicunav admin menu.
• Vicu\Core\Security helpers for common input, nonce, and capability checks.
• Vicu\Core\Rest route registration under the vicu/v1 namespace.

Requirements

• WordPress 6.6 or later.
• PHP 8.1 or later.

Install the repository as a WordPress plugin and activate Vicunav Plugin Core. Public classes are autoloaded after the plugin entry point is loaded.

Boundaries

• It does not contain presentation patterns, templates, or theme styling. Those belong to vicunav-theme-core.
• It does not contain payments, reservations, restaurant orders, or other vertical business logic.
• Other packages must depend only on published contracts and public hooks, never on another package's internal database details.

Development

The shared ecosystem standards are included as a Git submodule:

git submodule update --init --recursive

Read the repository-specific instructions in AGENTS.md and the shared standards in docs/standards/ before contributing.

Install development dependencies and run the complete validation suite:

composer install
composer check

The integration suite requires an isolated MySQL database. See docs/pruebas.md for the environment variables and LocalWP socket workflow.

Contributions follow an atomic issue, branch, pull request, and squash-merge workflow. See CONTRIBUTING.md.

License

This project is licensed under the GPL-2.0-or-later license.