Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

So that there is consistency in formatting between FEC publications, enable custom title formatting on FEC Record page CMS templates #1087

Closed
Tracked by #113
jenniferthibault opened this issue May 26, 2017 · 1 comment

Comments

@jenniferthibault
Copy link
Contributor

A funny scenario I just ran into:

On Press release page templates, we have a custom Formatted title field that allows content publishers to italicize court case titles.

  • screen shot 2017-05-26 at 5 59 49 pm

On FEC Record page templates, we do not have that field.

  • screen shot 2017-05-26 at 5 59 27 pm

Often, press releases and FEC Record articles cover the same topic, which means that it's possible to have a Press release and a Record article side by side with mis-matched formatting. (For transparency, I had to try intentionally to make this happen with sorting and filtering, but it is possible to happen through regular search behavior as well.)

  • screen shot 2017-05-26 at 6 00 52 pm

For consistency in formatting, we should enable the custom formatted title on Record templates. To make it one step more user-friendly for content managers, I also think we should move the Formatted title field to be immediately below the page title field, instead of below the body block. This would group fields by the same function.

@dorothyyeager
Copy link
Contributor

Just wanted to say thanks to @jenniferthibault for tipping me off to this github issue. This will definitely be good for the Record and also for any future litigation pages to be designed.

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

No branches or pull requests

3 participants