Elegantly redirects when file or internal link names are changed to prevent broken links. IPFS docs admins shouldn't have to chase this down manually, particularly considering the degree to which IPFS docs will be linked to by others.
To generate related items or automatic cross-linking — particularly useful for related items generated by community (Medium posts etc). Adding this greatly expands our ability to truly hyperlink docs in the long run — plus a good short-term solution for better incorporation of third-party content.
Granular API documentation
Better presentation of API docs, both at an overview/summary level and at a by-command level; note that this may require incorporating an additional tool like Swagger. Better search may ameliorate this to some extent, but we're starting to see widely-accepted and widely-expected UI for API docs, particularly including sandboxing.
Granular CLI documentation
Better presentation of CLI docs, both at an overview/summary level and at a by-command level; note that this may require incorporating an additional tool. CLI docs (as with API docs) are usually either viewed at a high-detail level OR a wide overview level; granular CLI documentation will need to include the best way to address both those use cases.
Inline "try this out" examples that ideally don't require you to have IPFS on your machine; primarily in API docs, but maybe in other areas too. Sandboxing/live coding is quickly becoming "table stakes" for documentation; you shouldn't have to install the thing to play with the thing.
Example ipfs links.
I've just spent 5 minutes trying to find ipfs links which I could paste into Brave to test, but have so far found no ipfs links on the ipfs site. I could be just confused.
Document language selection
Document distinguishing language will make users better read and recognize IPFS, such as Chinese, Russian and so on.
Tutorials & Examples
Stand alone posts that can be used by any one to build something interesting on IPFS from scratch.