Front page meta description still references obsolete node:summary

Steps to reproduce:

1. git clone https://git.drupalcode.org/project/drupal_cms.git
2. cd drupal_cms
3. ddev config --project-type=drupal11 --docroot=web --php-version=8.3
4. ddev start
5. ddev composer install
6. ddev launch

Skipped majority of config (no option to install SEO Recipe anyway).

Applied SEO tools recipe:

• This wasn't presented as an option on installation for dev, which confused me and it took a while (far too long in fact as the "commands" shown didn't work not matter what paths I was using under ddev) to figure out how to install it using the drupal script.
• I installed drush and from web, ran ddev drush recipe ../recipes/drupal_cms_seo_tools -v

View page source:

• Plenty of og and twitter tags present so recipe is installed.
• Both og:description and twitter:description are missing, presumably because they have null values before the patch.

Removed container, to start again, so repeated all of the above with the above recipe patched before I installed it.

View page source:

• Both og:description and twitter:description now have the vale "This is the home page of your new site. Start by editing this page, or creating new pages.".

All looks good to me.

I think we probably need to update the test coverage for this to ensure it doesn't regress later.

@phenaproxima annoying that we have really good test coverage of the meta tags but the front page requires separate config. Should we try to replicate this coverage for home? Or just quickly check for the values?

Either way would be good to get this fix in for 1.0.1 and follow up with tests.

Created 📌 Add test for front page meta tags Active for adding tests.

Merged into 1.x and cherry-picked to 1.0.x. Thanks!

Release notes are now handled via change records.

Created the change record, it just needs details filled in. https://git.drupalcode.org/project/drupal_cms/-/wikis/Committer-Info/Cha... can be used as a template.

CR published.

Screenshot added to change record.

Automatically closed - issue fixed for 2 weeks with no activity.