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

USA.gov Cross-Agency Content Sharing? #15

Open
jpgsa opened this issue Jul 29, 2015 · 2 comments
Open

USA.gov Cross-Agency Content Sharing? #15

jpgsa opened this issue Jul 29, 2015 · 2 comments

Comments

@jpgsa
Copy link

jpgsa commented Jul 29, 2015

USA.gov wants to have API open for submissions from agency partners.
-USA.gov wants to help agencies get more mileage out of content agencies have prepared through their networks.
Is there value in this type of service for agencies? What are the questions? Opportunities? Questions?

@jpgsa
Copy link
Author

jpgsa commented Jul 29, 2015

Notes/Thoughts from July working group call
-What about social media properties?
-yes, social media channels would pull content from agency pieces.
-Cross agency topics may be a good place to explore.
-public API of USA.gov soon, no timeline for agency consumption API,
-Periodical emergencies would be another place.
-Would USA.gov host API's? (not as part of pilot, maybe 18F could help in future?)
-What about editorial decisions?
---potentially could use Digital Analytics Program and other feedback loops like contact center

@lggsa
Copy link

lggsa commented Jul 29, 2015

Here is the outline of our conversation today. We are looking forward to finding answers to some of these questions together.

USAGOV - Who we are

  • Our structured content story
    • our challenges maintaining overlapping content across multiple channels
    • inconsistent user experience
    • desire to expand on early success with paid content syndication
    • implemented a COPE/Adaptive approach using structured content model and single CMS
      • FAQs now incorporated
      • new content model replaces FAQs and link lists; strives to answer one discrete question or issue
      • each unit of content should make experience with gov better

Results:

  • drastic reduction in content
  • ability to organize around topics, and improve content quality
  • reduction in costs from not having to maintain separate knowledge base for contact center.
  • easier to incorporate feedback directly from the public via contact center channels

Vision for USAGOV as a content syndication service for government

  • use this call as sounding board - we’re in very early stages, looking for early adopters to test concepts
  • content types we’re working with now
  • value for agencies
    • strong brand recognition (and working to improve) and good SEO
    • where content may have a fixed audience, and could benefit from exposure to *greater size and diversity
    • spanish language content getting to a broader audience
    • cross-agency topics that can be organized and presented in a way that blurs agency lines - using life events model
    • access to more channels (contact center, social)
    • ability to run campaigns to promote specific issues or programs
    • access to tools to improve quality
      • feedback from the public via site surveys and thru contact center
      • we constantly run ux testing
  • Need help with refining this value, and thinking about questions that would come up, and challenges with operating this model.
  • looking for people who we can have a more in-depth conversation to build out user cases.
  • looking for some who are experienced, some who are new to this

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

2 participants