[DRAFT] Links and metadata for single doc pages #5922
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary (required)
Link to document on standalone document pages now that they pages show up in search results and can be navigated to. Also link the Category button above the title to the parent... filtered page for that
report-type/category/year
Background: These pages are queried to populate a document-feed . The link and metadata the user enters in the fields is used in their listing on the feed. They cannot be navigated to on the site, but because they are a published Wagtail pages, they can now be navigated to when they show up in search results.
Resolves Wagtail Bug: Document Page template pages are showing up in search results #5918
Required reviewers
one content, one UX
Impacted areas of the application
standalone document pages used to populate the feed
Screenshots
Link from title:
Link from document type:
Also can link the category button to filtered parent:
Example:
/about/reports-about-fec/oig-reports/?category=inspection+or+special+review+report&year=2023
How to test
Content/UX :
I can push to dev for testing once PR #5908 is merged
Devs:
report-type/category/year
System architecture updates (if applicable)
(If this pull request changes our current system diagram, include a description of those changes here and create a new ticket to update the system diagram)