IP doesn’t need to be a dirty word. In this presentation, you will learn about what content developers need to know about protecting and respecting intellectual property rights. You will see some examples of what not to do, and more importantly, learn tips to protect you and your work.
Traditionally, scenarios are used as tools to help users understand a product or task. In our approach, scenarios are internal tools to inform information architecture and are rarely customer-facing.
What’s it like to not just allow community contributions to your documentation, but depend on them? What if literally anybody could edit the docs and see your work as you write? Mozilla doc team members share their experiences working with radically open documentation for end-users and developers.