Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CONSIDER: Drupalize the homepage meta description #19392

Open
10 tasks
jilladams opened this issue Oct 2, 2024 · 0 comments
Open
10 tasks

CONSIDER: Drupalize the homepage meta description #19392

jilladams opened this issue Oct 2, 2024 · 0 comments
Labels
Drupal engineering CMS team practice area Public Websites Scrum team in the Sitewide crew sitewide UX VA.gov homepage CMS managed product owned by Public Websites team

Comments

@jilladams
Copy link
Contributor

jilladams commented Oct 2, 2024

In #18020 we created a hard coded meta description for the homepage.

Everything else on the homepage (with some small exceptions) is configurable in Drupal. Should this be configurable as well?

Blockers

  • Product direction on where it makes sense to weave this into Drupal, related to homepage content
  • Drupal UX guidance for items below, as write up or Figma -- should this be its own ticket?
    • Character count
    • Helptext
    • Field type
    • Placement

ACs

  • Drupal field is created to manage the Homepage field description
  • UX review
  • A11y review
  • FE ticket created to follup and replace the hard-coded description with content from this new Drupal field
@jilladams jilladams added sitewide Drupal engineering CMS team practice area VA.gov homepage CMS managed product owned by Public Websites team Public Websites Scrum team in the Sitewide crew UX labels Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Drupal engineering CMS team practice area Public Websites Scrum team in the Sitewide crew sitewide UX VA.gov homepage CMS managed product owned by Public Websites team
Projects
None yet
Development

No branches or pull requests

1 participant