How to Build a React Client Intake Form with File Uploads Using Fillo SDK

·4 views

Developers can build a client intake form using Vite and React that collects both structured answers and uploaded files in a single submission. The form captures details such as the client's name, work email, project outcome, an optional target date, and up to five reference files. Fillo's SDK handles schema definition, field validation, and file uploads directly from the browser to connected storage services like Google Drive, Amazon S3, or Box, without routing files through the app's own server. A preview mode is available for testing the form locally without an account, though file uploads remain disabled and responses are not recorded in that state. Developers are advised to connect their own storage and run through a checklist of edge cases before deploying the form for real client use.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Don't Wire a Coding Model Into Your Workflow Until It Passes Your Own Harness

Liquid syntax error: Unknown tag 'endraw'

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Zero-Budget Framework for Benchmarking AI Coding Models on Side Projects

A developer has published a structured, repeatable workflow for evaluating AI coding assistants without spending money, using free-tier APIs and a disposable git repository. The method replaces the common "vibes-based" approach — testing a model with one prompt and judging it on that alone — with a reusable benchmark suite of five to eight task types. A minimal Python harness captures raw model responses, timestamps, and errors for offline comparison across multiple models and runs. The workflow is designed to be provider-agnostic, removing barriers like API costs and the need for local hardware capable of running large models. By versioning prompts and never tuning them to favour a specific model, the approach aims to surface genuine strengths and weaknesses before any real-world deployment.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Velero Backup Bug: Kubernetes Tool Silently Omitted PVC Data for Weeks

A homelab operator discovered on June 19, 2026, that Velero had been reporting successful daily backups while never actually capturing any PersistentVolumeClaim data. The tool defaulted to snapshot-based backups, which require a CSI snapshot provider — something NFS and local-path storage classes do not support. Without a snapshot provider, Velero silently backed up only Kubernetes manifests, omitting all application data including Postgres databases, Vaultwarden passwords, and Nextcloud files. The issue was fixed by adding a single line — defaultVolumesToFsBackup: true — to the backup schedule, switching Velero to filesystem-based backup via Kopia, after which backup size jumped from roughly 2 MB to 4 GB. The operator noted that running 'velero backup describe --details' and checking the 'Pod Volume Backups' field is the only reliable way to confirm actual PVC data was captured.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

New Tool Converts Dynamics 365 Task Recordings into Structured Markdown Guides

A developer tool called axtr-to-markdown automates the conversion of Microsoft Dynamics 365 Task Recorder exports into editable Markdown documents. The skill processes recorded user steps, form names, field controls, and action types to produce structured Level 3 or Level 4 process documentation. Output includes sections for purpose, scope, prerequisites, troubleshooting, and a SIPOC analysis draft, reducing manual transcription work for teams. Functional consultants and process owners can then review and enrich the generated draft rather than building documentation from scratch. The tool is designed to support use cases such as end-user training, onboarding guides, UAT test scripts, and SharePoint knowledge articles.

0 comments Read more at DEV Community