You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I was adding docs for the website of the governance contract #36 . But felt i was repeating a lot the documentation and wondering how that could be improved.
Describe the solution you'd like
I would like to directly generate the website docs from the Rust code docs. Rust docs are awesome and allow markdown. So i think they could be the source of truth and generate the website ones from them.
Describe alternatives you've considered
To invoke a script that parses the current rust docs rust docs and places a copy in the vercel app folder. This could be triggered by the CI.
It could be good to stablish a custom convention inside Rust docs convention. If done, it would favour the case in which we point the Wizard UI to other contract catalog and is able to load the example commands (now in rust docs) for the invoke buttons.
Is your feature request related to a problem? Please describe.
I was adding docs for the website of the governance contract #36 . But felt i was repeating a lot the documentation and wondering how that could be improved.
Describe the solution you'd like
I would like to directly generate the website docs from the Rust code docs. Rust docs are awesome and allow markdown. So i think they could be the source of truth and generate the website ones from them.
Describe alternatives you've considered
To invoke a script that parses the current rust docs rust docs and places a copy in the vercel
app
folder. This could be triggered by the CI.It could be good to stablish a custom convention inside Rust docs convention. If done, it would favour the case in which we point the Wizard UI to other contract catalog and is able to load the example commands (now in rust docs) for the
invoke
buttons.Additional context
The text was updated successfully, but these errors were encountered: