Closed janmiderback closed 6 years ago
We probably discussed this before, and I'm fine with either, but let's be consistent with calling them "use cases" or "(live) demos". Whatever we choose here is what we internally should call them as well (up to now, it's "use cases").
Overall it looks good to me. Some suggestions:
Start with the business problem, since it affects how we solve things (e.g. the architecture diagram) and gives the user some initial bail-out time (i.e. "is this going to be interesting to me").
Maybe a section about cost, and if there are certain aspects of the use case that was considered, and what future problems it might hold that can be worth considering during design of a similar use case.
I'll add more if I come up with it later.
Good points. If we have settled for "Use Cases" then we should stick to it. Personally, I feel that the term "use case" is a bit misused here, why I favor "Demo" or "Live Demo". Updating suggested order.
After some thought, I think we should stick to "Use Cases". Updated.
Great summary @janmiderback. I like the suggested above! Keeping the overview page short is a good idea since we most probably will add more use cases later.
This looks good to me! Thumbs up for the term "use cases" and having business problem first in the use case section.
Spawning out other tasks from this. Closing.
Update the Qlik Core documentation to cover our two Use Cases:
Suggested Changes