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

DOC-878 Reorganize and clean up Components docs #27848

Merged
merged 27 commits into from
Feb 19, 2025

Conversation

neverett
Copy link
Contributor

@neverett neverett commented Feb 13, 2025

Summary & Motivation

Reorganize according to proposed new IA and copyedit existing content.

How I Tested These Changes

Changelog

Insert changelog entry or delete this section.

@neverett neverett added the area: docs Related to documentation in general label Feb 13, 2025
@neverett neverett self-assigned this Feb 13, 2025
@neverett neverett changed the title Reorganize and clean up Components docs DOC-878 Reorganize and clean up Components docs Feb 13, 2025
Copy link
Member

Hey @neverett could you post a link to the preview website? That would make this easier to review.

Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
@neverett neverett marked this pull request as ready for review February 18, 2025 22:40
@neverett
Copy link
Contributor Author

Hey @neverett could you post a link to the preview website? That would make this easier to review.

Sure thing, with the caveat that this is still a work in progress until EOD today (although the high level structure is now in place). I can update again when I'm finished making changes.

Signed-off-by: nikki everett <[email protected]>
Copy link

github-actions bot commented Feb 18, 2025

Deploy preview for dagster-docs ready!

Preview available at https://dagster-docs-4bxevltol-elementl.vercel.app
https://nikki-docs-components-reorg.archive.dagster-docs.io

Direct link to changed pages:

Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
Copy link
Member

I think we should frame "Migrating to Components" to "Incrementally Adopting Componets" which I think is both more accurate and less scary.


:::info

This feature is still in development and might change in patch releases. It’s not production ready, and the documentation may also evolve. Stay tuned for updates.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@neverett This isn't related to this PR, but I find these inline comments from vale to be super noisy. Can we suppress them in this view and surface them elsewhere?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I made a ticket to tune/reconfigure Vale a few weeks ago, I can prioritize that after this PR is merged. I agree, it's super noisy and distracting.

Copy link
Member

@schrockn schrockn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Signed-off-by: nikki everett <[email protected]>
Copy link
Member

@schrockn schrockn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Requesting changes to change the name of the "migrating" section to "incrementally adopting" (as well as subpages). Huge improvement overall 👍🏻 Once that is change will very happily approve.

Signed-off-by: nikki everett <[email protected]>
@@ -1,6 +1,6 @@
---
title: 'Making an existing code location components-compatible'
sidebar_position: 300
title: 'Migrating an existing code location to components'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you change these subpages as well to include incremental adoption language?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is really "Using components in an existing code location"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah yeah, that makes more sense

@@ -1,10 +1,10 @@
---
title: 'Migrating existing definitions to components'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using existing definitions within components

Signed-off-by: nikki everett <[email protected]>
@neverett
Copy link
Contributor Author

@schrockn I pushed some changes while you were commenting, but will update those subpages accordingly.

Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
@neverett neverett requested a review from schrockn February 19, 2025 17:16
@neverett
Copy link
Contributor Author

@schrockn updated subpages and redirects, so this is ready for another review. Thanks!

Copy link
Member

@schrockn schrockn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great thank you! Please let @benpankow know when this as he has outstanding content read to merge I believe.

Signed-off-by: nikki everett <[email protected]>
- path: replication.yaml
asset_attributes:
- target: "*"
attributes:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The indentation on line 3 uses a tab character which will cause YAML parsing errors. Replace the tab with spaces to maintain consistent indentation with the rest of the file.

Spotted by Graphite Reviewer

Is this helpful? React 👍 or 👎 to let us know.

- path: replication.yaml
asset_attributes:
- target: "*"
attributes:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The indentation on line 4 uses a tab character which will cause YAML parsing errors. Replace the tab with spaces to match the surrounding indentation level. YAML is space-sensitive and does not handle tabs well.

Spotted by Graphite Reviewer

Is this helpful? React 👍 or 👎 to let us know.

Signed-off-by: nikki everett <[email protected]>
@neverett neverett merged commit ba5d017 into master Feb 19, 2025
7 checks passed
@neverett neverett deleted the nikki/docs/components-reorg branch February 19, 2025 22:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: docs Related to documentation in general
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants