-
Notifications
You must be signed in to change notification settings - Fork 40
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
Narrow down terminology for news and press pages #461
Comments
For the "Missives" section of the website, we need two pieces of microcopy:
Page titleI've been doing some content auditing, but there's not a great, well-established pattern we can to turn to for content here. So these options come to you only from my brain: Option 1(A)
This is what Jeremy has in as placeholder, and honestly, it ain't bad! Option 1(B)
A flashier version of Jeremy's name (better mouthfeel, I think), but it loses the word "updates." I'm not sure how important that word is, without input from users. If we wanted to do a "lowest fidelity" approach here (like we are with the drop-downs), B is better than A. We could add the word "updates" back, if we find in testing that people can't get there with "Latest" alone. Option 2
Wagtail uses this as their link to highlight release notes, which is a slightly different purpose than what we're going for. But what intrigues me about this approach is that it's more in the mindset of the users we're hoping will click into this section (i.e., people looking to see "what's new" at the FEC). Drop-down contentI wish I could think of a better way to visualize this. Let me know if any of this needs clarification. First drop down
Second drop down
Year fill-in box
Okay! Proposal over. My reasoning follows— Publication type: "Publication" feels more concrete (less abstract) than "update." Ultimately, what we are talking about are different publications, whereas "update type" could many many things, including "publication type." Additionally, the word "Publication" fits better with the mental model that I believe folks will have when they visit this page. Again, research would be helpful here. For journalists: I'm narrowing it down to "journalists" rather than "journalists / press." It's one less word to pay attention to, and I don't think any press member won't be able to identify "journalists" as the correct category. Subject: I think the FEC calls these "categories," but I believe what they are are subjects (please correct me if I'm wrong). Subjects is a more plain English word than "categories," which can mean subjects, but can also mean other things too. Okay! That's it! As always, open to all edits and suggestions. related to: https://github.com/18F/fec-cms/issues/443 cc @onezerojeremy @jenniferthibault @noahmanger @nickykrause |
The time zone difference is really giving me a lot of first responder advantages today. Please folks, I don't think any of you would hesitate to disagree, but just in case: don't hesitate! 😸 Page titleI find the straightforwardness of
to feel consistent with the tone of the rest of the site. Drop-down content
|
Piggy-backing on @jenniferthibault's comment:
As for "the latest" and "latest updates," etc., my vote is for "what's new," because I think that the phrase would be meaningful to users seeking the most recent info, as @emileighoutlaw suggested. "The latest" feels too hip, as Jen said, and "latest updates" feels very useful, but also potentially redundant...? I am in favor of making our best guess and testing it 😄 |
Mostly agree with everything! On whether or not we use "For filers" as a top level holder of the record or not, I think I'm torn.
Little things:
|
Thanks for the awesome thoughts, y'all! Media professionalsLet's do it! FEC RecordIt does feel like overbranding. But SubjectI am always afraid to break with convention, especially for something like my gut. But I'm feeling wild today, so maybe we can try "Subjects" first and see how it goes? |
@onezerojeremy, what about The existing Record page holds that it's:
|
Sorry missed this yesterday @emileighoutlaw: seems good, let's try it! |
@emileighoutlaw I did my best to get the design issues |
I think I got all the relevant content notes into those issues (let me know if you notice something missing, so I can rectify!). Thanks for doing so much initial organization, Jen. <3 |
I think we can mark this issue as done and move all content talk to the design/implementation issues. |
Awesome. Ok to close this issue then? |
omg jinx @emileighoutlaw ! |
Unified language is one of our content principles for this project. In keeping with that, we need to hone in on the lexicon we want to use to discuss our "Missives" section and the things that live there.
Tasks to completion
The text was updated successfully, but these errors were encountered: