Make JSON config files more findable

[kgudel]

Currently there are a number of json, human readable, config files that the frontend picks up and uses for documentation and other copy on the site.

These config files are intended to be able to be editable by non-developers. There is good documentation on how to find these files, however, it would also be useful to have these files be more findable simply through the file structure of the project rather than having them buried in the src files of the code.

As such, it would be helpful to have something like a centralized folder at the top level of the directory structure where you can find all of the files meant to be editable by non-developers.

[meissadia]

One small road bump here is that those files need to live under the /src directory in order to be built into our React app. Perhaps we could work around this by adding a pre-commit hook that copies the requisite files into the src directory.

Thoughts:

• Maybe an admin tool to edit these files?
• Move this content to an API? w/ an admin tool
• Smaller fix: Direct links from the documentation to the files?
• Internal docs: Make a TOC of how-to-edit's and their source files, for configs that are commonly edited

[meissadia]

I actually don't see any mention of the config files in the Frontend README, so that is one thing I can update.

• add config locations
• add documentation of each config key

[meissadia]

Config docs live in the repo wiki: https://github.com/cfpb/hmda-frontend/wiki/Front-end-Configuration

[meissadia]

As discussed during Sprint Planning, in practice these files are never modified by non-developers. We have scripts to generate PRs for common modifications, such as maintenance announcements.

Maybe moving files to /src/config from /src/common/constants/ would improve discoverability, but again, only frontend devs actually directly edit these files.

Dropping this back into the Backlog for now.