You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Data Processors generate their own documentation (index & license files). Example here.
Boundary Processor sets up the file-structure and also includes boiler-plate introduction html files for the project. Example here.
The original design involved serving these files to enable browsing of the package trees independently (i.e. outside global.infrastructureresilience.org site).
Given we now have improved metadata in the Processor Metadata classes and the frontend is serving this; are the flat html files still required?
Options:
Remove HTML generation completely from all Processors (boundary must still generate the folder structure ofc)
Refactor HTML generation to use templating and new metadata.
Others?
The text was updated successfully, but these errors were encountered:
Data Processors generate their own documentation (index & license files). Example here.
Boundary Processor sets up the file-structure and also includes boiler-plate introduction html files for the project. Example here.
The original design involved serving these files to enable browsing of the package trees independently (i.e. outside global.infrastructureresilience.org site).
Given we now have improved metadata in the Processor Metadata classes and the frontend is serving this; are the flat html files still required?
Options:
The text was updated successfully, but these errors were encountered: