massgov / massgov/feature-requests

Add organization-specific footers

Open
#280 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
12
Forks
8
PR merge metrics
No merged PRs in 30d

Description

Is your feature request related to a problem? Please describe.
We'd like to link to our accessibility and language access statements on all our organization's pages. This information is on our About page, but most constituents go directly to another page rather than via the About page. They may not necessarily know or easily be able to find that they can request reasonable accommodations or translations of our content.

Describe the solution you'd like
An organization-specific footer that would automatically be included on all pages that have MOD as the parent page. It could include a link to the About page, accessibility statement, language access statement (in multiple languages), and contact information. We'd also like the ability to remove it from specific pages as needed.

Additional context
Perhaps this could be incorporated into the current Contact Block or "Related" areas.

Reference
Include JIRA ticket number or ServiceNow ticket numbers that correspond to this issue.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing About page and the current Contact Block and Related areas mentioned in the request. Determine how organization pages and MOD parent pages are represented, then define how a configurable footer would appear on child pages and be excluded from selected pages. Done means the footer supports the requested links, languages, contact information, and page-level removal.

Written by the indexing model from the issue text.

Assessment

Domain
content, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.