From 6a7a5ce8f13de3f9d97aeb15a5e774e35c29918f Mon Sep 17 00:00:00 2001 From: copilotcoder Date: Fri, 19 Jun 2026 11:00:38 -0400 Subject: [PATCH] docs: wrap README lines for markdownlint compliance --- README.md | 42 +++++++++++++++++++++++++++++++----------- 1 file changed, 31 insertions(+), 11 deletions(-) diff --git a/README.md b/README.md index 71b9aa0..eac02b2 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,7 @@ # Plex Playlist Project -A full-stack application for managing Plex playlists with a FastAPI backend and Vue.js frontend. +A full-stack application for managing Plex playlists with a FastAPI backend +and Vue.js frontend. ## Architecture @@ -282,24 +283,43 @@ npm run dev ### Development & Workflow -- **[Development Environment Setup](docs/DEVELOPMENT.md)** - Comprehensive guide for setting up your development environment, git workflow, pre-commit hooks, manual tool usage, and CI/CD pipeline understanding -- **[Poe Task Reference](docs/POE_TASK_REFERENCE.md)** - Complete guide to unified development tasks and workflows using Poe the Poet -- **[Deployable Runtime Contract](docs/DEPLOYABLE_RUNTIME_CONTRACT.md)** - Canonical backend/frontend deployable runtime image requirements and exclusions -- **[ADR003: Deployable Runtime Image Contract Boundaries](docs/adr/ADR003-deployable_runtime_image_contract.md)** - Architectural decision that locks deployable image boundary policy +- **[Development Environment Setup](docs/DEVELOPMENT.md)** + - Comprehensive guide for setting up your development environment, + git workflow, pre-commit hooks, manual tool usage, and CI/CD pipeline + understanding +- **[Poe Task Reference](docs/POE_TASK_REFERENCE.md)** + - Complete guide to unified development tasks and workflows using + Poe the Poet +- **[Deployable Runtime Contract](docs/DEPLOYABLE_RUNTIME_CONTRACT.md)** + - Canonical backend/frontend deployable runtime image requirements + and exclusions +- **[ADR003: Deployable Runtime Image Contract Boundaries](docs/adr/ADR003-deployable_runtime_image_contract.md)** + - Architectural decision that locks deployable image boundary policy ### Architecture & CI/CD -- **[CI/CD Multi-stage Build](docs/CICD_MULTI_STAGE_BUILD.md)** - Docker multi-stage build strategy, architecture decisions, and performance optimizations -- **[CI/CD Troubleshooting Guide](docs/CICD_TROUBLESHOOTING_GUIDE.md)** - Comprehensive troubleshooting, optimization decisions, and performance monitoring for Docker builds and E2E testing -- **[CI/CD Success Summary](docs/CICD_SUCCESS_SUMMARY.md)** - Complete validation results and performance metrics for the optimized pipeline +- **[CI/CD Multi-stage Build](docs/CICD_MULTI_STAGE_BUILD.md)** + - Docker multi-stage build strategy, architecture decisions, + and performance optimizations +- **[CI/CD Troubleshooting Guide](docs/CICD_TROUBLESHOOTING_GUIDE.md)** + - Comprehensive troubleshooting, optimization decisions, + and performance monitoring for Docker builds and E2E testing +- **[CI/CD Success Summary](docs/CICD_SUCCESS_SUMMARY.md)** + - Complete validation results and performance metrics + for the optimized pipeline ### Dependency Management & Automation -- **[Renovate Bot Setup](docs/RENOVATE_SETUP_GUIDE.md)** - Automated dependency updates with Renovate for Python, Node.js, and Docker dependencies +- **[Renovate Bot Setup](docs/RENOVATE_SETUP_GUIDE.md)** + - Automated dependency updates with Renovate for Python, + Node.js, and Docker dependencies ### Operations & Troubleshooting -- **[Gitea Actions Troubleshooting](docs/GITEA_ACTIONS_TROUBLESHOOTING.md)** - Solutions for CI/CD pipeline issues, including the critical "jobs waiting forever" problem -- **[Secure Docker CI/CD](docs/SECURE_DOCKER_CICD.md)** - Security considerations and setup for Docker-based CI/CD pipelines +- **[Gitea Actions Troubleshooting](docs/GITEA_ACTIONS_TROUBLESHOOTING.md)** + - Solutions for CI/CD pipeline issues, + including the critical "jobs waiting forever" problem +- **[Secure Docker CI/CD](docs/SECURE_DOCKER_CICD.md)** + - Security considerations and setup for Docker-based CI/CD pipelines See the `backend/` and `frontend/` folders for more details.