-
Notifications
You must be signed in to change notification settings - Fork 394
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
guide: new Overview page #4006
guide: new Overview page #4006
Conversation
(the latter from sidebar only for now)
Link Check ReportThere were no links to check! |
Data science experiment sharing and collaboration can be done through a regular | ||
Git flow (commits, branching, pull requests, etc.), the same way it works for | ||
software engineers. Using Git and DVC, data science and machine learning teams |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Most of this is already mentioned in the docs home and Exp Mgmt docs so I'm just removing it.
- However, some changes to the ML experiment management text in the home page could recover some of these ideas (rel DVC home page + updates #3833).
and remove Core Features header (tmp)y
f619ffe
to
22f66fa
Compare
This comment was marked as outdated.
This comment was marked as outdated.
UPDATE: Actually, per #144 (comment) I'm going to transform the Core Features section of What is DVC? as well as the Related Technologies page into an overview for the UG. For now it will be the first sub-page (no index page) but it could also be the index page itself. WDYT @dberenbaum ? |
4b1eff0
to
7106b67
Compare
"source": "user-guide/index.md", | ||
"source": false, | ||
"children": [ | ||
{ | ||
"label": "What is DVC?", | ||
"slug": "what-is-dvc" | ||
}, | ||
"overview", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or should we use the UG index page for Overview? No strong opinion
"^/doc/user-guide/what-is-dvc$ /doc/user-guide/overview 302", | ||
"^/doc/user-guide/related-technologies$ /doc/user-guide/overview 302", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
302s for now in case we later decide to move it to the UG index page instead, though
## Comparison with Related Technologies | ||
|
||
DVC combines a number of existing ideas into a single tool, with the goal of | ||
bringing best practices from software engineering into the data science field | ||
(refer to [What is DVC?](/doc/user-guide/what-is-dvc) for more details). | ||
bringing best practices from software engineering into the data science field. | ||
|
||
<details> | ||
|
||
## Git | ||
### Git |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This section is moved verbatim for now. I just put each technology into collapsed sections so the Overview page stays short (on the surface at least).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It goes in the right direction, I think .. we can do structural changes like this quick and iterate on the content later
Sounds good! There's a separate task to combine Core Features and Feature pages (both rel #144 (comment) and #3833) so I suppose we can merge this indeed 🙂 |
## DVC does not replace Git! | ||
|
||
DVC files such as `dvc.yaml` and `.dvc` files serve as placeholders to track | ||
large data files and directories for versioning (among other | ||
[purposes](/doc/user-guide/project-structure)). These metafiles change along | ||
with your data, and you can use Git to place them under | ||
[version control](https://git-scm.com/book/en/v2/Getting-Started-About-Version-Control) | ||
as a proxy to the actual data versions, which are stored in the <abbr>DVC | ||
cache</abbr> (outside of Git). This does not replace features of Git. | ||
|
||
DVC does, however, provide several commands similar to Git such as `dvc init`, | ||
`dvc add`, `dvc checkout`, or `dvc push`, which interact with the underlying Git | ||
repo (if one is being used, which is not required). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This has been fully removed although the point has also been stressed in other existing docs but I'm not sure it's mentioned everywhere it should -- so that's another possible minor follow-up to this.
Cc @dberenbaum just FYI on this change (review no longer needed but if there's any feedback feel free to leave it). |
UG Overview page deployed ⚓ Note that Studio docs have a similar page called How it works, so this may be a bit of a pattern to keep in mind. |
OP
Per #144 (comment):
Note that clicking the UG nav entry will now open directly in https://dvc.org/doc/user-guide/project-structure (for now).
UPDATE:
Per #144 (comment):
In review app: https://dvc-org-guide-break-up--bvcwlb.herokuapp.com/doc/user-guide