Skip to content
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

UG: Write a synopsis section to Comparing Experiments #3160

Closed
iesahin opened this issue Jan 7, 2022 · 6 comments
Closed

UG: Write a synopsis section to Comparing Experiments #3160

iesahin opened this issue Jan 7, 2022 · 6 comments
Labels
A: docs Area: user documentation (gatsby-theme-iterative) C: guide Content of /doc/user-guide

Comments

@iesahin
Copy link
Contributor

iesahin commented Jan 7, 2022

Its too long. It’s hard to make sense w/o additional help /structure.
There should be an overview at the top of it at the very least. E.g. "there are three commands that could help you compare … list, show, diff"; Brief descriptions, links to the subsections...

@iesahin iesahin changed the title Its too long. It’s hard to make sense w/o additional help /structure. There should be an overview at the top of it at the very least. E.g. "there are three commands that could help you compare … list, show, diff"; Brief descriptions, links to the subsections... UG: Write a synopsis section to Comparing Experiments Jan 7, 2022
@iesahin iesahin added A: docs Area: user documentation (gatsby-theme-iterative) C: guide Content of /doc/user-guide labels Jan 7, 2022
@iesahin iesahin self-assigned this Jan 7, 2022
@jorgeorpinel
Copy link
Contributor

Its too long.
There should be an overview at the top

Doesn't that make it even longer? 🙂

It’s hard to make sense w/o additional help /structure.

💡 instead of grouping sections by command, we could consolidate them into major actions e.g. Review existing experiments can cover basic exp show and all of exp list. Feel free to leave some things out from sample blocks (just mention options, etc.)

From #2995 (comment)

@iesahin
Copy link
Contributor Author

iesahin commented Jan 11, 2022

I try to limit the changes per PR to a minimum. In this one, I plan to write a synopsis section. In another PR I'll regroup the sections. And yet in another I'll summarize/rephrase a section. I'd like to make everything in a single pass but IME, keeping the changes limited is essential for quick reviews :)

@iesahin
Copy link
Contributor Author

iesahin commented Jan 11, 2022

Excuse me, this is not a PR, I thought I've submitted it. This can be a tracking issue as well, yes, I'll consider these.

@jorgeorpinel
Copy link
Contributor

On the logistics: small PRs are great, but issue scan be larger. No need to create an issue for every PR I believe.
On the proposed change: If the problem is that the page is long, I'm not sure adding another section (the synopsis) addresses that, unless other parts are removed or summarized at the same time.

@iesahin
Copy link
Contributor Author

iesahin commented Jan 12, 2022

Then you recommend starting from summarizing? @jorgeorpinel

@jorgeorpinel
Copy link
Contributor

jorgeorpinel commented Jan 12, 2022

Yes I would try to address the content structure first which I think is the main issue (going back to #2995). A synopsis may also be useful (Idk) but I don't think it addresses the heart of the matter.

@iesahin iesahin removed their assignment Jan 13, 2022
@dberenbaum dberenbaum closed this as not planned Won't fix, can't repro, duplicate, stale Apr 24, 2024
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: guide Content of /doc/user-guide
Projects
None yet
Development

No branches or pull requests

3 participants