Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Identify all appropriate entity types and configure appropriate meta tags for them.
Comments
Comment #1
DamienMcKennaI'll put together a spreadsheet of the available meta tags from the Metatag module and we can start filling out entity types & appropriate default values.
Comment #2
DamienMcKennaI've built a spreadsheet of all meta tags supported by the (currently in progress) v1.5 release of Metatag:
https://docs.google.com/spreadsheets/d/176VdONRvD5KK7A8iCM7FC4Jz5__sIBFc...
Anyone who wants to help plot out the entity configurations should request access and we can work through it.
Comment #3
DamienMcKennaSo related to this we also need to work out what submodules are currently enabled and what ones should be added.
Comment #4
DamienMcKennaSo, some ideas and questions on project-related entities:
I think clarifying the title, description/summary and images would greatly help.
Comment #5
wmostrey CreditAttribution: wmostrey commentedThank you for adding me to the spreadsheet. All looks good for the Twitter Cards (#2229149: Add Drupal Issue Metadata for Twitter Cards). We should agree on the Site Account and Creator Account. @Drupal as a default (for drupal.org, groups.drupal.org, ...), @DrupalAssoc for assoc.drupal.org and @DrupalCon/@DrupalConNAfor events.drupal.org?
Should this become a seperate field?
Comment #6
DamienMcKennaThose separate sites are separate installations, so we could just use separate configurations for them.
Comment #7
wmostrey CreditAttribution: wmostrey commentedWe can discuss the Twitter Cards in the other issue. Do we need something more?
Comment #8
wmostrey CreditAttribution: wmostrey commentedAdded #2828997: Improve profile SEO as a child issue.
Comment #9
benjifisherI think we should add