Closed kbennett2000 closed 6 months ago
Latest commit: |
2cc6961
|
Status: | ✅ Deploy successful! |
Preview URL: | https://b9e16606.documentation-7tp.pages.dev |
Branch Preview URL: | https://kbennett2000-patch-5.documentation-7tp.pages.dev |
Just skipping through this PR, it seems to have overlap with various READMEs in ui-kit
How do we maintain this going forward? And who does the responsibility of updating docs fall on? Does this mean every time @samsiegart add a new ui-component to ui-kit repo, he'd need to also update the .md
file in this repo too?
Just skipping through this PR, it seems to have overlap with various READMEs in ui-kit
How do we maintain this going forward? And who does the responsibility of updating docs fall on? Does this mean every time @samsiegart add a new ui-component to ui-kit repo, he'd need to also update the
.md
file in this repo too?
Good question @LuqiPan, would love to get @sufyaankhan's thoughts on who owns keeping docs up to date as we go. As it stands today, if an engineer creates a new component are they the one responsible for documenting it in the repo?
@sufyaankhan - Where should this go on the navigation?
Link to ui-tookit in Building Client Dapps (https://docs.agoric.com/guides/getting-started/contract-rpc.html) instead of stand-alone doc
Explainer for getting started with
ui-kit