massgov / massgov/feature-requests

Relocate "associated pages" module for Events to more prominent tab

Open
#149 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

When creating an event, a user needs to explicitly note what pages the event will appear in. This is done in a new event draft by clicking the **Related** tab and populating fields with nodes under **Associated pages**, which is required for publishing.

For the majority of the content types, "Related" tends to mean "everything we couldn't put in the previous tabs; kind of a miscellaneous catch-all for information we need to add to the page. For something as pivotal as, "The event needs to show up on THIS page." I feel it needs a more prominent spot in an earlier tab (Overview or Details).

This will require some thought because under **Overview**, there are a number of areas dealing with Organization pages:

1. Participating organizations
2. Organization(s) (for relationship indicator)

It may be a bit confusing to have so much attention paid to _Organization_ pages; order will matter and so will subheadings.

I recommend considering moving **Associated pages** to an earlier tab and renaming it to "Pages for displaying event" or something like that. "Associated," to me, isn't descriptive enough (until you read the help text -- "Please select the page(s) where this event should appear.")

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

Review the event creation flow, especially the Related, Overview, and Details tabs, and compare the Associated pages fields with the organization-related fields. Clarify the preferred tab, ordering, and label with project stakeholders. Done means the placement and wording make the publishing requirement prominent without confusing it with organization relationships.

Written by the indexing model from the issue text.

Assessment

Domain
design
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.