Skip to content
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.

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

DevDocs Budget Request #223

Open
16 tasks
rossgalloway opened this issue Jul 19, 2024 · 1 comment
Open
16 tasks

DevDocs Budget Request #223

rossgalloway opened this issue Jul 19, 2024 · 1 comment
Labels
approved An approved budget request budget request A budget request

Comments

@rossgalloway
Copy link

Scope

This budget request is to continue the Yearn documentation effort. I have worked as the devdocs maintainer for the last 3 months (BR here) and would like to continue with my efforts to improve and expand upon Yearn's documentation. A report of the work I have done over the last 3 months can be seen here.

I will continue to maintain and improve Yearn's documentation and knowledge base, including continuing to stay in contact with those building V3-Vaults, yLockers, yETH, veYFI, yDaemon, the subgraphs, and any other initiatives that need documentation. I will continue with my efforts to improve the flow and usefulness of the docs for all users and contributors.

The devdocs are currently in a state where they are functional and have lots of information on the multiple parts of Yearn, but this information is fragmented and sometimes outdated or inaccurate. The organizational structure is haphazard and reflects the peicemeal way that information has been added over the years. By consolidating, updating, and improving on the docs, there is an opportunity to fill a missing piece of Yearn's information ecosystem: The passive sales and marketing domain that is not captured with the dApp and out of scope of the social channels.

As @MarcoWorms is moving on, he will be transferring the github repo permissions to me to continue the work. We have discussed keeping him on as a reviewer. I would also like to distribute review responsibilities to stakeholders in different teams as needed for their documentation (this usually happens anyway).

My requested compensation is bumping up from the initial "trial period" rate that I requested in my first BR.

Plan

Baseline Tasks:

  • Continue to learn about Yearn's documentation and organizational structure to improve all aspects of documentation. This involves research and discussions with contributors about different parts of Yearn as I update the documentation on those elements.
  • Continue to maintain the current yearn-devdocs while adding and improving the documentation for new products (vaults v3, yETH, yLockers, yPools, etc.)
  • Work with ySupport to keep User guides up to date and relevant
  • Confirm move to new versioning system for the website and assure stakeholders are aware of how this has changed. Write docs to document new process.
  • Finalize updating the algolia script to automatically re-index upon master branch pushes. Troubleshoot issues as they come up/ (PR #439)
  • continue to maintain and improve the backend infrastructure for the docs. Keep dependencies up to date and add new features as needed.
  • New page focused on wallet and asset aggregator integrations. (Issue #416)
  • Fix github linter check that always fails on deploy when relative links are used.

Improvement Tasks

  • Continue working on the "DevDocs Revamp" organizational changes. See this presentation
    • Solicit comments on current re-design
    • Implement changes from comments on re-design to dev branch.
    • Implement approved changes to master branch cleanly
    • Add quality of life improvements. Better links, graphics, marketing copy, etc.
    • Flesh out yearn landing page with additional copy, images, etc to serve as a general landing page for new users.
    • Work on splitting out important information about products in user docs (layman audience) and dev docs (technical audience).
  • Update DAO/contributor docs to reflect current working practices of the DAO and governance process. Futureproof for new changes in veYFI and on-chain voting. veYFI docs page needs lots of work to be understood by the average user.

General

  • Assist with community management as needed on discord and telegram. This helps me understand user needs and what is lacking.
  • Tackle all other challenges that may come up throughout the work with enthusiasm and a "can-do" attitude.

Deadline

2024-10-31

People

Money

  • 7.3k DAI in yvDAI and 0.4 YFI, per month

Split

  • 6.3k DAI and 0.3 YFI per month, for @rossgalloway (maintainer)
  • 1k DAI and 0.1 YFI per month, for @MarcoWorms (reviewer)

Amount (Total)

21.9K DAI and 1.2 YFI

Wallet address

TBD - need to create multi-sig?

Reporting

Once

@rossgalloway rossgalloway added the budget request A budget request label Jul 19, 2024
@github-project-automation github-project-automation bot moved this to Needs Sorted in yBudget Jul 19, 2024
@0xPickles 0xPickles added the approved An approved budget request label Oct 7, 2024
@rossgalloway
Copy link
Author

rossgalloway commented Oct 25, 2024

End of Period Report

Implementation of the "Devdocs Revamp" reorganization has been completed in that all the big changes are complete. Styling is updated, docs are split into user, dev, and dao sections, sidebars are more intuitive. Natspec docs are re-organized and there is a new workflow to generate docs more easily.

As a reference, this is what the docs looked like before: https://yearn-docs-ba94fydb3.yearn.farm/
This is what they look like now: https://docs.yearn.fi

Content Updates

Implement Styling and Design Changes

Quality of Life Changes

Misc other Work

  • Research on new Kong public API to create future docs.
  • Built Yearn-Charts interface to learn about and use the new Kong API.
  • Assistance in discord for user problems.
  • I helped the Sonne Depositors group with navigating the governance process.

There are some elements I didn't get to:

  • A new page for wallet integrations (pushed to next BR)
  • Update linter in build step (pushed to next BR)
  • Update landing page further with more info and to serve as general landing page. (not sure if this is actually valuable and needed.)

Other work still pending:

  • top 2 items in above section
  • Improved DAO Docs
  • Improved Guides
  • Kong Public API documentation
  • Continued Subgraph docs improvement
  • Port v3 natspec documentation flow to v2.
  • Coordinate with SAM to update risks and security sections.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved An approved budget request budget request A budget request
Projects
Status: Needs Sorted
Development

No branches or pull requests

2 participants