Add new "highlights" container layout #1582
Merged
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.
What's changed?
Adds new container layout for use as the "highlights" container.
This is a new container layout intended to only be used once per front, in the first position only. This is intended to be guided by training and not enforcement in the tool.
If the first container on a front has this highlights layout, it will be positioned above the title piece/nav sections on both web and apps to showcase feature stories across the site.
The display on desktop is to show three content items and a "peek" of the fourth item.
On mobile and apps it will display two content items and a "peek" of the third item.
How to test
We deployed the changes to
CODE
. The Config Tool displayed the new layout typefixed/highlights
in the drop down list for layout type properly:The new layout type
fixed/highlights
could be selected:After saving the container, I could see the new layout type in the output file
config.json
in S3:I reopened the config tool and the container was reloaded with the correct
fixed/highlights
type.Implementation notes
When this PR is merged, the new layout type
fixed/highlights
will be available on the config tool, but it should not be used until we support this type of container on web/app.We discussed this issue with the team (homepage redesign) and Jonathan Haynes. Given that the number of people using the tool in production is quite low, Jonathan believed that it should be sufficient just to make front editors aware that this new layout type should not be used for now.
We should inform users (and Jonathan) before we merge this PR.
Checklist
General
Client