Invonotify DocsProduct, workflows, and requirements
Open App
Documentation Hub

Product docs, workflows, and the full SRS in one place.

This section is now organized like a real documentation portal: dedicated pages, sidebar navigation, source-backed content, and routing that works directly under `/docs` on the current site.

Open getting startedRead the SRS
Primary docs URL: `https://invonotify.vercel.app/docs`
Landing-page Docs buttons now point to `/docs`
Architecture, workflows, and SRS are available as separate pages
Content is sourced from the `Documentation/` folder and `README.md`
Documentation map
Open any major section directly from here.

Getting Started

Use this first for installation, environment setup, and the main system overview.

Architecture

Explains how the application is structured and how data moves through the system.

Workflows

Diagram-focused documentation for onboarding, reviews, and operational understanding.

Software Requirements Spec

The project requirements specification used for academic and product documentation.

AI Recovery PRD

Use this to understand the P0 recovery MVP, module status, demo account, and judging checklist.

AI Recovery TODO

Tracks complete P0 work, the next buildathon modules, and production hardening work.

Use this docs home as the single public entry point. Every page in this section lives under `/docs`.
Structured like a docs portal
The docs now live under a dedicated documentation shell with a sidebar, page routing, and per-page navigation.
Backed by repo sources
README, architecture docs, workflow diagrams, and the SRS are rendered directly from the markdown files already in this repository.
Built into the same app
The documentation stays at `/docs` on the current deployment, so users do not leave the main Vercel site.
Documentation library
Choose a page below to read the complete content from the repo.

Getting Started

Start Here

Project overview, environment variables, setup, deployment, and operational guidance.

README.md

Architecture

Core Reference

Narrative architecture covering frontend, backend, data model, and optimization guidance.

Documentation/architecture/system-architecture.md

Workflows

Core Reference

System context, request flows, dashboard analytics, auth, and deployment diagrams.

Documentation/architecture/system-architecture-diagrams.md

Software Requirements Spec

Formal Docs

Formal SRS for product scope, actors, features, interfaces, and non-functional requirements.

Documentation/SRS.md

AI Recovery PRD

Buildathon

Prioritized Razorpay AI Revenue Recovery product requirements, module coverage, safety boundaries, and demo runbook.

PRD.md

AI Recovery TODO

Buildathon

Prioritized implementation checklist for the recovery modules and submission readiness.

docs/RAZORPAY_HACKATHON_TODO.md

How to read this docs site
A simple order helps users and reviewers get context quickly.

Step 1

Start with Getting Started

Use the README-backed page for project overview, setup, environment variables, deployment, and troubleshooting.

Step 2

Move to Architecture

Read the system narrative to understand the frontend, route handlers, data layer, integrations, and scaling guidance.

Step 3

Open Workflows

Review the major system flows including auth, invoice reads, dashboard analytics, reminders, and deployment runtime paths.

Step 4

Reference the SRS

Use the SRS for formal requirements, actors, interfaces, and non-functional expectations.

The main pages are `/docs`, `/docs/getting-started`, `/docs/architecture`, `/docs/workflows`, and `/docs/srs`.
What is covered
Setup instructions, environment variables, deployment notes, authentication flow, analytics flow, reminder automation, and formal requirements are all included.
How it is organized
The sidebar stays visible across docs pages, each document gets its own route, and the detail pages include page-level navigation plus an on-page section index.
Where content comes from
`README.md` powers getting started, `Documentation/architecture/*` powers the architecture and workflows pages, and `Documentation/SRS.md` powers the requirements page.