Conversation
reecepbcups
left a comment
reecepbcups
left a comment
There was a problem hiding this comment.
Good work, I know you are refinding more monday but giving a stamp of approval now. will review then or if you want to merge that works too
|
cc @evanorti can you pull over the fix from https://github.com/Lay3rLabs/WAVS-docs/pull/45/files here as well? (both in docs & the main readme) |
|
Note: #164 & Lay3rLabs/WAVS-docs#55 depends on this PR first |
|
TODO
|
reecepbcups
changed the title
|
I am going to change scope of this PR to just the outside docs of 0.4 (not the tutorial). I will do that in its own PR to limit size |
…ties & merge with blockchain interactions
|
|
||
| A component is defined in the [workflow](../workflows) object of the [service.json](../service) file. Below is an example of the different fields that can be defined in the component object. | ||
|
|
||
| ```json service.json |
There was a problem hiding this comment.
It does feel like we define component sources many times. We should link out maybe if we do
service.mdx, workflows.mdx, and component.mdx. or we give just the very specific sections for each at each. I think 1 large service json file would be better utilized
|
Looks good 🫡 Will get the tutorial fix work in another PR |
2 participants
Tagging with todos and creating a new structure for the handbook. I've added some new sections on triggers, manifest, etc.
The service handbook should follow the general structure of the service manifest and explain every part and available options. How it works becomes more like an overview of the pages of the handbook.
Next week we will fill this out more and refine. We can update the sections after changes to the template and wavs are finalized.
Note: The entire tutorial needs to be updated with the new template flow once that is finalized.