Closed LockerM closed 1 year ago
Was discussed separately that SAMPLE is mostly used for code rendering and not representative of a 'preview' set of Powers or Beasts. Resolving issue for now and can discuss separately how we'd like to highlight a sampling of powers and beasts while keeping a larger development list separate.
Suggestion
Rather than managing a separate YAML file for SAMPLEs and needing those sample files rendered separately we could just have a tag or category or attribute that can be read and rendered by a sample page output script.
If it would work as a category, where one -option is
- Sample
and have the yaml to other files read that category to generate a sample list. Or we can create a new field in the YAML dict that is Sample: True, and if blank or False don't render on the Sample page.Value-add
This way any small tweaks to the core code are rendered automatically for the sample and we can make the sample bigger or swap items on it more easily by just changing a tag or category in one file rather than maintaining multiple files that may develop inconsistencies during the testing and development phases.