massgov / massgov/feature-requests

Suppress display of individual events on pages that include events

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

Nobody has claimed this yet.

Design support Events
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.
From a ServiceNow request: "Can we use events without the two events at the bottom of the page? We would like to have a previous and an upcoming page but not display only two meetings since in this case we have many more and think people will not click to see the additional meetings."

Describe the solution you'd like
In its simplest form, this request could be fulfilled by offering a checkbox within the page types that are capable of displaying events (Organization, Service, and some law library types) that says "Check here to show only links to upcoming and past events, but no individual event cards" or something to that effect. It might be worthwhile doing a bit of research to explore whether there's a better or more comprehensive solution that would solve the problem (having more events and wanting to be sure page visitors understand that) better.

Additional context
Add any other context, use cases, or screenshots about the feature request here.

Reference
Jira: https://jira.mass.gov/browse/DP-9633
ServiceNow: SCTASK0050805

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 Organization, Service, and law library page types that display events, along with the Jira and ServiceNow references. Determine how upcoming and past event links are presented and how individual event cards are added. Done means a documented, tested approach lets editors retain the event links while suppressing the individual cards.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.