2019-12-06 | Journal | Weave
I got the intro site up. Now I need to build out the IT org and figure out a way to layer the journal over and among the org in a way that leaves the demo domain and the intro site intact and isolated. Intro and demo only cross-reference each other. Currently the ITD site looks horrible on mobile. I haven't decided if that is OK or not.
I already know that I can layer the journal over the DFD generally. This will lead to another interesting but still valid add. All layers are around the DFD. This includes all layers of the web domains.
Cod and Orng use the predicate "manifests". For instance, I could have a long story about Royal and the laser printer. I could say that the story manifests part of ITD that documents the printer. Manifests uses a symbolic link as an object. It will pull through parts from other domains kind of like how the SVG parts are pulled into the ITD.
Embedded system component diagrams, workflows, and checklists are each generated separately, is my current guess, but I am still unclear how DRY works. I'm doing that thing where I look at it and then go do something else (take a nap, walk, drink a beer in the sun, take a bath, work out, go to bed for the night and sleep on it... almost anything will do as long as it is away from the computer and my mind is allowed to spin off for awhile). The thing is that none of this stuff exists. I can do it anyway I want. What constraints are useful?
I need to get to the point where I can start creating narrative around ITD and fill out the rest of the data flow. It is so boring to do that raw, and, if it is boring to me, it is boring to the reader, probably. The stories will make it better.
Arewedown is operational. It could have workflow, checklists, and system component diagrams, so it is a good guinea pig.
I am re-watching Planet of the Apes, and I noticed that the musical score is sampled by Snake River Conspiracy in Breed.
After much consideration, I arrived at the idea that any kind of graph or anything that can generate the .txt include file, is referenced as a category under 0. They are distinguished by predicates (has_related_dataflow, has_related_system_components, had_related_diagram, etc.). The diagrams can zoom if needed. The rest should work all the same. They can go under graph.
As for the ITD includes from the other site, just add a predicate has_include with a shortcut with an object of a relative link.