[alohaandmahalo]

GitLab team member here. Written communication is vital in a remote company, and makes all types of companies operate more transparently and efficiently.

At GitLab, we don't just document to document. Instead, we recommend a "handbook-first" approach, which we outline here in our public handbook: https://about.gitlab.com/company/culture/all-remote/handbook...

We're also articulate about what we expect in terms of writing style guidelines, part of our Communications handbook: https://about.gitlab.com/handbook/communication/#writing-sty...

[MeetingsBrowser]

This is a great resource! I hope I can convince my team to implement something similar.

I see that the handbook is mostly focused on company level procedures and "What we do". Doe GitLab folow similar principles for documenting code? E.g. Update the documentation for the design before writing code?

[sytse]

Not yet, I'm advocating that our issues for new features should read like the eventual text in the release post.

[benhurmarcel]

Great resources, thank you. This is remarkable that this is public.