Reference
| Document status | |
|---|---|
| Release status | |
| Related pages | Insert links to specification docs |
Milestones
| Start date | Oct.10, 2018 |
|---|---|
| Release from development | TBD |
| Release | TBD |
Development team
| Developers | Project manager | Page owner |
|---|---|---|
| Kelly Foster | Kelly Foster |
Marketing team
| Marketing lead |
|---|
Release summary
Simple overview
The goal of this project is to publish documentation of Rholang's syntax and semantics.
Technical overview
Provide a high level overview of what is launching for a technical audience. Don’t oversell and make sure it’s credible to developers. If we say that the feature does X, then we need to provide the data to prove it. What will this release not do?
Metric for tracking success
What is special about this release?
Are we launching anything different than what’s out there? If so, what is it and how is it different? Use the ‘peel the onion’ approach, “there are three reasons why this feature is unique / 1 short sentence for each / 3-4 sentences about each vs. immediately going deep into the feature.
Are we doing something differently? If so, why are we doing it this way?
If developers need to do something new/different to take advantage of this launch we should explain why we’re doing it differently to get them to buy into it. For example, why do we need a new language and why is it implemented in a specific way?
Before these features were available, what were developers able to do with RChain?
Provide an overview of what developers were able to do without these new features. Please write this from the end user perspective.
After these features launch, what will developers be able (and not able) to do with RChain?
Provide an overview of what developers will be able to do after the new features launch. Please write this from the end user perspective. For example, after we launch the SDK dApps developers can run the RhoVM to create their first dApp on RChain.
Description of release packaging
Where do developers go to learn more and get started?
CTA and link to the appropriate spot that marketing needs to point developers to.
Where will bugs be filed?
Where do developers go for support? What is the SLA? Who is on point?
What license will this be released under?
Jira issues related to this work
