PD Module implementation v0
aka: Entities / Generators / Building blocks
This is a heavy weight issue with a large scope. Must ensure we're on the right path towards a v1.
Discussion points
-
Module dependencies / linking ?_? -
Can use use and rely on existing infrastructure such as NPM? -
What are NPM alternatives? -
Module loading priority -
3rd-party module ratings? Based on health/compliance/etc?
Easy to
-
Create -
Install -
Maintain -
Preview -
Link/stack
List / META
-
Author/Title -
Taxonomy - Entity, generator, transformer, DOM, nav, geo etc... -
Dependencies -
Required -
Optional
-
-
Priority # (lower = higher priority for INIT etc) -
Worker/parallel Y/N -
Permissions - what access does it and it's dependencies require? -
state/db access limits, prevent rogue modules from accessing entire state chains. -
Optional permissions
-
-
Affected domains / limits d::Library d::Framework d::Platform C::BuildDeploy etc -
Render -
Static (prerender safe, long term cacheable) -
Dynamic (potentially safe) -
Live (on demand, no prerender, client cache?)
-
-
Compliance -
accessibility WCAG -
C::i18n -
legal Distribution license, OS/Proprietary -
Presets via Software Package Data Exchange (SPDX) License List?
-
-
legal GDPR, other compliance frameworks (SOC2, ISO27001, HIPAA...)
-
-
Edition limitations ed::Community / ed::Pro -
Pricing (ed::Pro only?)
Nice to have
-
d::Framework Control panel: Name, version, license, source link
Edited by Lorin Halpert