Case study Child Theme

BnB Child Theme

Child Theme

The first BnB child theme belongs to the early Lubinik phase. It contains direct overrides for BnB templates, shortcodes, CSS, JavaScript, headers, footers, mobile behavior, accommodation lists, galleries, menus, translation behavior, and plugin assets.

  • Child Theme
  • Site Addon

Inside

StackChild Theme, Site Addon
Addonlubinik-bnb-addon
Pluginslubinik, lubinik-bnb-addon, lubinik-translation
01

Problem

In the beginning, the project boundaries were still blurry. The child theme did a lot of direct plugin and template replacement, because the cleaner override systems had not yet emerged.

02

Solution

The first BnB child theme solved real site needs with local overrides and site-specific presentation. Looking back, it also revealed what should not stay ad hoc forever: asset replacement, shortcode overrides, template swaps, and context-specific layouts needed a cleaner convention.

03

Results

This early BnB child theme is useful historical evidence. It explains why later child themes moved toward metadata-driven template packages, context-aware assets, declared removals, and fewer direct copies of addon internals.