Why Flow needs a link to scripts article once written
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 81
- PR merge metrics
- No merged PRs in 30d
Description
Reported by: Brian Doyle (<@brian.doyle>)
Issue Description:
Resolve after https://github.com/onflow/cadence-lang.org/issues/265
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the referenced cadence-lang.org issue 265, since this issue is explicitly blocked on it. Once the scripts article exists, locate the appropriate Flow documentation page and add the requested link; the work is done when the link is published and resolves to that article.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100