kling3-pro

Python metadata and integration helper package for kling3.pro.

kling3-pro provides a small, importable Python layer for Kling 3 Pro website publishing, content automation, and Next.js route discovery workflows. The package is intentionally lightweight, but the published metadata is complete: it exposes the production website URL, documentation URL, source repository, local repository path, content path, and Next.js app path used by the site.

This package is useful as a stable integration point for scripts that generate content, inspect website structure, publish MDX files, or attach site metadata to automation output. It follows the same package-page pattern used by broader SDK-style placeholder packages: clear installation instructions, concrete usage examples, package metadata, and direct links back to the target website.

Installation

Install from PyPI:

pip install kling3-pro

Upgrade to the latest published version:

pip install --upgrade kling3-pro

Quick Start

from kling3_pro import HOMEPAGE, hello, get_site_info

print(hello())
print(HOMEPAGE)
print(get_site_info())

Expected output includes the public website URL:

https://kling3.pro

Metadata API

The package exposes simple constants for direct imports:

from kling3_pro import (
    HOMEPAGE,
    DOCUMENTATION,
    PACKAGE,
    REPOSITORY,
    LOCAL_REPOSITORY,
    CONTENT_PATH,
    APP_PATH,
)

You can also retrieve everything at once:

from kling3_pro import get_site_info

site = get_site_info()

print(site["name"])
print(site["homepage"])
print(site["content_path"])
print(site["app_path"])

Returned metadata:

{
    "name": "kling3.pro",
    "homepage": "https://kling3.pro",
    "documentation": "https://kling3.pro/docs",
    "package": "kling3-pro",
    "repository": "https://github.com/youram470-art/kling3-pro-python",
    "local_repository": "/Users/mac/Documents/code/kling3-cf",
    "content_path": "content",
    "app_path": "src/app",
}

Automation Example

The metadata can be used in release scripts, blog generators, indexing tools, or site maintenance commands:

from pathlib import Path
from kling3_pro import get_site_info

site = get_site_info()
content_dir = Path(site["local_repository"]) / site["content_path"]
app_dir = Path(site["local_repository"]) / site["app_path"]

print(f"Website: {site['homepage']}")
print(f"Content directory: {content_dir}")
print(f"Next.js app directory: {app_dir}")

Use Cases

• Keep a Python package name reserved for Kling 3 Pro related tooling.
• Provide a clean PyPI page that points back to https://kling3.pro.
• Share website metadata across scripts without duplicating hard-coded paths.
• Support Kling 3 Pro content tooling, website metadata, and deployment helper scripts.
• Help publishing tools locate content and src/app consistently.

Project Layout

The related website project is organized around local content and Next.js app routes:

Local repository: /Users/mac/Documents/code/kling3-cf
Content path:     content
Next.js app path: src/app

Use it when Python automation needs a stable reference to the Kling 3 Pro homepage, source repository, content directory, and Next.js application path.

Links

• Website: https://kling3.pro
• Documentation: https://kling3.pro/docs
• Source: https://github.com/youram470-art/kling3-pro-python
• PyPI: https://pypi.org/project/kling3-pro/

License

MIT