Dave Berenbaum

@jorgeorpinel Is this waiting on anything?

Do we need a development/pipelines-related use case? We have https://dvc.org/doc/use-cases/versioning-data-and-model-files, which addresses model development but focuses on versioning and not pipelines. My model development may include data validation and preprocessing...

> 4.3 **Production Integrations** > Databases (e.g. SQL dump versioning/preprocessing) > Spark (e.g. remote training) > AirFlow (e.g. batch scoring) > Kafka (e.g. real-time predictions) + Feast/feature stores: https://discord.com/channels/485586884165107732/563406153334128681/969249645073145896

👍 The only thing I can think of that you might want to add is `import`/`update`.

Thanks @jorgeorpinel! My specific feedback on https://github.com/iterative/dvc.org/pull/3414#issuecomment-1238505396: > We should probably talk more about dvc exp init here? (since it helps to bootstrap the dvc.yaml after all)? We can mention...

Great subject! I think it's worth spending a little time iterating on this to make it as helpful as possible since it's a common topic.

> The most important: What they ask from DVC? What they are looking to do with our tools depends on the doc. For example, I would assume that a get...

I'm not sure where features should live, but otherwise LGTM.

Some thoughts on content: * Features: for now, we can focus on 3 main components of DVC: data management, pipelines, and experiments. * What it is: CLI tool with accompanying...

One more thought: how much should it focus on the rest of the Iterative ecosystem (both Studio and other products)? I'd suggest we mention the Iterative ecosystem and link to...