How alibekhov/online-imzo works
DocuSign Telegram is a web app for preparing PDF signature requests and collecting signatures through Telegram or a web signing screen. Senders authenticate, upload or generate a sample PDF, place a signature field, and create a request with a QR/deep link; recipients submit a drawn signature and can download the signed PDF. The graph separates the React client, HTTP/API layer, signing services, and persistent data. README content was absent, so capabilities and flow are based on the source index and shown source excerpts; some client/server wiring is inferred from matching API routes.
Main entry points: App.tsx App shell · api.ts API client · signing.routes.ts Signing routes · index.ts JSON database
Components 25
Web client
- App shell
src/App.tsx - Login and register
src/components/auth/LoginRegisterModal.tsx - Document dashboard
src/components/dashboard/Dashboard.tsx - PDF upload
src/components/upload/UploadModal.tsx - Signature placement
src/components/placement/SignaturePlacementEditor.tsx - QR display
src/components/placement/QRCodeModal.tsx - Signing screen
src/components/signing/TelegramSigningScreen.tsx - Audit trail
src/components/audit/AuditTrailModal.tsx - Bot status
src/components/telegram/TelegramBotStatusModal.tsx - Session context
src/context/AuthContext.tsx
HTTP API
- API client
src/services/api.ts - Express app
server/app.ts - API router
server/routes/index.ts - Authentication routes
server/routes/auth.routes.ts - Document routes
server/routes/document.routes.ts - Signing routes
server/routes/signing.routes.ts - Telegram routes
server/routes/telegram.routes.ts
Signing domain
- PDF processing
server/services/pdf.service.ts - QR generation
server/services/qr.service.ts - Telegram integration
server/services/telegram.service.ts
Data and identity
- JWT authentication
server/middleware/auth.ts - JSON database
server/db/index.ts
Other components
- Document sender
- Signer
- Telegram platform
Connections 40
- Document sender → App shell: uses
src/App.tsx - App shell → Login and register: renders
src/App.tsx - App shell → Document dashboard: renders
src/App.tsx - App shell → PDF upload: opens
src/App.tsx - App shell → Signature placement: opens
src/App.tsx - App shell → QR display: renders
src/App.tsx - App shell → Signing screen: renders
src/App.tsx - App shell → Audit trail: opens
src/App.tsx - App shell → Bot status: opens
src/App.tsx - App shell → Session context: wraps
src/App.tsx - Login and register → Session context: authenticates through
src/components/auth/LoginRegisterModal.tsx - Session context → API client: requests session
src/context/AuthContext.tsx - Document dashboard → API client: loads documents
src/components/dashboard/Dashboard.tsx - PDF upload → API client: uploads PDF
src/components/upload/UploadModal.tsx - Signature placement → API client: creates request
src/components/placement/SignaturePlacementEditor.tsx - Signing screen → API client: submits signature
src/components/signing/TelegramSigningScreen.tsx - Audit trail → API client: loads audit
src/components/audit/AuditTrailModal.tsx - Bot status → API client: checks status
src/components/telegram/TelegramBotStatusModal.tsx - API client → Express app: sends HTTP requests
- Express app → JSON database: initializes
server/app.ts - Express app → API router: mounts API
server/app.ts - API router → Authentication routes: registers
server/routes/index.ts - API router → Document routes: registers
server/routes/index.ts - API router → Signing routes: registers
server/routes/index.ts - API router → Telegram routes: registers
server/routes/index.ts - Authentication routes → JSON database: reads and writes
server/routes/auth.routes.ts - Document routes → JWT authentication: protects routes
server/routes/document.routes.ts - Signing routes → JWT authentication: protects routes
server/routes/signing.routes.ts - JWT authentication → JSON database: looks up user
server/middleware/auth.ts - Document routes → JSON database: reads and writes
server/routes/document.routes.ts - Document routes → PDF processing: inspects and generates PDFs
server/routes/document.routes.ts - Signing routes → JSON database: reads and writes
server/routes/signing.routes.ts - Signing routes → QR generation: generates signing QR
server/routes/signing.routes.ts - Signing routes → PDF processing: places signature
server/routes/signing.routes.ts - Signing routes → Telegram integration: validates Telegram data
server/routes/signing.routes.ts - Telegram routes → JSON database: looks up request
server/routes/telegram.routes.ts - Telegram routes → Telegram integration: builds bot replies
server/routes/telegram.routes.ts - Telegram routes → Telegram platform: dispatches bot messages
server/routes/telegram.routes.ts - Signer → App shell: opens signing link
src/App.tsx - Signer → Telegram platform: uses bot or QR