Project Backlog¶
This page tracks planned and possible future work for django-resume. Items here are not commitments; they are a shared planning list for maintainers.
Completed user-visible work belongs in the Changelog. Backlog items should be removed from this page when they are released, or rewritten if the next useful step changes.
Backlog Items¶
Add support for JSON Resume.
Support importing from and exporting to the JSON Resume schema. Directional design decisions are recorded in the JSON Resume plan; remaining design and implementation work includes choosing the exact schema revision to pin, implementing field mappings and plugin compatibility, validation tests, and round-trip fidelity checks. A later trusted same-installation round-trip phase should cover provenance signing, canonicalization, replay protection, and signing-key rotation. Schema pinning gates the conditional extension and complete-document validation decisions in the plan; stable item identity is separate future work for item-level restoration and merge updates.
Design application workflows and agentic job/project outreach.
Explore how django-resume can use structured resume data to draft, queue, review, send, and track job or project applications. The first design should keep sending behind explicit user approval, define the relationship to content plugins, page plugins, JSON Resume import/export, and optional pipy-based agent execution.
Document agent-assisted plugin authoring.
Coding agents are now a better fit for plugin generation than a productized LLM workflow inside django-resume. Instead of maintaining provider integrations, prompt orchestration, or an MCP server as runtime or package functionality, document how an agent should create a filesystem plugin using the current plugin APIs.
The useful output should be durable documentation or a small agent skill: describe the expected plugin files, base classes, forms, templates, URL and admin integration points, tests, and constraints to preserve. Keep this as authoring guidance for humans and coding agents, not as generated runtime behavior.
Related old issue: #7.