Fec-cms: Design menu option B--change get started language--for usability testing

[AmyKort]

What we're after: We've learned from users that our menus for the data, legal resources and H4CC pages might not be as effective as we'd like in getting folks to the resources they need. We're going to try some A/B testing on alternatives to see if we can learn more about what works for users.

Option B is to change the "get started" language in the menu.

We're going to try changing the language to see if that helps. Completion criteria:

• [x] Draft new languge
• [x] Incorporate into design

[AmyKort]

Looks like we've landed on 'Learn more" for the language change.

cc @patphongs @JonellaCulmer @jenniferthibault

[patphongs]

During design sync, we mind melded on some ideas for testing. There's some subtle differences that we added in here to see how users will do as well as if they will notice the heading links to go to the landing pages more. We didn't change any of the menu options, just added some small text change and visual cues. Here's what we did:

Change 1:
Added » as call to action for the header link

Change 2:
Changed button to Learn more as suggested by the content team

Change 3:
Slight tweaks in the language for the submenu descriptor text because some of them said Learn more already. We chose words like "Explore" and "Find"

[patphongs]

I would say that this is good to go for testing too @JonellaCulmer. Let me know if you need more tweaks.