Skip to content

Conversation

mandylloyd
Copy link
Contributor

@mandylloyd mandylloyd commented Dec 6, 2024

Summary

Add a changelog for PR uswds/uswds#6205

Important

We need to update the changelog dates before merge.

Preview link

In-page navigation changelog

@mandylloyd mandylloyd changed the title USWDS-Site: Add changelog for in-page navigation [#6205] USWDS-Site: Add changelog for in-page navigation Dec 6, 2024
@mandylloyd mandylloyd changed the title USWDS-Site: Add changelog for in-page navigation USWDS-Site: Add changelog for in-page navigation [#6205] Dec 6, 2024
@mahoneycm
Copy link
Contributor

Todo: Update guidance to include this new data attribute

Copy link
Contributor

@amyleadem amyleadem left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this, @mlloydbixal! I added a comment below with some suggestions for copy updates.

Can you also add documentation for this new setting on the settings page and in the settings table on the in-page navigation page? Whoops, I mean can you add this prop to the "In-page navigation initialization properties" table?

Let me know if you have any questions.

Comment on lines 6 to 10
summary: Hide in-page navigation when there are fewer than 2 headings.
summaryAdditional: The `data-minimum-heading-count` setting determines when the in-page navigation should be displayed or hidden if the minimum number of headings is not reached. Previously, in-page navigation was shown even when there were no headings, resulting in an empty component. This setting can be customized.
affectsGuidance: true
affectsJavascript: true
affectsMarkup: true
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: Update the focus of the summary to highlight that this is a customizable setting. I also made some suggestions to change the "affects" tags here. Here is a possible rewrite:

Suggested change
summary: Hide in-page navigation when there are fewer than 2 headings.
summaryAdditional: The `data-minimum-heading-count` setting determines when the in-page navigation should be displayed or hidden if the minimum number of headings is not reached. Previously, in-page navigation was shown even when there were no headings, resulting in an empty component. This setting can be customized.
affectsGuidance: true
affectsJavascript: true
affectsMarkup: true
summary: Added the `data-minimum-heading-count` setting, which hides the component when the content region does not contain the minimum number of headings.
summaryAdditional: By default, this setting hides the in-page navigation component when there are fewer than two headings in the content region. Teams should customize the value of this setting based on their content needs.
affectsJavascript: true
affectsSettings: true

Copy link
Contributor Author

@mandylloyd mandylloyd Jan 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in af55dd9 and 464f531 :) thanks!

@amyleadem amyleadem changed the base branch from main to release-3.12.0 January 9, 2025 19:08
@amyleadem amyleadem marked this pull request as ready for review January 22, 2025 22:55
@amyleadem amyleadem requested a review from a team as a code owner January 22, 2025 22:55
@amyleadem amyleadem merged commit daddd81 into release-3.12.0 Jan 22, 2025
0 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants