-
Notifications
You must be signed in to change notification settings - Fork 394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use-cases: revise so they're more high level "landing pages" #820
Labels
A: docs
Area: user documentation (gatsby-theme-iterative)
C: cases
Content of /doc/use-cases
✨ epic
Placeholder ticket for multi-sprint direction, use story, improvement
p1-important
Active priorities to deal within next sprints
type: enhancement
Something is not clear, small updates, improvement suggestions
Comments
jorgeorpinel
added
A: docs
Area: user documentation (gatsby-theme-iterative)
type: enhancement
Something is not clear, small updates, improvement suggestions
use-cases
labels
Nov 26, 2019
This comment has been minimized.
This comment has been minimized.
jorgeorpinel
changed the title
use-cases: revise so they're all high level
use-cases: revise so they're more high level "landing pages"
Nov 26, 2019
shcheklein
added
the
p2-nice-to-have
Less of a priority at the moment. We don't usually deal with this immediately.
label
Nov 26, 2019
This comment has been minimized.
This comment has been minimized.
jorgeorpinel
added
the
✨ epic
Placeholder ticket for multi-sprint direction, use story, improvement
label
May 7, 2020
9 tasks
jorgeorpinel
added
p1-important
Active priorities to deal within next sprints
and removed
p2-nice-to-have
Less of a priority at the moment. We don't usually deal with this immediately.
labels
Aug 26, 2020
jorgeorpinel
added a commit
that referenced
this issue
Aug 27, 2020
This was referenced Aug 27, 2020
2 tasks
This was referenced May 16, 2021
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
2 tasks
2 tasks
5 tasks
1 task
1 task
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A: docs
Area: user documentation (gatsby-theme-iterative)
C: cases
Content of /doc/use-cases
✨ epic
Placeholder ticket for multi-sprint direction, use story, improvement
p1-important
Active priorities to deal within next sprints
type: enhancement
Something is not clear, small updates, improvement suggestions
Use cases should have a different focus, so they are more high level and serve as landing pages – single web page that appears in response to clicking on a search engine optimized search result – leaving most details to the user guide. Some relevant quotes from #784 (comment):
Note: perhaps we could split this issue into 3. Not 4 because Data Registry is already written in this direction in #818.Ideas:
blog postsuser guide? - how-to: setup a shared cache (extracted from use cases) #2482Extracted to #2490:
QUESTIONED best-practice: dataset partitioning and/or data compression? #682 new case about data partitioning and compression ?The text was updated successfully, but these errors were encountered: