Versioned and revised ideas for how to run a good tech company.
Edits can just be plain edited. Redactions must be turned into strikethrough and a comment added stating why the text/point is being removed.
Good interview processes and how to find the right people for the job.
As you move your application to production, you will run into problems no matter how great your team is. Make sure you never make the same mistake twice. For this reason, write post-mortems that everyone (across teams) reads, so the company as a whole can learn from it.
Making sure everybody's happy is priority #1 here. We can help achieve this by talking directly to individual team members on a regular basis to ascertain whether they have any annoyances or problems, understand better what they enjoy doing or creating, who they enjoy working with and who they don't.
A list of good questions (or a skeleton plan for these sessions) would be good to work on.
Trainings days, afternoons or even an hour a week can help. Have someone new teach each time. Imparting knowledge to others solidifes it in your own mind. Each session must have ideas for how this knowledge can be applied in the "real" world (laughably vague is fine).
These "training sessions" don't have to be long-winded, well-researched or in-depth, but even sharing a handy CLI tip means that teams get used to sharing information and are encouraged to keep investigating new technologies and methodologies outside of their usual work.
None yet.