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
There are a lot of different workflows that this template offers. Would like to update the README.md (or better yet set up a docs website with vocs) to describe and offer direction on different workflows:
What to update when changing the packages/contracts structure
What to update / do when adding new components to packages/ui
Setting up an appropriate anvil network on popular browser wallets when applicable
Updating apps/ponder to use a REST api rather than the default configuration (which uses GraphQL)
Appropriate workflows for testing packages and/or apps in isolation when applicable
These are just a few of the different workflows that could / should be described. The ultimate goal of this starter kit is to provide not only a great scaffolding that uses cutting edge software, but also provides guidance for those that may have limited experience with certain pieces of software that this monorepo relies on.
There are many angles to consider here, so I am very much open to discussion and will keep this issue open as more workflows and ideas come about!
The text was updated successfully, but these errors were encountered:
Description
There are a lot of different workflows that this template offers. Would like to update the
README.md
(or better yet set up a docs website withvocs
) to describe and offer direction on different workflows:packages/contracts
structurepackages/ui
anvil
network on popular browser wallets when applicableapps/ponder
to use aREST
api rather than the default configuration (which usesGraphQL
)These are just a few of the different workflows that could / should be described. The ultimate goal of this starter kit is to provide not only a great scaffolding that uses cutting edge software, but also provides guidance for those that may have limited experience with certain pieces of software that this monorepo relies on.
There are many angles to consider here, so I am very much open to discussion and will keep this issue open as more workflows and ideas come about!
The text was updated successfully, but these errors were encountered: