The first version of the plugin-side shortcode manager solved one problem: it could render active shortcodes in the order selected from the admin.
That was already useful. A single custom post type page no longer had to hardcode every section forever. The manager could decide whether to show the gallery, details, related content, calls to action, tabs, or any other registered section.
But Shelter made another problem visible. Some pages do not want to be one simple vertical stack.
An animal profile might need a strong hero, a split layout, a gallery-first design, a sticky area, or a template that places certain shortcodes in very specific positions. A BnB accommodation page might need a completely different rhythm. A case study might want a narrative structure instead of a list of blocks.
Not a visual builder, still not rigid
That is when the selected template shell became important.
The manager should not only decide which shortcodes are active. It should also be able to choose which coded template renders them.
The classic template can stay simple: render the active shortcodes in order. But an addon can also provide more opinionated templates. A template can call specific managed shortcode sections in specific places, add layout structure around them, and still let the manager control which pieces exist and how they are configured.
This became one of the cleaner compromises in Lubinik. The page is not built by dragging things around visually. The layout is still a file. But the admin can choose between several file-based templates and manage the sections inside them.
That small shift made entity pages feel less like generated output and more like designed pages that still belong to the framework.
