-
Notifications
You must be signed in to change notification settings - Fork 406
Closed
Labels
A: docsArea: user documentation (gatsby-theme-iterative)Area: user documentation (gatsby-theme-iterative)C: guideContent of /doc/user-guideContent of /doc/user-guidep1-importantActive priorities to deal within next sprintsActive priorities to deal within next sprintsp2-nice-to-haveLess of a priority at the moment. We don't usually deal with this immediately.Less of a priority at the moment. We don't usually deal with this immediately.✨ epicPlaceholder ticket for multi-sprint direction, use story, improvementPlaceholder ticket for multi-sprint direction, use story, improvement
Description
Extracted from #2548
Review/consolidate these:
- index and Overview pages - should be about bigger picture, general workflow diagrams, benefits, etc. Help users better navigate in the section structure (e.g. map subsections to the workflow).
- Index: Do we need Organization patterns and Run-cache sections?
- guide: Naming experiments section or page #3106
- guide: Running Experiments improvements #2768
- & mention that untracked files can slow the exp commands {BECAUSE ...}
- guide: "Comparing Experiments" improvements #2995
- guide: concerns with "Persisting" experiments #2960
- Longer
exp initsection or its own guide (currently in the ref.) Perhaps even reuse/rename Exps Overview.
See possible structure + other possible pending questions. - Reorganize Sharing Experiments completely: it's like a cmd ref. at the moment (too many linear sections).
See guide: revisit Exp Sharing #2908 (comment) - guide: "Cleaning-up Experiments" improvements #2777
- guide: revisit Checkpoints guide(s?) #2769
- and/or guide: all the ways to use checkpoints #2432
- ref:
exp run --set-paramwith templating #2313 (could be included above) - Use the term "experiment tracking" more? We currently focus on "experiment management" and throw "tracking" here and there but never use the full phrase, which is a well-known concept in the field (so good for SEO) and relates to many of our guides, probably.
From guide: concerns with "Persisting" experiments #2960 (comment)
See also guide: DVC Experiments Overview #2909 (review) - Create a diagram for different
expworkflows? (at least the basic one)
See guide: DVC Experiments Overview #2909 (review)
and guide: DVC Experiments Overview #2909 (review). -
exp: baseline -> parent [term] #3432 -
exp: CI runs require unshallow clone (fetch-depth: >1) #3416 ?
Metadata
Metadata
Assignees
Labels
A: docsArea: user documentation (gatsby-theme-iterative)Area: user documentation (gatsby-theme-iterative)C: guideContent of /doc/user-guideContent of /doc/user-guidep1-importantActive priorities to deal within next sprintsActive priorities to deal within next sprintsp2-nice-to-haveLess of a priority at the moment. We don't usually deal with this immediately.Less of a priority at the moment. We don't usually deal with this immediately.✨ epicPlaceholder ticket for multi-sprint direction, use story, improvementPlaceholder ticket for multi-sprint direction, use story, improvement