Community outreach (Marketing, Docs, Examples)

[j1010001]

Why (Objective)

To use Cadence to it's full potential, developers need clear content, complete documentation and examples of it's features and how to use them, demonstrating the possibilities.

• Deliver on Crescendo promise - all content owned by Cadence team is updated to cover changes delivered in C1.0.
• Prioritize helping 4D Marketing, Education and Product teams when they need Cadence expertise, so that content production is not blocked.
• Cadence team becoming more familiar with developer journey, so they can better understand developer needs.

How will we measure success (Key Results) ?

• Content production is not blocked by capacity on Cadence team.
• Having visibility into cadence-lang.org usage by integrated analytics tool.
• Cadence-lang.org reviewed & updated - no known gaps in docs.
• Cadence docs linked to examples.
• Submitted Cadence talk proposal to 3 conferences.
• Cadence dev team went through the developer journey end-end.

DACI

Role	Assigned
Driver	@turbolent
Approver	@roham
Consulted	@gregsantos , @SeanRobb
Informed	Cadence team, 4D team

collaboration: Cadence <> 4D <> Marketing <> Education

Beta Give feedback

1. Evaluate Content/Demos for "EVM problems Solved on Flow" #3598
   0 of 1
   +0
2. Support Brian on educational content
3. Sync on tutorials in: Improve Documentation in the leadup to Cadence 1.0 cadence-lang.org#26
4. Event planning (Open-World Builders)

Tasks - Cadence team

Beta Give feedback

1. Review existing content on cadence-lang.org #3606
   0 of 2
   Documentation +1
2. Discovery of gaps in our dev journey (time-boxed, Cadence devs dog-fooding the dev experience) - Join Josh's smart-contract workshop ~1w/developer.
3. Link from Cadence docs to the examples to show real-world usage (Use the existing links from examples to Language reference to link back.) ~1d/d
4. Integrate our docs site with google analytics to track & analyze user actions (reuse dev portal if possible)
5. Re-submitt talk proposal to few conferences (IPFS camp ? - Anthony)
6. Start writing Cadence Whitepaper (Tech Credibility)

Stretch-goals: collaboration: Cadence <> 4D <> Marketing

Beta Give feedback

1. Pick "lighthouse" features (attachments, safe usage of on-chain randomness) and create examples for how to use them
2. Create content for "What you can do with ... feature" (review availablility of examples/content)