docs(notebook): finalize leksara notebooks#76
Conversation
There was a problem hiding this comment.
Pull Request Overview
This PR finalizes the Leksara notebook documentation by consolidating two separate notebooks into a single comprehensive quickstart playbook. The updated notebook now provides an end-to-end guide covering installation, CartBoard dashboards, ReviewChain pipelines, benchmarking, logging, cleaning primitives, PII masking, and advanced normalization features—all in one cohesive document with English documentation.
Key changes:
- Merged feature test content into the main quickstart notebook with improved structure and English descriptions
- Deleted the redundant
leksara_full_feature_tests.ipynbfile - Enhanced documentation with detailed section headers and usage guidance
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| notebooks/leksara_quickstart.ipynb | Expanded from basic quickstart to comprehensive playbook covering all Leksara features with structured sections, installation guide, and closing insights |
| notebooks/leksara_full_feature_tests.ipynb | Removed redundant notebook as content was consolidated into the main quickstart |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "pip install leksara\n", | ||
| "```\n", | ||
| "\n", | ||
| "Tip: activate a virtual environment (for example `python -m venv .venv` then `.\\.venv\\Scripts\\activate`) to keep project dependencies isolated." |
There was a problem hiding this comment.
The virtual environment activation command uses Windows-style path separators (.\\.venv\\Scripts\\activate). Consider providing cross-platform examples or using forward slashes, as the notebook should be platform-agnostic. For example: 'then source .venv/bin/activate on macOS/Linux or .venv\\Scripts\\activate on Windows'.
| "Tip: activate a virtual environment (for example `python -m venv .venv` then `.\\.venv\\Scripts\\activate`) to keep project dependencies isolated." | |
| "Tip: activate a virtual environment (for example `python -m venv .venv`, then `source .venv/bin/activate` on macOS/Linux or `.venv\\Scripts\\activate` on Windows) to keep project dependencies isolated." |
No description provided.