This is something that is a WIP and needs maintainer input and adjustment. Hoping to address #1 and #6 with this.
@esodesod I think you can kinda see what direction I am going in. I am inclined to have us have only "1" guide for a .json. It's better to have a longer page that explains everything, than multiple pages about. Makes for easier PR and reviews too.
Ideally, we'd have a PR look like this.
1 item goes into images
1 item goes into templates
1 item goes into template guides
@esodesod We could look at the .json to Publish JS, but as mentioned by Lemons here it does make some assumptions.
This is something that is a WIP and needs maintainer input and adjustment. Hoping to address #1 and #6 with this.
@esodesod I think you can kinda see what direction I am going in. I am inclined to have us have only "1" guide for a .json. It's better to have a longer page that explains everything, than multiple pages about. Makes for easier PR and reviews too.
Ideally, we'd have a PR look like this.
@esodesod We could look at the .json to Publish JS, but as mentioned by Lemons here it does make some assumptions.