Jorge P

OK. I'd just note that to avoid 4 levels (excessive clicking) we'll need to remove the **Contributing** submenu and just list both contribution guides inside **Customization** directly.

Other general doc structure changes (each one of these could be a `good-first-issue`: - [x] #425 Absorb Understanding DVC into existing sections - guide: extract part of `config` cmd ref...

@VANRao-Stack thanks, I will check it out. You are also involved with https://github.com/iterative/dvc.org/issues/614#issuecomment-630561304 though, please pick one issue to focus on for now and let us know. --- UPDATE: I...

> > The user guide structure has changed quite a bit since this was opened. Is it still desired? > > Yes, I think it still relevant. We still don't...

Here's an interesting framework to consider, brought up by @shcheklein: https://documentation.divio.com/introduction/ > documentation needs to include and be structured around its four different functions: tutorials, how-to guides, technical reference and...

Here's a proposal: - /docs 🏠 (Home) What is DVC, List of **Get Started** pages, Related Techs - cases 💡 Use Cases _- may extract to /cases (outside of docs)...

> Documentation -> doc (universal), surely? @casperdcl it's not universal but also I don't thin it's related to US vs UK. TBH I wasn't proposing to change it, it just...

> get started here. I see it's hidden under UG, but I would not do this. It's better to have it as a top-level section. @shcheklein a) if we remove...

@casperdcl thanks. I think we can worry about moving /cases out of docs and about outliers (contrib, troubleshooting) in a 2nd iteration. Yes, my main proposal is to remove the...

> Let's first try to properly consolidate things under Guide and then we can decide? OK. So would reorganizing most guides into 4 topics as (sub-levels of /doc/guide) be a...