neo-technology-build-agent
commented
2 years ago 
Having a section of APOC docs that are sort of like a FAQ would be useful. For example, people use apoc.periodic.iterate to overcome OOMEs. They don't search for apoc.periodic.iterate, they search for solutions to OOME.
So a very short "cookbook" would be nice.
- Have problem X? Look at apoc.foo.whatever();
- Have problem Y? Look at apoc.bar.magic();
Second idea -- curated blog posts. A lot has already been written about APOC. Some probably has aged out of usefulness. Some might get referred to a lot by people. Help boost the non-APOC documentation by linking useful resources for further learning / tutorials. This gives more official stance to the best blog posts, and drives more traffic to them, improving APOC documentation and understandability without changing much.
Third idea -- "apprentice tasks". Some good open source repos I've seen have issues that are filterable by "how hard is it to do this". They have some small documentation tasks as apprentice tasks because it's an easy approachable way for someone new to contribute without knowing all the stuff really deep. So one thing to improve collaboration is don't write all of the docs, but have a list (like what you have here) that's always available so a newbie can tackle a simple issue, learn more, and contribute. "Wantlist" for documentation if you will.
Sections
Schema
Data Integration
-> Export/Import -> CSV/JSON/XML/XLS/GRAPHML -> Databases -> RDBMS/Mongo/ES/Couchbase/Bolt -> Geospatial
Conversion
Graph Refactoring
Path Finding
Virtual
Utilities
Cypher Execution
Operational
Indexes (deprecate)