Seeking explanation of the re-org from Pull Request #7 about compliance-masonry

[mogul]

I think you've covered it pretty thoroughly... (It looks like you already found this based on issue #11, but an outline of our thinking is in issue #2.) @RAMIREZG can you comment?

[geramirez]

@gregelin You're absolutely right, we should have been clearer. Like @mogul said you covered the changes thoroughly. Just to add a little more background, the changes you're seeing grew out of a fundamental shift in philosophy.

Originally, the documentation centered the NIST-800-53 controls, which tied Control-masonry to a generic SSP. The new format centers components, which facilitates documentation for various certifications that go beyond NIST and documentation that engineers can better understand.

We also moved to Python because it's more accessible/clearer for data tasks. Soon, we will reconnect the markdown pages, but right now our priority is defining the documentation and its format.

[gregelin]

@mogul @RAMIREZG Thanks for confirming.