Skip to content

Add 5-min quick wins page to docs #3633

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

Merged
merged 15 commits into from
May 7, 2025
Merged

Conversation

strickvl
Copy link
Contributor

@strickvl strickvl commented May 1, 2025

Added a quick-wins page (as previously discussed) to our documentation.

Would welcome alternative / additional suggestions for things we could add here. Also potentially the sections could be a teeny bit shorter?

Feedback welcomed.

@strickvl strickvl added documentation Improvements or additions to documentation internal To filter out internal PRs and issues labels May 1, 2025
@strickvl strickvl requested review from htahir1, marwan37 and Copilot May 1, 2025 09:10
Copy link
Contributor

coderabbitai bot commented May 1, 2025

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR enhances the documentation by updating an outdated link in the scheduled pipelines tutorial and adding a new "5-minute Quick Wins" page entry to the table of contents.

  • Updated the URL in the scheduled pipelines tutorial to point to the correct scheduling reference.
  • Added a new navigation link for a quick wins page in the table of contents.

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File Description
docs/book/user-guide/tutorial/managing-scheduled-pipelines.md Updated the URL for schedule reference documentation.
docs/book/user-guide/toc.md Added the "5-minute Quick Wins" link under Best Practices.
Comments suppressed due to low confidence (2)

docs/book/user-guide/tutorial/managing-scheduled-pipelines.md:26

  • Please confirm that the updated URL reflects the current organization of the documentation and is fully aligned with the intended reference structure.
For our full reference documentation on schedules, see the [Schedule a Pipeline](https://docs.zenml.io/concepts/steps_and_pipelines/scheduling) page.

docs/book/user-guide/toc.md:62

  • Ensure that the new '5-minute Quick Wins' page exists and that the link follows the established styling and hierarchy conventions in the table of contents.
* [5-minute Quick Wins](best-practices/quick-wins.md)

Copy link
Contributor

github-actions bot commented May 1, 2025

Documentation Link Check Results

Absolute links check passed
Relative links check passed
Last checked: 2025-05-07 09:39:52 UTC

Copy link
Contributor

@htahir1 htahir1 left a comment

Choose a reason for hiding this comment

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

Great one! Sorry I didnt get to it in time.

I think I'd add the following:

  • Add the Model for the Model Control Plane (seems like an obvious one most people don't use?
  • Use tags as a way to organize artifacts and pipelines and run templates?
  • Write simple smoke tests for remote pipelines on docker orchestrator
  • Create a parent image to avoid image building headaches

@strickvl strickvl requested review from htahir1 and Copilot May 2, 2025 09:15
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR adds a quick wins documentation page to help users quickly grasp essential improvements.

  • Updates the URL in the managing scheduled pipelines tutorial to the new docs location.
  • Adds a new entry in the table of contents for the quick wins page.

Reviewed Changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.

File Description
docs/book/user-guide/tutorial/managing-scheduled-pipelines.md Updated the reference URL for scheduling documentation.
docs/book/user-guide/toc.md Added a new bullet entry for the quick wins page.
Comments suppressed due to low confidence (2)

docs/book/user-guide/toc.md:62

  • [nitpick] Consider aligning the naming convention for the quick wins entry with the overall documentation style (e.g., '5-min' vs '5-minute') for consistency.
* [5-minute Quick Wins](best-practices/quick-wins.md)

docs/book/user-guide/tutorial/managing-scheduled-pipelines.md:26

  • Verify that the updated URL is accurate according to the new documentation structure and that similar references are updated consistently.
For our full reference documentation on schedules, see the [Schedule a Pipeline](https://docs.zenml.io/concepts/steps_and_pipelines/scheduling) page.

@strickvl
Copy link
Contributor Author

strickvl commented May 2, 2025

@htahir1 addressed all your requests / comments in the latest version

Copy link
Contributor

@htahir1 htahir1 left a comment

Choose a reason for hiding this comment

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

Coming along - lets not rush the finer details :-) !


# Tag based on performance
if accuracy > 0.9:
add_tags(tags=["high-accuracy"], infer_artifact=True)
Copy link
Contributor

Choose a reason for hiding this comment

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

hmm what is infer_artifact?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

From the docstring: "Flag deciding whether the artifact version should be
inferred from the step context."

# Automatically attach to the current model
log_metadata(
{"accuracy": accuracy, "f1_score": 0.89},
infer_model=True # Automatically finds pipeline's model
Copy link
Contributor

Choose a reason for hiding this comment

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

am i the only one who hates these redundant ass flags?

Copy link
Contributor

Choose a reason for hiding this comment

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

the infer_model flag? it's useful if we only want to log metadata to the model and not the pipeline run... though it would be nice to be able to log to the model and pipeline run in one log_metadata call.

Comment on lines +723 to +731
RUN pip install --no-cache-dir \
zenml==0.54.0 \
tensorflow==2.12.0 \
torch==2.0.0 \
scikit-learn==1.2.2 \
pandas==2.0.0 \
numpy==1.24.3 \
matplotlib==3.7.1

Copy link
Contributor

Choose a reason for hiding this comment

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

you also need to install stack requirements. here you can reuse some of the work you did in the tutorial you write for CI/CD

Copy link
Contributor

github-actions bot commented May 7, 2025

Images automagically compressed by Calibre's image-actions

Compression reduced images by 36.4%, saving 117.15 KB.

Filename Before After Improvement Visual comparison
docs/book/.gitbook/assets/pipeline-run-on-the-dashboard.png 169.18 KB 106.80 KB -36.9% View diff
docs/book/.gitbook/assets/stack-deployment-options.png 152.81 KB 98.04 KB -35.8% View diff

342 images did not require optimisation.

Update required: Update image-actions configuration to the latest version before 1/1/21. See README for instructions.

strickvl and others added 6 commits May 7, 2025 10:34
Added instructions to install stack component requirements in the parent Docker image to ensure all required dependencies for the stack are available. This enhances the quick win by ensuring the parent image is fully prepared for all stack components.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>
@htahir1
Copy link
Contributor

htahir1 commented May 7, 2025

@strickvl
image

The absolute link checker failed while i was doing the apidocs thing . it should be fixed with redirects when DNS propogates BUT maybe its a good time to replace these links with sdkdocs anyway ?can you do this in this Pr please

@strickvl
Copy link
Contributor Author

strickvl commented May 7, 2025

@strickvl image

The absolute link checker failed while i was doing the apidocs thing . it should be fixed with redirects when DNS propogates BUT maybe its a good time to replace these links with sdkdocs anyway ?can you do this in this Pr please

Yes already doing it. Pushing in a min and then will merge it in.

@strickvl strickvl merged commit 9285c4d into develop May 7, 2025
14 checks passed
@strickvl strickvl deleted the doc/five-minute-quick-wins-page branch May 7, 2025 09:40
strickvl added a commit that referenced this pull request May 7, 2025
* Fix link

* Add quick wins guide + photo

* Remove line breaks

* Fix broken slack alerter link

* Fixes based on PR feedback

* Optimised images with calibre/image-actions

* Addressing Marwan's comments

* Handle installed docker

* Add tag filtering image

* Fix deleted text

* Add stack requirements installation to parent Docker image guide

Added instructions to install stack component requirements in the parent Docker image to ensure all required dependencies for the stack are available. This enhances the quick win by ensuring the parent image is fully prepared for all stack components.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

* API & SDK docs fixes

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Claude <[email protected]>
(cherry picked from commit 9285c4d)
htahir1 added a commit that referenced this pull request May 7, 2025
* Add 5-min quick wins page to docs (#3633)

* Fix link

* Add quick wins guide + photo

* Remove line breaks

* Fix broken slack alerter link

* Fixes based on PR feedback

* Optimised images with calibre/image-actions

* Addressing Marwan's comments

* Handle installed docker

* Add tag filtering image

* Fix deleted text

* Add stack requirements installation to parent Docker image guide

Added instructions to install stack component requirements in the parent Docker image to ensure all required dependencies for the stack are available. This enhances the quick win by ensuring the parent image is fully prepared for all stack components.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

* API & SDK docs fixes

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Claude <[email protected]>
(cherry picked from commit 9285c4d)

* Remove mention of "Other Services" connector type (#3646)

(cherry picked from commit fc0ff9c)

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Claude <[email protected]>
Co-authored-by: Hamza Tahir <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation internal To filter out internal PRs and issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants