Ward explores below how Graphviz Markup Semantics enters into dialogue with how pages are structured.
This work is similar to the work I've been engaged in with creating Page Templates out of federation page-json. I believe there could be considerable benefit in establishing a general set of techniques for marking up pages with metadata the enables the effective parsing of wiki-pages in order to extract data.
In Livecode I've been structuring a Page Model - that is a series of handlers that provide access to building and deconstructing page-json as arrays. this work has been informed in particular through the need of creating places (wike-pages) in the federation where we store information about sites, servers, and authors - that is how we treat wiki as data.
Wards notes below
Small discovery of the day: Algorithmic markup in one plugin interprets the meaning of the remainder of the page which should be designed with this cooperation in mind.
Case in point: Each urban pattern has both a title and an image. I've separated these into an image cluster and a bullet list.
A summary page for related patterns from Michael Mehaffy's Pattern Language for Growing Regions.
This is a mistake. I should place titles under each picture emphasizing the tight relationship. Then I should revise the algorithmic markup of the diagram to read its starting points from the captions rather than the bullet lists as done now. This change will serve to "schematize" the summary pages that will thus feel an organizing pressure from the wiki itself.
# See also