Modeling Signal Tower Knowledge with Shapezo: A Structured Content Pipeline for Telecom Assets
Most telecom documentation fails for a boring reason: it is unstructured prose about structured things. A signal tower site is a graph. It has a mast, a compound, a power feed, a backhaul link, a service polygon, and a maintenance schedule, all with relations between them. Storing that as a Word document throws the graph away and leaves you re-deriving it by hand every quarter. Shapezo's answer…
Telecom documentation often struggles due to its unstructured nature, which is a problem when dealing with structured entities like signal tower sites. These sites comprise components such as a mast, compound, power feed, backhaul link, service area, and maintenance schedule, all interconnected in a graph-like structure. By storing this information within the site schema as typed objects rather than in unstructured Word documents, Shapezo aims to simplify documentation creation and maintenance.
The Shapezo model comprises a small site object with four primary entities: site, mast, compound, compound, power, cable entry, service area, terrain, coverage, narrative, and anchor details. The narrative.shape field determines the article structure from a fixed set of options, while the anchor_details field specifies the technical details that the article can delve into. This constraint ensures that the generated articles remain readable.
Rendering the article from the model involves using a template per narrative shape, with each template consisting of sections bound to schema paths. If a slot has no data, the section renders a visible TODO marker, signaling gaps in the article during review. This deterministic output allows for meaningful diffs when a schema change occurs, facilitating infrastructure knowledge review in code reviews.
Image assets are treated as build inputs with contracts, not decorations. Each site declares three slots for images: context, equipment, and consequence. The pipeline enforces geometry and weight constraints on image ingest to keep documentation lightweight, particularly for rural areas with limited cellular coverage. Limiting image sizes to a 200KB budget per image ensures that a full three-scene guide remains under a megabyte, making the documentation affordable and accessible.
The shelter image plays a crucial role in the pipeline, as it serves as a change-detection baseline, given that the compound component changes frequently. By keeping equipment data in the schema, comparisons become straightforward Git diffs of images at a fixed angle, instead of requiring time-consuming archaeology projects.
In summary, Shapezo adopts a disciplined approach to content creation by deciding the shape of the content before writing it and enforcing this decision with tooling. It offers reviewable, complete, and cost-effective documentation for telecom assets like signal towers, where the underlying object is already a well-defined graph.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
