#388 recently made it possible to list html assets which should be explicitly tracked through scripts/pre-build/library/.tracked-html-assets.json. Currently there are strong expectations of certain html documents.
For example, a pattern called 'sample' would be located at content/patterns/sample/sample-pattern.html but there isn't an expectation for there to be content/patterns/sample/sample-support.html. Same with there being an expectation of a practice called sample having a content/practice/sample/sample-practice.html.
This will create build issues for continued APG contributions should additional unexpected files be added in, with the bottleneck being to add to that list here. To continue having efficient contributions against the APG repository, that list of 'tracked' html assets should be done from the APG repository.
#388 recently made it possible to list html assets which should be explicitly tracked through scripts/pre-build/library/.tracked-html-assets.json. Currently there are strong expectations of certain html documents.
For example, a pattern called 'sample' would be located at
content/patterns/sample/sample-pattern.htmlbut there isn't an expectation for there to becontent/patterns/sample/sample-support.html. Same with there being an expectation of a practice calledsamplehaving acontent/practice/sample/sample-practice.html.This will create build issues for continued APG contributions should additional unexpected files be added in, with the bottleneck being to add to that list here. To continue having efficient contributions against the APG repository, that list of 'tracked' html assets should be done from the APG repository.