Documentation does not scale - support multiple tabs for different aspects. Put the dependencies graph into one such tab. Ideally short abstract and dependencies visible as two side by side open tabs if screen size allows.
could consolidate some existing screen real estate into these
other ideas:
"Conformance" - details of what the bblocks implements (maybe a link to OGC supported conformance patterns how to reference it ?)
"Governance" - who, when, status etc.
"Usage" - configurable call to the KG showing downstream usage?
"Details" - extended description
"Design" - design goals and constraints
"Issues" - possible to pull down open issues referencing this bblock from repo?
should these be user configurable? I think not - these concerns are fairly universal and want to make it clear these are handled consistently
Documentation does not scale - support multiple tabs for different aspects. Put the dependencies graph into one such tab. Ideally short abstract and dependencies visible as two side by side open tabs if screen size allows.
could consolidate some existing screen real estate into these
other ideas:
"Conformance" - details of what the bblocks implements (maybe a link to OGC supported conformance patterns how to reference it ?)
"Governance" - who, when, status etc.
"Usage" - configurable call to the KG showing downstream usage?
"Details" - extended description
"Design" - design goals and constraints
"Issues" - possible to pull down open issues referencing this bblock from repo?
should these be user configurable? I think not - these concerns are fairly universal and want to make it clear these are handled consistently