📄 project2pdf
Convert project structures into a single PDF. Perfect for providing context to an LLM (Large Language Model) about a specific project.
🚀 Features
✅ Automatically detects projects in the root directory
✅ Generates a structured PDF with directory trees and code snippets
✅ Supports multiple file types (.py, .ipynb, .tsx, .js, Dockerfile, .env, .md, .gitignore)
✅ No manual input needed – just run and get your documentation
📦 Installation
Install project2pdf from PyPI:
pip install project2pdf
🛠 Usage
Simply run the command inside your project directory:
project2pdf
This will:
- Detect all project folders in the root directory
- Generate a structured PDF for each project
- Save the output in the root as
project_name_documentation.pdf
📝 Example Output
After running project2pdf, you will find a PDF file like:
📂 my_project_documentation.pdf
🔧 Configuration
No additional configuration is needed. The script will:
- Include the first two levels of the directory structure
- Extract relevant code from supported files
- Format everything in a clean, readable PDF
👨💻 Supported File Types
The tool processes and includes the following file types:
.py,.ipynb→ Python scripts & Jupyter Notebooks.tsx,.js→ TypeScript/JavaScript filesDockerfile,.env,.gitignore→ Project metadata.md→ Markdown documentation
📌 Use Cases
🔹 Quickly onboard new developers to a project
🔹 Document your project before sharing it with an LLM
🔹 Organize and archive project structures
💡 Example
If your project structure is:
my_project/
│── src/
│ ├── main.py
│ ├── utils.py
│── README.md
│── requirements.txt
│── .gitignore
project2pdf will generate my_project_documentation.pdf with:
- Project structure (
tree -L 2output) - Code snippets from
main.py,utils.py, etc. - Metadata from
.gitignore,requirements.txt, etc.
🔥 Why Use This?
- Automates project documentation 📑
- Saves time onboarding new team members ⏳
- Enhances LLMs' understanding of project context 🤖
🌍 License
MIT License. Free to use and modify!
📬 Feedback & Contributions
Have ideas or found a bug? Open an issue or contribute on GitHub!
Metadata
Release files for project2pdf 0.3.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| project2pdf-0.3.6.tar.gz | 6.2 kB | Without provenance | Details for project2pdf-0.3.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| project2pdf-0.3.6-py3-none-any.whl | Python 3 | none | any | Details for project2pdf-0.3.6-py3-none-any.whl |
Total release size: 13.1 kB
Release files / project2pdf-0.3.6.tar.gz
| Download URL | project2pdf-0.3.6.tar.gz |
|---|---|
| Size | 6.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
76ac562aeb853d0a3fd34a8109b560641ec2a15aad71b37bd71b586226fb3794
|
|
BLAKE2b-256 checksum How to use checksums |
1cf9dba2b860397f8d3c001605184b19945c3a0fb0e126cbbb253cc5b9f55aab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.16
|
Release files / project2pdf-0.3.6-py3-none-any.whl
| Download URL | project2pdf-0.3.6-py3-none-any.whl |
|---|---|
| Size | 7.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
09562dac6132424904c5b4fe89b7a1b14826e4660a8a47b4b04cbfd00032fc33
|
|
BLAKE2b-256 checksum How to use checksums |
fb5dff3232e3eabadc417ee0cbc2c1666039a8e348ee2cc4b6253cebf682c045
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.16
|
Security for project2pdf 0.3.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.