I’m building a web platform that lets our team crunch large census-style datasets online, display the results in clear interactive graphs, and manage every record from a secure admin area. The core of the job is custom code—no generic templates—so the site stays lean, scalable, and easy for future contributors to understand. Data engine You’ll wire in the advanced calculations I’ll provide (population projections, demographic breakdowns, percent-change metrics, etc.) and process them server-side before they reach the browser. Accuracy and speed are critical, so thoughtful data structures and efficient queries will be appreciated. Admin panel The first-line requirement here is simple: authorised users must be able to add, edit, and delete census records without touching the database directly. A clean table view with inline editing or modal forms is fine as long as it’s fast and intuitive. Bulk import/export can follow the same logic if you have a straightforward solution. Visualisations On the public-facing side, users should be able to explore results through responsive graphs—think line, bar, or multi-series comparisons. If you like working with D3.js, Recharts, Chart.js or similar libraries, let me know; I’m open to whichever integrates best with React. We may introduce maps or additional chart types later, so keep the component structure flexible. Tech stack & security • Front-end: JavaScript/React is my preference. • Back-end: choose the environment you’re most productive in (Node/Express pairs nicely, but suggest otherwise if it benefits performance). • Database: any modern relational or document store is fine as long as queries can be indexed for speed and all data travels over encrypted connections. Role-based authentication is mandatory. Responsive UI The interface needs to look and work great on desktop, tablet, and mobile. I have a light style guide to share—colours, fonts, spacing—nothing heavy, but it should feel bespoke rather than cookie-cutter. Code quality & hand-off Please keep the repo tidy, comment sections that are not self-explanatory, and write concise README notes so another developer can spin up the project quickly. I’ll review work in milestones: data engine, admin panel, visual layer, final polish. If this sounds like the type of build you enjoy, let’s talk through timelines and your recommended toolset.