Closed lijenn closed 7 months ago
MTL Manual TOC draft from Jane: @staceypark
@branscombj Thanks for working on this! @lijenn shared this with us and it looks like a great start. Could you clarify the difference between the content in 4a (tools/resources) and 5 (platforms)?
@lzim @lijenn @branscombj Following the plan for MTL technical manual vs. MTL fidelity manual, here's a new TOC draft for the technical manual:
[ ] ### 1.0 Introduction - Short blub on purpose, how to use manual, etc.
[x] ### 2.0 Learner
[x] 2.1 MTL Red vs. Blue map
[x] 2.2 MTL Blue at-a-glance guide with
[x] - Phase
[x] - Session title
[x] - learning objectives
[x] - SEE guide link
[x] - MTL Video links
[x] - Resources
[x] 2.3 MTL Red at-a-glance guide
[x] - Phase
[x] - Session title
[x] - learning objectives
[x] - SEE guide link
[ ] - MTL Video links - NA
[x] - Learner-only Resources
[x] ### 3.0 Facilitator
[x] 3.1 MTL Blue at-a-glance guide with
[x] - Phase
[x] - Session title
[x] - SAY guide links
[x] - Facilitator-only Resources
[x] 3.2 MTL Red at-a-glance guide
[x] - Phase
[x] - Session title
[x] - SAY guide links
[x] - Facilitator-only Resources
[ ] ### 4.0 Admin
[ ] 4.1 MTL Blue at-a-glance guide with
[ ] - Phase
[ ] - Session title
[ ] - Admin-only Resources
[ ] 4.2 MTL Red at-a-glance guide
[ ] - Phase
[ ] - Session title
[ ] - Admin-only Resources
This looks good to me @staceypark
@lijenn and @staceypark
This is going to be one manual with readers advancing through material based on their role from overview - > highly technical.
note: for most recent instructions 3/4 see main card on this document
1. Link to the document, add relevant team members to the card, and add workflow decisions.
2. Link to issues that must be edited in the document in the issue_tracker and feature_tracker. (use the # for the link to the issue)
dev-test-prod qa cycle
wk2
wk3
wk4
Related issues:
3. Team Review
4. Review and Open Pull Requests (use the # for the link to the pull request)
5. Review and/or Update Graphics
6. Dependencies
7. Close Pull Requests