Skip to content

docs: update readme - #9

Closed
Yggdrasill501 wants to merge 4 commits into
mainfrom
filipzitny/mar-340-create-deepnote-toolkit-readme
Closed

docs: update readme#9
Yggdrasill501 wants to merge 4 commits into
mainfrom
filipzitny/mar-340-create-deepnote-toolkit-readme

Conversation

@Yggdrasill501

@Yggdrasill501 Yggdrasill501 commented Oct 31, 2025

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

  • Documentation
    • Redesigned README with a cover image and centered layout while preserving CI badges
    • Removed the warning banner and lengthy onboarding narrative in favor of concise content
    • Simplified installation instructions to use pip for toolkit and server components
    • Reorganized into clear sections (Installation, Features, Architecture, Usage, Development, Docker, Contributing, License, Support)
    • Shifted to a modular, reference-style documentation format for easier navigation

@Yggdrasill501 Yggdrasill501 self-assigned this Oct 31, 2025
@Yggdrasill501
Yggdrasill501 requested a review from a team as a code owner October 31, 2025 10:24
@linear

linear Bot commented Oct 31, 2025

Copy link
Copy Markdown

@coderabbitai

coderabbitai Bot commented Oct 31, 2025

Copy link
Copy Markdown
Contributor

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)
  • deepnote-toolkit-cover-image.png is excluded by !**/*.png

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

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

📝 Walkthrough

Walkthrough

The README has been restructured from a narrative format into a modular reference guide. The cover image and centered layout replace the initial header, and the warning banner is removed. The setup instructions shift from a multi-tool approach (mise/poetry/venv) to a simplified pip-based installation. Content is reorganized into discrete sections: Installation, Features, Architecture, Usage, Development, Docker images, Contributing, License, and Support. Outdated or duplicated commands are removed, and new explicit headings clarify core capabilities, developer tools, and infrastructure components.

Pre-merge checks

❌ Failed checks (1 warning, 1 inconclusive)
Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. You can run @coderabbitai generate docstrings to improve docstring coverage.
Title Check ❓ Inconclusive The title "docs: update readme" is related to the changeset—the README file was indeed updated—but uses a generic, non-descriptive term that fails to convey meaningful information about the scope of changes. The summary shows a substantial restructuring: replacing narrative onboarding content with a modular reference-style format, changing installation approaches, and reorganizing major documentation sections. This title could apply equally to a minor typo fix or a complete rewrite, making it too vague to clearly communicate the primary change to a teammate reviewing history. Revise the title to be more specific about what was updated. For example: "docs: restructure readme with modular documentation sections" or "docs: reorganize readme to reference-style format" would better capture the substantive nature of the changes and help reviewers understand the primary intent at a glance.
✅ Passed checks (1 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions

github-actions Bot commented Oct 31, 2025

Copy link
Copy Markdown

📦 Python package built successfully!

  • Version: 1.0.0.dev5+09c14fc
  • Wheel: deepnote_toolkit-1.0.0.dev5+09c14fc-py3-none-any.whl
  • Install:
    pip install "deepnote-toolkit @ https://deepnote-staging-runtime-artifactory.s3.amazonaws.com/deepnote-toolkit-packages/1.0.0.dev5%2B09c14fc/deepnote_toolkit-1.0.0.dev5%2B09c14fc-py3-none-any.whl"

@codecov

codecov Bot commented Oct 31, 2025

Copy link
Copy Markdown

⚠️ JUnit XML file not found

The CLI was unable to find any JUnit XML files to upload.
For more help, visit our troubleshooting guide.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 3

📜 Review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

Disabled knowledge base sources:

  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 48b0a54 and 819c995.

⛔ Files ignored due to path filters (1)
  • deepnote-toolkit-cover-image.png is excluded by !**/*.png
📒 Files selected for processing (1)
  • README.md (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.18.1)
README.md

1-1: First line in a file should be a top-level heading

(MD041, first-line-heading, first-line-h1)


34-34: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)


40-40: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)


46-46: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)


96-96: Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


103-103: Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


110-110: Fenced code blocks should be surrounded by blank lines

(MD031, blanks-around-fences)


174-174: Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)
  • GitHub Check: Test - Python 3.11
  • GitHub Check: Test - Python 3.10
  • GitHub Check: Typecheck - 3.9
  • GitHub Check: Build and push artifacts for Python 3.11
  • GitHub Check: Build and push artifacts for Python 3.12
  • GitHub Check: Build and push artifacts for Python 3.9
  • GitHub Check: Build and push artifacts for Python 3.10
🔇 Additional comments (1)
README.md (1)

1-176: Well-structured documentation update.

The README restructure from narrative to modular reference format is effective. Content is clear, links are properly formatted, and the simplified pip-based installation guidance is an improvement. After addressing the markdown formatting issues above, this will be ready.

Comment thread README.md
Comment on lines +34 to +46
### Core capabilities
- **SQL execution engine**: Multi-database SQL support with connection management, query templating via Jinja2, intelligent caching, and query chaining with CTE generation
- **Interactive visualizations**: Vega-Lite charts with VegaFusion optimization, multi-layer support, and interactive selections
- **Data processing**: Enhanced DataFrame utilities, data sanitization, and DuckDB in-memory analytics
- **Jupyter integration**: Custom IPython kernel with scientific computing libraries (pandas, numpy, etc.)

7. Install pre-commit hooks:
### Developer tools
- **CLI interface**: Command-line tools for server management and configuration
- **Streamlit support**: Auto-reload development workflow for Streamlit applications
- **Language server protocol**: Code intelligence and autocompletion support
- **Runtime initialization**: Session persistence, environment variable management, and post-start hooks

```bash
$ poetry poe setup-hooks
```
### Infrastructure

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion | 🟠 Major

Add blank lines before subheadings.

Subheadings at lines 34, 40, and 46 lack blank lines above them per markdown conventions.

 ### Core capabilities
 - **SQL execution engine**: Multi-database SQL support with connection management, query templating via Jinja2, intelligent caching, and query chaining with CTE generation
 - **Interactive visualizations**: Vega-Lite charts with VegaFusion optimization, multi-layer support, and interactive selections
 - **Data processing**: Enhanced DataFrame utilities, data sanitization, and DuckDB in-memory analytics
 - **Jupyter integration**: Custom IPython kernel with scientific computing libraries (pandas, numpy, etc.)

+
 ### Developer tools
 - **CLI interface**: Command-line tools for server management and configuration
 - **Streamlit support**: Auto-reload development workflow for Streamlit applications
 - **Language server protocol**: Code intelligence and autocompletion support
 - **Runtime initialization**: Session persistence, environment variable management, and post-start hooks

+
 ### Infrastructure
 - **Git integration**: SSH/HTTPS authentication for repository access
 - **SSH tunneling**: Secure database connections through SSH tunnels
 - **Metrics collection**: Prometheus metrics for monitoring and observability
 - **Feature flags**: Dynamic feature toggling support

Committable suggestion skipped: line range outside the PR's diff.

🧰 Tools
🪛 markdownlint-cli2 (0.18.1)

34-34: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)


40-40: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)


46-46: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

🤖 Prompt for AI Agents
In README.md around lines 34 to 46, the markdown subheadings at lines 34, 40,
and 46 are missing blank lines above them; insert a single blank line
immediately before each "###" subheading so each section is separated by an
empty line to follow Markdown conventions and improve readability.

Comment thread README.md
Comment thread README.md
@deepnote-bot

deepnote-bot commented Oct 31, 2025

Copy link
Copy Markdown

🚀 Review App Deployment Started

📝 Description 🌐 Link / Info
🌍 Review application ra-9
🔑 Sign-in URL Click to sign-in
📊 Application logs View logs
🔄 Actions Click to redeploy
🚀 ArgoCD deployment View deployment
Last deployed 2025-10-31 14:02:21 (UTC)
📜 Deployed commit 62552543c69d520114d2d0a0477e750a5ea29797
🛠️ Toolkit version 09c14fc

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

Disabled knowledge base sources:

  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 819c995 and a91be2c.

📒 Files selected for processing (1)
  • README.md (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.18.1)
README.md

1-1: First line in a file should be a top-level heading

(MD041, first-line-heading, first-line-h1)


34-34: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)


40-40: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)


46-46: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)
  • GitHub Check: Test - Python 3.11
  • GitHub Check: Typecheck - 3.11
  • GitHub Check: Build and push artifacts for Python 3.12
  • GitHub Check: Build and push artifacts for Python 3.11
  • GitHub Check: Build and push artifacts for Python 3.9
  • GitHub Check: Build and push artifacts for Python 3.10
🔇 Additional comments (6)
README.md (6)

1-11: First line should be a top-level heading per MD041.

Line 1 starts with an image instead of a top-level heading, which violates markdown convention MD041. However, if this cover-image-first design is intentional, it may be acceptable. Verify this aligns with your documentation standards.


18-30: Installation section is clear and user-friendly.

The simplified pip-based approach with optional [server] extras is a clear improvement over the previous multi-tool setup. Aligns well with Python community standards.


52-66: Architecture section is well-structured.

Clear explanation of deployment bundles and module organization. Good addition for user understanding.


68-86: Usage section is practical and well-documented.

Clear CLI examples with security guidance. Good balance of information and actionable commands.


89-150: Development section is comprehensive.

Testing guidance across three approaches (mise, nox, Docker) is clear. Hot-reload documentation and coverage threshold are well-documented. Code block spacing appears correct per MD031.


152-179: Closing sections are well-organized.

Docker images, Contributing, License, and Support sections provide clear guidance. Footer formatting issue (MD036) appears resolved—bold markers removed, text now plain.

Comment thread README.md
Comment on lines +32 to +50
## Features

```bash
$ poetry self add 'poethepoet[poetry_plugin]'
```
### Core capabilities
- **SQL execution engine**: Multi-database SQL support with connection management, query templating via Jinja2, intelligent caching, and query chaining with CTE generation
- **Interactive visualizations**: Vega-Lite charts with VegaFusion optimization, multi-layer support, and interactive selections
- **Data processing**: Enhanced DataFrame utilities, data sanitization, and DuckDB in-memory analytics
- **Jupyter integration**: Custom IPython kernel with scientific computing libraries (pandas, numpy, etc.)

7. Install pre-commit hooks:
### Developer tools
- **CLI interface**: Command-line tools for server management and configuration
- **Streamlit support**: Auto-reload development workflow for Streamlit applications
- **Language server protocol**: Code intelligence and autocompletion support
- **Runtime initialization**: Session persistence, environment variable management, and post-start hooks

```bash
$ poetry poe setup-hooks
```
### Infrastructure
- **Git integration**: SSH/HTTPS authentication for repository access
- **SSH tunneling**: Secure database connections through SSH tunnels
- **Metrics collection**: Prometheus metrics for monitoring and observability
- **Feature flags**: Dynamic feature toggling support

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion | 🟠 Major

Add blank lines after subsection headings (MD022).

Lines 34, 40, and 46 lack blank lines immediately after the heading before the bullet list content. Insert a blank line after each ### heading to comply with markdown conventions.

 ## Features

 ### Core capabilities
+
 - **SQL execution engine**: Multi-database SQL support with connection management, query templating via Jinja2, intelligent caching, and query chaining with CTE generation
 - **Interactive visualizations**: Vega-Lite charts with VegaFusion optimization, multi-layer support, and interactive selections
 - **Data processing**: Enhanced DataFrame utilities, data sanitization, and DuckDB in-memory analytics
 - **Jupyter integration**: Custom IPython kernel with scientific computing libraries (pandas, numpy, etc.)

 ### Developer tools
+
 - **CLI interface**: Command-line tools for server management and configuration
 - **Streamlit support**: Auto-reload development workflow for Streamlit applications
 - **Language server protocol**: Code intelligence and autocompletion support
 - **Runtime initialization**: Session persistence, environment variable management, and post-start hooks

 ### Infrastructure
+
 - **Git integration**: SSH/HTTPS authentication for repository access
 - **SSH tunneling**: Secure database connections through SSH tunnels
 - **Metrics collection**: Prometheus metrics for monitoring and observability
 - **Feature flags**: Dynamic feature toggling support
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)

34-34: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)


40-40: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)


46-46: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

🤖 Prompt for AI Agents
In README.md around lines 32 to 50 (specifically the subsection headings at
lines 34, 40, and 46), the three "###" subsection headings are missing a blank
line before their following bullet lists; insert a single blank line immediately
after each of those `###` headings so there is an empty line between the heading
and the subsequent list item(s) to satisfy MD022 and standard Markdown
formatting.

@jamesbhobbs
jamesbhobbs marked this pull request as draft October 31, 2025 14:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants