List view
Host all IPFS documentation within one place. A lot of individual IPFS projects have documentation all over the place, JS-IPFS, and Go-IPFS in particular. This makes it convenient for the devs to create docs but makes it tricky for users that need to access or find those docs in the first place. Having all IPFS documentation in one place keeps things tidy, consistent, and makes the user experience much better. Instead of having to jump around GitHub repositories and blog posts, readers can head to docs.ipfs.io and get all the information they need.
No due dateAutomatically check the documentation for broken links, broken assets, spelling mistakes, and grammatical issues. A substantial amount of time is spent checking for spelling and mistakes when writing documentation. Once the docs are written, links and assets need to be tested to make sure they're not broken. While the sidebar navigation in VuePress handles broken-links very well, the body content of the docs doesn't have any process to check links. These three things are automatable. The grammar checker will likely require a substantial amount of work; however since there doesn't seem to be any decent automation too already to deal with that.
No due dateThe new [docs-beta.ipfs.io](docs-beta.ipfs.io) site has been live for a few months now, allowing real-world user testing to take place. The site is now in a position to completely replace the legacy [docs.ipfs.io](docs.ipfs.io) site. The planned deprecation date is Friday 15th May 2020. Work will still continue under this milestone until the end of May.
Overdue by 5 year(s)•Due by May 29, 2020•15/15 issues closedAs time permits these are the top tasks to take on in Q1 2020
No due date•3/3 issues closed