The first commit to the code behind this website was made on August 18, 2026. It was a scaffold: a framework, a configuration file, a stylesheet with five colors in it, and a document titled “standing instructions” that every working session has read since. Nineteen days later the site replaced the WordPress installation that had been sitting at justiceimpact.com. Four days after that it had a resource directory. Today it has a magazine.
That is the whole timeline so far. The site’s founder, JP Maroney, has said publicly that the platform is being built in public, from scratch, starting now, and that it is going to get ugly before it smooths out. This is the first of what will be an occasional record of what that looks like from the inside. Not a launch announcement. A build log.
What Justice Impact is
Maroney’s argument is compressed into one line at the top of the homepage: the problem in criminal justice is not a shortage of resources. It is that nobody is connecting them.
He has spent thirty-five years building media companies and, by his own account, five years inside the criminal justice world. He sold a group of magazines in 1999 and went on the speaking circuit. The premise for this platform came from the second number, not the first. Advocates, attorneys, nonprofit directors, ministries, reentry specialists, and families who learned more about the system than they wanted to are all working in isolation from one another. A family looking for help does not find a field. It finds fragments.
The plan is five properties in one codebase, built in a stated order: a podcast network, this magazine, a resource directory, a professional network, and later a publishing and merchandise arm. The order is on the homepage. It is a list, not a promise. No launch dates are published for the parts that do not exist yet, on purpose.
What exists today
The Justice Impact Show has published four episodes since July 21: Stephen Keller on the life settlement industry and the federal case that followed it; Dr. Ron Elfenbein on the billing dispute that became a $15 million indictment; Dr. Sanjeev Kumar, five weeks before his restitution hearing; and Dr. Karen Gedney on thirty years as a physician inside Nevada’s prisons. The first four features in this magazine are those four stories, written from the recordings.
The directory launched this week with eighteen organizations. Every listing is written in the site’s own words and checked against the organization’s own website, because third-party directories can tell you an organization exists but should never supply the description. Listings are free. Search is not built yet; the directory is browsable by category and state until the database that will power search arrives.
The founding host program is open: ten criminal defense attorneys, ten markets, ten locally branded shows on the network, produced for the host. The five cover concepts on the homepage are mockups, and the page says so in words. None of those shows is on the air.
How it is being built
The technical decisions are boring on purpose, and they are the part that will matter most in a year.
Everything a search engine or an AI answer engine needs is in the HTML the server sends. No page on the public site depends on JavaScript to show its content. A podcast player embedded in a page is not treated as content; the episode’s title, description, and notes are written into the page around it. This is the single most common way a rebuilt website loses the rankings the old one had, and it is the rule the build has been strictest about.
Data lives in three places and never crosses between them. Editorial content, including this article, lives in a git repository and is edited through a content management interface that writes plain files. Directory records will live in a Postgres database. People and money, meaning subscribers, listing owners, members, and payments, live in the customer relationship system and the payment processor, and nothing person-shaped is ever stored in the code. A lapsed subscription is handled by an automation, not by a developer.
Commerce, community, and membership billing are not being built. They run on vendors. The team is one person and, for the mechanical work, an AI coding tool working from a written roadmap and that standing instruction file. Strategy, structure, and copy decisions stay with Maroney. The instruction file includes a section titled “Report, don’t assert,” which requires any claim about accessibility, contrast, or build success to come with the measurement behind it.
What broke
Building in public means the mistakes are part of the record.
The first production deploy was run from the wrong place. The site looked fine. The homepage rendered, the about page rendered, every static page rendered. What did not run was the small server-side program that handles form submissions and, as it happened, the file that tells search engines whether to index the site. That file was supposed to say “do not index” until the launch was ready. It was never served. The site was left indexable while it was still a shell. The fix was a one-line change to the deploy command and a new rule in the instruction file: after any deploy, check a server-rendered route, not just the homepage, before believing it.
A platform-specific lock file broke the hosting provider’s build on a different operating system. An admin interface rendered blank because two integrations were registered in the wrong order, with no error message. The domain could not be attached to the new host until the old DNS records were deleted by hand. Each of these cost a few hours and each is now written down so it costs nothing the second time.
The magazine had a hard date of September 7. It shipped September 9.
What is next
The published build order says the professional network comes after the directory, and that publishing and merchandise come last. Between here and there, the directory gets its database and search, the show gets proper episode pages with transcripts, and the magazine gets contributor profiles and a September issue.
Progress is visible on the site itself. When something on the list is live, the homepage says “Live” next to it. When it is in build, it says “In build.” Nothing on that list says “coming soon.”
If you want to follow along, the email form at the bottom of every page is the only list. It is used for exactly that.