Happy New Year, or should we say year of the Secret Moon
Biz Dev Committee has followed up with an initial offer to one of our most loved community members to continue and accelerate his work on the community developer documentation. Technical writing is one of the most important yet tedious initiatives any community faces, and we’re immensely grateful for Schultzie to take this on. He was kind enough to develop the outline, and general timeline (although please dont hold it against him if its more than we thought) to get our documents up to par and in line with other networks. Please reach out here on the forums with any questions or concerns that we can address.
This initiative is going to be funded by BizDev with rollover funds from our Q4 discretionary fund. All accounting of the discretionary can be found in our EOM reports. We forsee being able to cover 80-90% of this total initiative to start, and will be approaching Secret Labs and the Foundation to discuss covering anything our discretionary cannot before bringing any additional asks on chain.
Longer term (outside of Q1) we hope to continue partnering with Secret Labs to identify a long term resource to continue expanding and updating these documents moving forward as our technology evolves. Each update will require someone like Schultzie to comb through documentation, continually verifying its accuracy and updating for any discrepancies.
If you hang around the dev channels for any length of time, you’ll see it’s not an entirely smooth process for developer onboarding.
With that in mind, I propose a 6-step approach to improving them:
do quick repairs on the docs - make sure links work, nothing is immediately incorrect, etc.
go through the active dev docs (getting set up, creating nfts, etc) with a fine toothed comb via doing them, taking notes, etc. this is going to take by far the longest.
do a thorough analysis of the docs - all cli commands are accurate (and consistent against external sources)
coordinate internal Secret tooling
create a “How to Port your dApp from Terra to Secret”
align Secret dev docs with external cosmwasm dev docs
→ whatever else, if they have it
The developer documentation is insufficient. The biggest pain point for developers is the initial onboarding, and there are 2 aspects to this:
strong documentation so developers know how to get started, and get building fast
a strong community that’s there to provide help
I’m not going to address point 2, other than to say Reuven does an outstanding job while also juggling all of his other responsibilities.
However, for point 1, there’s work to be done. See Near 0, LearnNear 1, and Cosmwasm 2 for a few examples of great documentation. I cannot emphasize LearnNear enough. Developers are paid to take courses, and have access to instructional help. That’s crazy.
…but we’re not there just yet.
In the mean time, point 1 can be addressed and attempted to be brought in line with competitors.
I want to emphasize that this is a long-term project, with many milestones. There are 3 “short-term” milestones, and 3 “long-term” milestones that are broken down by priority levels.
These are milestones that can be completed within a single quarter, at this time Q1 2022.
- Do quick repairs on the docs - make sure links work, nothing is immediately incorrect, etc.
Some of this has been done already 35, but it’s clear that more attention needs done from a quick pass perspective. This is intended as a stopgap solution. Get in, so that while working on 2, incoming developers are in a better state.
- Go through the active dev docs
This is the bulk of the short-term work. It will include going through every single step on all tutorials provided on https://docs.scrt.network/ and Figment Learn | Secret, including fixing and improving upon them. Note that I don’t think figment currently accepts direct fixes, so this will be more involved.
I believe doing every tutorial is paramount to a job well done here, as reading over and reviewing the documentation isn’t the same as executing every command provided.
- Do a thorough analysis of the docs
Finally, this will include comparing the documentation against source documentation, such as gaiacli. With Supernova, much of the cli has been updated and so the documentation is no longer correct. This documentation either needs to be reviewed, re-written, or purged completely. For much of the documentation I don’t see a ton of benefit to keeping what amounts to a copy & paste of the source docs, with gaiacli replaced with secretcli.
These are long-term projects that will likely need to be updated on a recurring basis. These are loose project ideas that can be expanded further, and all would come with their own proposals.
- Coordinate internal Secret tooling
There are a ton of tools that have been built around Secret that aren’t in a unified location for developers to quickly access. These should be coordinated, and documented. Explain how to use them, why to use them, etc. As an example, why is Griptape 6 not referenced?
- Create a “How to Port your dApp from Terra to Secret”
We need more developers. Why not invite those from Terra and other ecosystems to port their dApps, but private?
- Align Secret dev docs with external cosmwasm dev docs
→ whatever else, if they have it
This is a continuation of 5, in a sense. Create documentation that ultimately amounts to “here’s how to make your dApp work on Secret”.
This is a serious undertaking, that frankly, would be best served by a team of engineers and writers. For the purposes of this proposal, I’m going to outline the hours required for the short-term goals, but I’m leaving the long-term goals available for others to take, for the benefit of the ecosystem.
schultzie | Lavender.Five Nodes
- 8 years experience as a software engineer - Authored uncountably many technical and architectural documents, including creating the [Web Map Specification](https://developers.arcgis.com/web-map-specification/) which standardizes 2D maps across all ESRI products and the US Department of Defense - Validator on more than a dozen networks - Member of the Secret Network Infrastructure team - Member of the Secret Network Support team
Hours for part 1: 40
Hours for part 2: 200
Hours for part 3: 40
The following is a rough expectation of timeline, assuming the proposal goes through the week of January 3rd, 2022:
The initial pass will take up to 2 weeks, concluding January 15th
The thorough dev docs will take roughly 2 months, concluding around March 15th
The final pass should take another 1-2 weeks, concluding by April 1st