Add initial jutut instructions

[joni-toivonen]

Fixes #38

Description

What?

[ANSWER HERE]

Why?

[ANSWER HERE]

How?

[ANSWER HERE]

Fixes #

Testing

Remember to add or update unit tests for new features and changes.

• How to test your changes in A-plus
• How to test accessibility

What type of test did you run?

• [ ] Accessibility test using the WAVE extension.
• [ ] Django unit tests.
• [ ] Selenium tests.
• [ ] Other test. (Add a description below)
• [ ] Manual testing.

[ADD A DESCRIPTION ABOUT WHAT YOU TESTED MANUALLY]

Did you test the changes in

• [ ] Chrome
• [ ] Firefox
• [ ] This pull request cannot be tested in the browser.

Think of what is affected by these changes and could become broken

Translation

• [ ] Did you modify or add new strings in the user interface? (Read about how to create translation)

Programming style

• [ ] Did you follow our style guides?
• [ ] Did you use Python type hinting in all functions that you added or edited? (type hints for function parameters and return values)

Have you updated the README or other relevant documentation?

• [ ] documents inside the doc directory.
• [ ] README.md.
• [ ] Aplus Manual.
• [ ] Other documentation (mention below which documentation).

Is it Done?

• [ ] Reviewer has finished the code review
• [ ] After the review, the developer has made changes accordingly
• [ ] Customer/Teacher has accepted the implementation of the feature

Clean up your git commit history before submitting the pull request!

[markkuriekkinen]

The text looks good to me (with couple of small suggestions). If we don't have one already, we should have some sort of acknowledgments section to credit those who have provided input to the manual.

Acknowledgements for the whole project are here: https://apluslms.github.io/about/authors/ It combines people from all components including the Aplus-manual repo.