New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Figure out how to structure content #2

Closed

smartcontracts opened this issue Jul 16, 2018 · 1 comment

Labels

question

Milestone

Initial release

Member

smartcontracts commented Jul 16, 2018

A proper structure for content will be extremely important. How should we group content?

Some possible "tracks" below? Feel free to comment and give suggestions.

Plasma 101
Plasma MVP in-depth (problem, solution)
"Learn Plasma by building one"

smartcontracts added the question label

smartcontracts added this to the Initial release milestone

Collaborator

barrasso commented Jul 16, 2018

I think that's an accurate content structure for the initial release. A more comprehensive track list may look like the following:

Intro to Plasma (Plasma 101, and explain the differences in naming conventions i.e. Plasma Cash)
Plasma by Example (Plasma MVP deep dive, provide references to other repos and examples)
Security Considerations (explain how to balance trade-offs i.e. security vs throughput)
List of Known Bugs (if any)
Plasma for Developers (highlight our Plasma abstraction toolkit and provide How-To documentation on it)

barrasso mentioned this issue

Added structure for content and documentation #11

Merged

smartcontracts closed this as completed

pet3r-pan mentioned this issue

Pre-requisite / recommended knowledge for learning plasma #75

Open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment