Create automated sitemap.xml generation for policy/guidance pdfs

[jason-upchurch]

Summary

From #3554, we need to build automated sitemap generation based on existing/added/deleted content and create update policy/schedule, e.g., once per day to be consistent with search.gov

This ticket is presently blocked by #3580, which creates the strategy for dealing with policy/guidance documents in an unambiguous way to enable automatic sitemap generation (which will enable automatic index updating).

Completion criteria

• sitemap.xml is generated correctly based on established convention/strategy

Technical considerations

• ATO
• AWS/cloud.gov v server

[jason-upchurch]

Related issue opened with cloud.gov to consider AWS Lambda or Scheduled Task: cloud-gov/s3-broker#38

[jason-upchurch]

@lbeaufort advised in sprint planning to use caution with respect to this work as it pertains to ATO.

cc @wjiangFEC @PaulClark2

[jason-upchurch]

requesting ATO for review. Issue open with cloud.gov to check feasibility of deploying cloud.gov only solution. Investigating contingency plans, i.e., server based, in the event cloud.gov is unable to support application.

[jason-upchurch]

Issue moved to fecgov/openFEC #4234 via ZenHub