Publish resource for non-federal agencies

## User Story

In order to get their data on catalog.data.gov, non-federal agencies would like a resource that describes how the process is different for non-federal agencies.

## Acceptance Criteria
[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using [BDD](https://en.wikipedia.org/wiki/Behavior-driven_development#Behavioral_specifications).]
- [ ] GIVEN [a contextual precondition] \
[AND optionally another precondition] \
WHEN [a triggering event] happens \
THEN [a verifiable outcome] \
[AND optionally another verifiable outcome]

## Background
[Any helpful contextual notes or links to artifacts/evidence, if needed]

While not required, non-federal agencies, like federal associations, state and local governments, and educational organizations are included on catalog.data.gov. Some required fields (`bureauCode`) are not applicable to non-federal agencies. There is also a concept of a [non-federal schema](https://github.com/GSA/ckanext-datajson/tree/master/ckanext/datajson/pod_schema/non-federal-v1.1) used to validate non-federal agencies.

## Security Considerations ([required](https://nvd.nist.gov/800-53/Rev4/control/CM-4))
[comment]: # "Our SSP says 'The Data.gov team ensures security implications are considered as part of the agile requirements refinement process by including a section in the issue template used as a basis for new work.' so please don't remove this section without care."
[Any security concerns that might be implicated in the change. "None" is OK, just be explicit here!]

## Sketch
[Notes or a checklist reflecting our understanding of the selected approach]I