docs: restructure documentation layout#6
Conversation
- Rename async-python-debug-toolbar to debug-toolbar throughout - Reorganize index with grid layout for screenshots - Create architecture/index.md for cleaner ADR navigation - Simplify API reference with quick navigation section - Use hidden toctrees with section captions - Match litestar-storages/workflows docs style 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
|
There was a problem hiding this comment.
Pull request overview
This PR renames the repository from async-python-debug-toolbar to debug-toolbar and modernizes the documentation structure to match the litestar-storages/workflows documentation style.
Key Changes:
- Repository renamed throughout all documentation, configuration files, and URLs
- Documentation index restructured with grid layout for visual screenshot gallery
- New architecture index page for cleaner ADR navigation with grouped sections
- API reference enhanced with quick navigation links to key classes
Reviewed changes
Copilot reviewed 9 out of 9 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| pyproject.toml | Updated all project URLs and changelog postprocessor to use new repository name |
| docs/index.md | Restructured with grid layout for screenshots, hidden toctrees with captions, and streamlined feature list |
| docs/conf.py | Updated GitHub URL in theme options |
| docs/comparison.md | Updated all references from async-python-debug-toolbar to debug-toolbar |
| docs/architecture/index.md | New index file for architecture section with organized ADR navigation |
| docs/architecture/ARCHITECTURE.md | Updated repository directory name from async-python-debug-toolbar/ to debug-toolbar/ |
| docs/api/index.md | Added quick navigation section with links to core classes, Litestar integration, and panels |
| README.md | Updated all GitHub URLs and documentation links to use new repository name |
| CONTRIBUTING.rst | Updated clone URLs and issue tracker links to new repository name |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Replace recursive autosummary with manual API documentation - Document each class with params, methods, and examples - Remove deeply nested module tree in sidebar - Match litestar-workflows API docs style 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 38 out of 38 changed files in this pull request and generated 8 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| @@ -1,4 +1,4 @@ | |||
| debug\_toolbar.core.config | |||
| debug\_toolbar.core.config | |||
There was a problem hiding this comment.
This file contains a Unicode BOM (Byte Order Mark) character at the beginning. While it typically doesn't cause issues, it's generally best practice to avoid BOMs in UTF-8 files as they're unnecessary and can occasionally cause parsing issues with some tools. Consider saving these files without the BOM.
| debug\_toolbar.core.config | |
| debug\_toolbar.core.config |
| @@ -1,4 +1,4 @@ | |||
| debug\_toolbar.core.context | |||
| debug\_toolbar.core.context | |||
There was a problem hiding this comment.
This file contains a Unicode BOM (Byte Order Mark) character at the beginning. While it typically doesn't cause issues, it's generally best practice to avoid BOMs in UTF-8 files as they're unnecessary and can occasionally cause parsing issues with some tools. Consider saving these files without the BOM.
| debug\_toolbar.core.context | |
| debug\_toolbar.core.context |
| @@ -1,4 +1,4 @@ | |||
| debug\_toolbar.core.panel | |||
| debug\_toolbar.core.panel | |||
There was a problem hiding this comment.
This file contains a Unicode BOM (Byte Order Mark) character at the beginning. While it typically doesn't cause issues, it's generally best practice to avoid BOMs in UTF-8 files as they're unnecessary and can occasionally cause parsing issues with some tools. Consider saving these files without the BOM.
| debug\_toolbar.core.panel | |
| debug\_toolbar.core.panel |
| @@ -1,4 +1,4 @@ | |||
| debug\_toolbar.core.storage | |||
| debug\_toolbar.core.storage | |||
There was a problem hiding this comment.
This file contains a Unicode BOM (Byte Order Mark) character at the beginning. While it typically doesn't cause issues, it's generally best practice to avoid BOMs in UTF-8 files as they're unnecessary and can occasionally cause parsing issues with some tools. Consider saving these files without the BOM.
| debug\_toolbar.core.storage | |
| debug\_toolbar.core.storage |
| @@ -1,4 +1,4 @@ | |||
| debug\_toolbar.core.toolbar | |||
| debug\_toolbar.core.toolbar | |||
There was a problem hiding this comment.
This file contains a Unicode BOM (Byte Order Mark) character at the beginning. While it typically doesn't cause issues, it's generally best practice to avoid BOMs in UTF-8 files as they're unnecessary and can occasionally cause parsing issues with some tools. Consider saving these files without the BOM.
| debug\_toolbar.core.toolbar | |
| debug\_toolbar.core.toolbar |
| @@ -1,4 +1,4 @@ | |||
| debug\_toolbar.litestar.config | |||
| debug\_toolbar.litestar.config | |||
There was a problem hiding this comment.
This file contains a Unicode BOM (Byte Order Mark) character at the beginning. While it typically doesn't cause issues, it's generally best practice to avoid BOMs in UTF-8 files as they're unnecessary and can occasionally cause parsing issues with some tools. Consider saving these files without the BOM.
| debug\_toolbar.litestar.config | |
| debug\_toolbar.litestar.config |
| @@ -1,4 +1,4 @@ | |||
| debug\_toolbar.litestar.middleware | |||
| debug\_toolbar.litestar.middleware | |||
There was a problem hiding this comment.
This file contains a Unicode BOM (Byte Order Mark) character at the beginning. While it typically doesn't cause issues, it's generally best practice to avoid BOMs in UTF-8 files as they're unnecessary and can occasionally cause parsing issues with some tools. Consider saving these files without the BOM.
| debug\_toolbar.litestar.middleware | |
| debug\_toolbar.litestar.middleware |
| @@ -1,4 +1,4 @@ | |||
| debug\_toolbar.litestar.plugin | |||
| debug\_toolbar.litestar.plugin | |||
There was a problem hiding this comment.
This file contains a Unicode BOM (Byte Order Mark) character at the beginning. While it typically doesn't cause issues, it's generally best practice to avoid BOMs in UTF-8 files as they're unnecessary and can occasionally cause parsing issues with some tools. Consider saving these files without the BOM.
| debug\_toolbar.litestar.plugin | |
| debug\_toolbar.litestar.plugin |
Summary
async-python-debug-toolbartodebug-toolbarthroughout codebasearchitecture/index.mdfor cleaner ADR navigationChanges
Test plan
make cipasses🤖 Generated with Claude Code