Case study Utility Plugin

Lubinik API

Utility Plugin

Lubinik API is the read-only public data layer for Lubinik sites. It exposes entities, collections, taxonomies, media, menus, settings, search results, and shortcode data providers as clean JSON, without turning WordPress into a second admin system.

  • API
  • Public Data
  • REST

Inside

StackAPI, Public Data, REST
Child Themelubinik-child-showcase
Pluginslubinik, lubinik-showcase-addon
01

Problem

Lubinik already stores structured content in WordPress: case studies, addons, taxonomies, galleries, menus, settings, and shortcode-managed sections. If a future mobile app, headless frontend, or external tool needs that content, duplicating the data in another database would create the exact maintenance problem Lubinik tries to avoid.

02

Solution

The API plugin follows the same config-driven philosophy as SEO Light and Structured Data. It discovers public data from WordPress and Lubinik registries, then lets each layer refine the output through optional `config/api` files. The plugin stays agnostic: addons, themes, the core plugin, and child themes can declare what they own without hardcoding project-specific assumptions into the API engine.

03

Results

The first implementation provides a public read API with manifest, schema, health checks, entities, collections, taxonomies, terms, settings, menus, media, search, pages, entity pages, and shortcode data endpoints. It supports CORS, optional tokens, rate limiting, and public-data boundaries, making it a clean doorway for future apps without exposing private admin data.