Problem/Motivation
The Rightup publishes news, not blog posts, yet the recipe requires drupal/varbase_blog_base and applies it. Every install carries a Blog post type, a blog view, 19 blog Canvas templates, a "Latest Blog Posts" pattern and blog views blocks nobody uses.
Steps to reproduce
- Install The Rightup from 1.0.x-dev.
- Look at the content types, views and Canvas templates: the blog ones are there, unused.
Proposed resolution
- Remove the requirement and the recipe from composer.json and recipe.yml, with every blog-only config and action.
- Point the author articles view and the CTA card at news.
- Tests create news posts where they created blog posts; the 06 suite becomes 06-content-news.
Only fresh installs change. Existing sites keep their Blog post type.
Checked on a fresh DDEV install of the branch: 33 news, 6 podcasts, 67 episodes, 16 Canvas pages; home, /news, article, author, landing and podcast pages return 200; axe-core reports 0 WCAG 2.2 AA violations; no "blog" text anywhere. 05-content-pages 9/9, 06-content-news 4/4, 09-drupal-canvas 14/14, 12-content-access-and-lock 26/26, 15-quality 110/110; 13-varbase-recipes green except the three API/auth/i18n recipe scenarios that CI applies after install. MR !64 pipeline: 36/36 green.
AI-Generated: Yes
Remaining tasks
- ✅ File an issue
- ✅ Addition/Change/Update/Fix
- ✅ Testing to ensure no regression
- ➖ Automated unit/functional testing coverage
- ➖ Developer Documentation support
- ➖ User Guide Documentation support
- ➖ UX/UI designer responsibilities
- ➖ Accessibility and Readability
- ❌ Reviewed by a human
- ❌ Code review by maintainers
- ❌ Full testing and approval
- ❌ Credit contributors
- ❌ Review with the product owner
- ❌ Update Release Notes
- ❌ Release
- ✅ Open the MR
User interface changes
- No Blog post type, blog view, blog templates or "Latest Blog Posts" pattern on fresh installs.
API changes
- N/A
Data model changes
- Fresh installs no longer get the Blog post content type.
Release notes snippet
- N/A
Issue fork rightup-3627803
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #4
rajab natshah