Community + ecosystem infrastructure · 02
FlexJD Resource Hub
Community infrastructure · independently maintained
Make fragmented institutional information usable without pretending it is official.
What I noticed
Part-time online law students must assemble critical information across institutional pages, emails, calendars, informal knowledge, and third-party sources. A directory without freshness and correction controls can make that problem worse.
What I researched
Program requirements, student needs, opportunity types, institutional boundaries, source freshness, privacy, non-endorsement, correction processes, and the practical maintenance burden of a student-run resource.
What I built
A mobile-first hub with a newsletter, all-purpose guide, filterable opportunity tracker, seven awareness campaigns, correction and privacy pathways, source-verification policy, automated link checks, secret scanning, and freshness controls.
Who it serves
Northeastern University School of Law's FlexJD students, especially people balancing law school with work, care responsibilities, distance, and asynchronous participation.
What it demonstrates
Community-centered service design, information governance, operational maintenance, and the discipline to state clearly what a resource is—and is not.
Verified build record
What is actually running, and what it is not.
LiveLive · independently maintained by a student leader
The problem. Part-time online law students assemble critical information across institutional pages, emails, calendars, informal knowledge and third-party sources — and a directory without freshness and correction controls makes that worse, not better, because it adds a source that looks official and is not.
What it does. Runs a mobile-first hub with a newsletter, an all-purpose guide, a filterable opportunity tracker and seven awareness campaigns. The part that matters most is the machinery around them: a stated source-verification policy, a correction pathway anyone can use, privacy rules, freshness controls, and automated link checking and secret scanning in continuous integration. A resource a student relies on for a deadline has to be maintainable by one person who also has coursework, so the maintenance burden was designed for before the content was.
Built on. A static multi-page site with automated link checking and secret scanning in CI, served from Vercel.
What it does not establish. Maintained by a student leader for the FlexJD community. Not an official statement, publication or record of Northeastern University or its School of Law; requirements, policies, deadlines and contacts must be verified with the original source.
This record is generated from the same inventory as the complete build index: the production URL was checked at the last regeneration, and the status line above repeats what the build reports about itself rather than restating an intention.