YAML Configuration Editor

Context

At papernest, data pipeline configuration relied on manually editing YAML files distributed across multiple markets. Non-technical stakeholders — Sales Ops managers and Data Analysts in FR, ES, and IT — had no safe way to adjust configurations without involving a Data Engineer. A single YAML syntax error could silently break pipelines affecting multiple markets.

Approach

• ·Designed a Next.js/React web interface with real-time YAML validation and an intuitive form-based editor
• ·Built a Python backend handling API calls with the internal ETL engine and LLMs
• ·Created a context-aware UI translating YAML structure into understandable fields for non-technical users
• ·Integrated an AI Copilot assistant guiding stakeholders through creating, editing, and repairing YAML configurations
• ·Implemented a testing framework to preview and validate business logic before any production deployment

Solution

The editor gives non-technical stakeholders full control over pipeline configuration through a guided, safe interface. All changes are validated in real-time, previewed before application, and deployed through a controlled flow — with no risk of introducing syntax errors into production pipelines.

Applications

• ·Multi-market data pipeline self-service
• ·Non-technical stakeholder autonomy
• ·Reducing engineering bottlenecks in data operations
• ·Safe configuration management