...
Status
...
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
...
Type
...
Explanation/Reference
...
Reader
...
Clients / CSMs
...
Reader goal
...
Decide how to pull and sort content for a module, most likely coming from one of these mindsets…
They have a specific idea (use case) in mind – “Can I do this?” If they are tech/design savvy they might look at this on their own. Otherwise, they might ask a CSM, “can I do this?” and the CSM would look at this doc to find the answer.
Or they/CSM have a template or prebuilt module that they want to adjust. “I want to change this default. What are all my options?”
They do NOT want to think about how it all works on the back end. They are focused on use case.
Learning goal: Understand all parts of how content is pulled and sorted. Be able to fill in the “formula” with their choices and hand it to the CSM/Config team
...
Contributors
...
Nelly, Scrilla
...
JUNO version
...
Reviewers (check the box when you’re done!)
...
- Scrilla
- Travis
- Some CSMs
- Leon (just the recommended tags section)
...
Review deadline
...
...
Notes for reviewers
Let me know if anything comes to mind that’d make something easier to understand. 
Thank you all. This one’s a beast!
...
Scrilla, the red section at the bottom is particularly for you.
...
To build your own module, you need to decide which content it will showcase.
...
The goal of this module is: |
Pull these content type(s): This step is required. The rest are optional. Then narrow it down…
Then sort it all by: |
...
| Anchor | ||||
|---|---|---|---|---|
|
...