As a morph, or sub-issue to #46 : Keeping /resources information in one, large YAML file creates a bottleneck when adding or changing various resources connected to the /resources command. To that end, we'll be breaking up the one large file (as suggested by @angelocordon), and we'll need to change the file tree to accommodate this.
As a morph, or sub-issue to #46 : Keeping
/resourcesinformation in one, large YAML file creates a bottleneck when adding or changing various resources connected to the/resourcescommand. To that end, we'll be breaking up the one large file (as suggested by @angelocordon), and we'll need to change the file tree to accommodate this.