Projects are broader than formal research. A new medical atlas, for example, is tracked here while it is illustrated and edited, then appears as a book once published.
The first technical build of the institutional website: a multi-page Next.js and TypeScript application with content hubs, dynamic detail routes and typed local content that can later move to a CMS or database.
Sign-in and sign-up backed by Supabase authentication, with each login mapped to a user or administrator role and an upload permission, as the blueprint requires before any admin area is introduced.
A curated, verified library of published articles, reference books and registered studies for each of the nine divisions. Every record is checked against an authoritative source (Crossref, ISBN catalogues or ClinicalTrials.gov) and credited to its real authors and publisher.
A gallery of openly licensed anatomical, cellular and scientific illustrations with full creator and licence attribution, as the starting point for the institute’s own illustration portfolio.
Type checking, linting, production builds, responsive testing and accessibility checks against WCAG 2.2 AA practice before public launch.
Confirm which named people will represent the institute publicly, verify their qualifications and memberships, and publish a small verified founding team instead of many unverified profiles.
Deploy to Vercel, connect the custom domain, and set up analytics, form handling, official email addresses and the legal policies.
Internal workflows for content approval, review dates, corrections and publishing, so every record has a clear owner, reviewer and approver.
Move high-volume structured content from local TypeScript files into an editorial CMS or database once the volume of real content justifies it.
Formalise Sterling IMRES Press as the institute’s publishing imprint: book metadata, ISBN workflow, PublishDrive distribution and catalogue pages for the institute’s own titles.
Richer search, author dashboards, institutional reporting, APIs or member workflows — added only when there is a validated need.
