3 ms·

I just followed the links, but this seems to have left out specifications.

• O__________O 4y ago
  Interesting point. Generally, in my experience, specifications, that is the documents produced prior to building a system are replaced by the documentation that’s created after the system is built. I have seen some projects try to keep the specs updated, even fewer that try to keep the specs/build/docs in sync via tagging and unique IDs. If the specs were within this framework, my guess is they would go under reference; for example, an API spec would easily be kept in sync and would naturally go under the reference section. In fact, the example given is for a CLI: https://docs.divio.com/en/latest/reference/divio-cli/ https://docs.divio.com/en/latest/reference/divio-cli/
• jimmySixDOF 4y ago
  I agree these don't fit into the 4Ds because the spec is many times the contractual document used for handover compliance line item by line item as part of a larger RFP. Much of it should end up in permanent operational documents but you keep the baseline fixed (with amendments) to compare the original intent against what you end up with. Still, I'm not sure this matters enough to add another D to the taxonomy. If I was to add one it would be D for Diagrams which matter enough to be a category of their own ;}