onflow / onflow/docs

[Epic] Technical credibility content

Open
#931 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
13
Forks
81
PR merge metrics
No merged PRs in 30d

Description

Why

How will we measure success

DACI

D: Various
A: TBD
C: TBD
I: TBD

Problem definition

Flow's needs to improve it's technical creds in the industry through publishing content which surfaces the advanced capabilities of Flow and to highlight different areas of strength and other improvements to various audiences

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

This epic names no files, tests, or entry points, so first clarify the intended content scope, audiences, success measures, and DACI ownership. Done requires an agreed plan for publishing content that demonstrates Flow's advanced capabilities and areas of strength.

Written by the indexing model from the issue text.

Assessment

Domain
content, documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.