hirosystems / hirosystems/hiro-experience-map
Lack of intentionally designed transitions or handoff between our core products in order to push developers towards the next logical step in their developer journey, or to encourage the use of particular Hiro tools/services at each stage. (eg Docs → Playground, Docs → Platform, Playground → Platform)
Open
Clarinet
Docs
Hiro.so
Platform
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
This issue has no description.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.