After writing a mission statement (see #32), write one user persona for MagicBox and tie that persona to our mission statement; publish the persona to our ReadTheDocs documentation
How to do it
Go back to list of users from #32: of those users, choose one whose use case is important and helpful to highlight to a new contributor / team member
Write a persona about one of these users: What do they need from MagicBox? How do they use MagicBox?
Review persona with other team members, get feedback
A persona helps us keep who our users and their needs in mind when developing. A persona is also a story: it's an opportunity to show an outsider how this project actually meets the goals and purpose it meets from our mission statement (#32). This does two things:
Appeals to the unique nature of our project and demonstrate value in contributing
Helps a new contributor understand our project and user needs better
Writing a persona for an important user of MagicBox introduces the project for us automatically through documentation.
After writing a mission statement (see #32), write one user persona for MagicBox and tie that persona to our mission statement; publish the persona to our ReadTheDocs documentation
How to do it
Why do it
A persona helps us keep who our users and their needs in mind when developing. A persona is also a story: it's an opportunity to show an outsider how this project actually meets the goals and purpose it meets from our mission statement (#32). This does two things:
Writing a persona for an important user of MagicBox introduces the project for us automatically through documentation.