refactor: #3616588 Move the Stories view displays to Varbase News Base and Varbase Events Base

Rajab Natshahrequested to merge
issue/educare-3616588:3616588-move-the-stories into 1.0.x

Fixes #3616588.

Depends on varbase_news_base !9 (#3616585) and varbase_events_base !15 (#3616587) being merged and released first. Merged before then, the Stories section loses its two displays.

Problem/Motivation

Making the Stories section dynamic in #3616545 added two Views block displays to this recipe: featured for views.view.news and latest for views.view.events — ~380 lines.

Neither belongs in a site template. The news view is owned by Varbase News Base; the events view is reshaped by Varbase Events Base. Defining the displays here made them unusable by any other consumer of those recipes, and left several hundred lines of view configuration in a file that should not own it. The exported displays also carried vartheme_bs5_educare: component ids, which only work on this template's theme.

Proposed resolution

Remove both from recipe.yml; they now ship from the recipes that own their views, with the base theme's component ids. This recipe's existing setViewsComponentStyleTheme actions repoint them to vartheme_bs5_educare at install, exactly as they already do for every other display.

The Home page keeps the two Views blocks it places — only the definitions moved.

Testing

Fresh Varbase 11 install with all three changes in place:

  • both displays arrive from the base recipes and are repointed to vartheme_bs5_educare:views-view-grid
  • Stories renders 3 real upcoming events and 2 real news posts, no duplicates
  • 0 render errors across all 12 site pages
  • prop audit over every Canvas content template — 608 values, 24 templates — 0 invalid values

Diff is −380 / +0; 306 + 74 is exactly what the two base recipes gained, so nothing was lost in the move.

AI-Generated: Yes

Checkpoints:

  • File an issue
  • Addition/Change/Update/Fix
  • Testing to ensure no regression
  • Automated unit testing coverage
  • Automated functional testing coverage
  • UX/UI designer responsibilities
  • Readability
  • Accessibility
  • Performance
  • Security
  • Developer Documentation
  • User Guide Documentation
  • Reviewed by human
  • Code review by maintainers
  • Full testing and approval
  • Credit contributors
  • Review with the product owner
  • Release notes snippet
  • Release
Edited by Rajab Natshah

Merge request reports