The Showcase addon is a strange little loop in the project: Lubinik using Lubinik to document Lubinik.
When I started thinking about the site that would explain the framework, I already had the Freelance addon. Freelance had projects and case studies, which sounded close to what I needed. But using the whole Freelance addon would have been too much.
The Lubinik site does not need services, packs, clients, leads, waitlists, QCM forms, tool workflows, or a full professional-site content model. It needs a way to explain pieces of the framework: what each theme, plugin, addon, child theme, and tool does, why it exists, what problem it solved, and what it taught me.
Reuse does not mean copying the biggest thing
So Showcase became a lighter addon based on the useful pattern: case studies.
It has one main CPT for case studies, taxonomies for project types and stack components, and focused single-page sections like summary, stack, problem, solution, results, links, related items, and galleries.
That is enough. The parent theme can handle the generic site: homepage sections, blog, header, footer, menu, heroes, custom sections, and normal pages. The Showcase addon only needs to bring the structured layer that belongs to the Lubinik story.
This is a good reminder for future addons too. Reuse is not always copying a large existing system. Sometimes the cleaner move is to extract the smaller pattern and leave the rest behind.
