-
Notifications
You must be signed in to change notification settings - Fork 381
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Template Documentation #764
Comments
Hi @dansiegel thanks for the feedback. I just made a bunch of changes to runnable projects based on this. The sample I think the only remaining item from your feedback is the PAR page itself. I see what you mean about the format. |
@sayedihashimi that looks a lot better! One minor thing I might add is As for the PAR page, I might add based on the feedback from @mlorbetske in #765
Reading the Wiki documentation on the |
@dansiegel FYI I've added FYI the wiki pages are editable by anyone. If you see anything that can be improved and are up for it, then feel free to go for it. |
I believe these docs have been added, closing. |
@sayedihashimi I was actually just trying to add the Prism Quickstart Templates to the wiki but it's giving me a permission denied error. |
The documentation needs a little cleanup particularly for Post Actions. For example in the "Runnable Project" Templates configuration section there is an example of what a template configuration could look like, and it includes some post actions. Several properties in the example do not meet the official schema which could really lead to some confusion.
Another point of confusion would be that the Post Actions in the sample don't actually make use of a real action in the Post Action Registry. It might also be good to link to the Post Action Registry from the description of the postAction.args. And you're looking at the Post Action Registry there's a lot of (TBD) or text that is larger than the view bounds. Ideally each one should have an example of use as you would see it in the post actions of your template.json
The text was updated successfully, but these errors were encountered: