Jorge Orpinel

> dedicated page for each implementation (not only target envs, but other base classes too) Agree: https://github.com/iterative/mlem.ai/issues/143 Documenting all existing config options may also help us design a more segmented...

p.s. there's no verbose output option right? (like `dvc ... -v`)

> There is mlem --tb ... option Should we consider changing that to `--verbose` (`-v`) for consistency? (with `dvc` + think it's pretty standard). > very hard to wrap each...

May be related to #267 as well.

I guess this is related to https://github.com/iterative/mlem/issues/233 ? If so cc @dberenbaum I'm not sure I'm getting this mlem declare2 syntax TBH. Maybe a bit more explanation or quick demo...

> need to merge this to unblock other PRs Sure! Didn't mean to block. I noticed the PR was approved but sometimes there's still other feedback that can def. wait...

Transferred from docs PR. Not sure it's still a valid/relevant Q (feel free to close if not).

What about extracting all user messages to a central location for easy access to the prod team to help with? Could even help for future i18n ([more context](https://github.com/iterative/dvc.org/issues/2108#issuecomment-774580721)).

> We decided to adopt https://clig.dev as a base guideline for the CLI applications p.s. would it be worth giving a quick talk to others on this? E.g. in an...

> The add command is quiet about what is done, at the end, there's only a progress bar (and, an ugly hint). Not sure why you consider the progress bar...