Hey prospective content writer,
We would really welcome you to come and lend your writing skills for DevDAO Academy (DDA in this doc) education platform we are building out.
What follows, is quite a long read, but we feel it necessary to communicate clearly and thoroughly, why the team started, what we wish the project to achieve, how, with whom, in what form and at what stages. We will discuss $CODE rewards and how you submit your work, writing guidelines to reduce the need for long review processes, what is urgent right now and also office hours, all to ensure successful collaboration with you and success for the platform. Please read and understand this document first. It’s a bit messy, but it’s iteration!!
n.b. urgency: we are releasing an MVP (minimal viable project) on September 20 2022
Table of contents:
- Please, “don’t make assumptions”, one of this project’s core values, and read the whole doc 😊
- What makes DDA different from the competition? Potentials for the future.
- For content writers/reviewers: Skill sets we have in-house, roots of our strategy, solving problems through ‘how’ we write and map out the platform.
- For content writers/reviewers: What we need - high level. MVP structure of content: Project track + Fundamentals track. Journey to modular content.
- $CODE Rewards, how to find and submit work, office hours & synchronous support
- Support channels for contributors
- Trimming the review process. Successful content examples and reviews you can use as reference.
- Finally!!! What content can you write or review for DevDAO_Academy, for each lesson??? See what is needed from Lesson 1 through to Lesson 5
How does DDA differ from other DAO web3 learning projects and internet competitors?
Selling points for the platform in simplest form i.e. learning to code:
- our goal is to have content that is representative of the real world, e.g. not just snippets but full [comprehensive] examples.
- all-in-one learning hub allowing for:
- minimal distractions, so no need to visit other sites to find answers.
- people can focus on content, with fundamentals' drawers as needed.
- each lesson has a forum. Reliable answers.
- healthy learning env, hence pomodoro.
- skills badge / competency
- user-profile / digital ID / holds all skills / other systems can import into their system
- Integration of existing tooling DeWork, Github, Coordinape,
- Potential for platform beyond MVP:
For content writers/reviewers: Skill sets we have in-house, roots of our strategy, solving problems through ‘how’ we write and map out the platform
- Some insight into our beginnings might help start answer that.
For content writers/reviewers: What we need - high level. MVP structure of content: Project track + Fundamentals track. Journey to modular content ****