System Requirements Document (SRD)

nova-template

1. Introduction

The nova-template project is designed to generate production-ready document templates for large-scale insurance systems, such as TATA AIG. This document outlines the system requirements necessary to convert design inputs (Figma/Adobe) into deployable template packages that meet high standards of accuracy, scalability, and production readiness.

The project focuses on delivering pixel-perfect templates, dynamic Handlebars logic, and accurate Joi validation schemas, while adhering to strict engineering constraints and validation checklists.

This document has been tailored for Monin Modi, based in the US, ensuring locale-specific considerations such as time zones and currency formatting are accounted for.

2. System Overview

The nova-template system will automate the conversion of design files into functional templates, enabling seamless integration into insurance platforms. The system will support:

• Design-to-Code Translation: Converting layouts into pixel-accurate HTML/CSS.
• Dynamic Handlebars Logic: Adding reusable constructs for conditional sections and dynamic tables.
• Schema Generation: Inferring Joi validation schemas from design inputs and references.
• Output Structure: Ensuring modular folder organization for scalability and reusability.

The system will prioritize production readiness, minimal iteration costs, and high accuracy, while adhering to strict validation standards.

3. Functional Requirements

As User:

• I should be able to upload Figma/Adobe design files for template generation.
• I should be able to preview the generated template in real-time.
• I should be able to compare the design input with the generated output side-by-side.
• I should be able to provide feedback on alignment, table logic, and conditional sections.

As Admin:

• I should be able to manage folder structures and naming conventions for templates.
• I should be able to validate schema accuracy and ensure edge case handling.
• I should be able to deploy templates directly to production systems.

As System:

• I should infer schema constraints intelligently from design inputs.
• I should generate reusable Handlebars partials for dynamic sections.
• I should ensure responsiveness and print-friendly layouts.

4. User Personas

User

• Role: Designers and developers uploading design files for template generation.
• Needs: Real-time preview, design fidelity, and iteration feedback.

Admin

• Role: Supervisors ensuring schema accuracy and production readiness.
• Needs: Validation tools, deployment capabilities, and folder management.

System

• Role: Automated engine for template generation.
• Needs: Accurate schema inference, reusable logic, and scalable output structures.

5. Visuals Colors and Theme

Color Palette:

The nova-template project will use a clean, modern, and professional color palette to reflect the insurance industry's trustworthiness and precision.

• Background: #F5F5F5 (Soft Gray)
• Surface: #FFFFFF (Pure White)
• Text: #333333 (Dark Charcoal)
• Accent: #0077CC (Bright Blue)
• Muted Tones: #B0BEC5 (Muted Steel Blue)

This palette ensures clarity, readability, and a professional aesthetic suitable for insurance systems.

6. Signature Design Concept

Interactive Blueprint Landing Page

The homepage of the nova-template system will feature an interactive blueprint design that mimics an architectural drawing. Users will see pencil-sketch animations of templates being constructed in real-time, with sections dynamically "drawn" as they hover or click.

Key Features:

• Dynamic Animations: Pencil-sketch lines animate to form grids, tables, and sections.
• Interactive Elements: Hovering over sections highlights them with a glowing effect.
• Color Shifts: Accent colors subtly change based on user interaction, creating a lively yet professional feel.
• Micro-Interactions: Clicking on a section zooms into its details, allowing users to explore template components.
• Responsive Design: The blueprint adapts seamlessly to different screen sizes, ensuring usability across devices.

This concept will make the system visually engaging while emphasizing precision and modularity.

7. Non-Functional Requirements

• Performance: Templates must be generated within seconds of file upload.
• Scalability: The system must support large-scale deployments without degradation.
• Security: Ensure secure handling of uploaded files and generated templates.
• Usability: Provide an intuitive interface for users and admins.
• Reliability: Ensure consistent output quality across iterations.

8. Tech Stack

Frontend:

• React for Web

Backend:

• Python
• FastAPI

Database RDBMS:

• MySQL (preferred)
• Alembic for migrations

AI Models:

• GPT 5.4 for user-friendly responses
• Claude 4.6 Opas for coding work

AI Tools:

• Litellm for LLM Routing
• Langchain

Local Orchestration:

• Docker
• docker-compose

Server-Side Orchestration:

• Kubernetes

9. Assumptions and Constraints

Assumptions:

• Design inputs will be provided in Figma/Adobe formats.
• Templates will not require multilingual support.
• The system will follow existing folder structure conventions.

Constraints:

• Output must be production-ready and scalable.
• No hardcoding of dynamic values.
• Strict adherence to validation checklists.

10. Glossary

• Handlebars: A templating engine used for dynamic HTML generation.
• Joi: A schema validation library for JavaScript.
• Edge Case Handling: Ensuring templates function correctly with unusual or extreme data inputs.
• Responsive Design: Templates that adapt to different screen sizes.
• Dynamic Sections: Template components that change based on data inputs.