Some guides I would like to see (if someone wants to volunteer as tribute 
otherwise I could have a go) on general development.
There is so many things that the team have created/developed/evolved, that would be great to easily share with the community as OpenZeppelin best practice suggestions. I would have loved to know how to get a development environment, style, get test coverage and deploy the OpenZeppelin way.
Development environment
A suggested development environment. nvm, node, npm, Truffle (or Embark), IDE such as VS Code etc.
Style guide and linting
How to use the same style as OpenZeppelin for Solidity and JavaScript (tests) and how to enforce via Linting
Also naming conventions for files e.g. test files.
Test coverage
How to report on test coverage as OpenZeppelin does. Even a line or two on CI setup.
Deploying to testnets and mainnet
Including using Infura, simple things like using .env for mnemonic and Infura API keys. (otherwise pointing to documentation for Truffle)
Contributing
How to get stuff added to OpenZeppelin e.g. a new contract or utility, how to update guides, or even just fix a typo.