What you should know and check in order to write content****
🏠 HOME
Before
- [ ] Make sure you have read our content styleguide, especially the section about technical content.
- [ ] Make sure you have read the forewords of the section you are going to complete.
After
- [ ] Make sure you do not disclose any sensitive information (table names, credentials). Remember that this playbook is public. That’s why architecture documentation goes into repositories’ wiki.
- [ ] Fill in every section you have created, do not leave placeholders. There is a backlog hereunder for ideas.
- [ ] Make your draft reviewed by the CTO before merging it.
- [ ] Notify the team into the developers channel when you merge a change, so that everybody can immediately enjoy the newly added value.
Backlog
Here is a list of potential additions, pick an item if you feel to:
- [Coding Practices] Peer Programming
- [Tutorials] How to write bugs reports
- Add a “Snacks Bar” section with funny yet interesting resources about web or development
<aside>
<img src="/icons/playback-previous_lightgray.svg" alt="/icons/playback-previous_lightgray.svg" width="40px" /> SSH Tunnels
</aside>
<aside>
<img src="/icons/playback-next_lightgray.svg" alt="/icons/playback-next_lightgray.svg" width="40px" /> Fullstack Traineeship Program
</aside>