Built for big document libraries
Structured content, metadata, and taxonomy keep dockets, filings, and orders organized and related.
South Dakota Public Utilities Commission · RFP #26RFP19845
We read your requirements. Then we studied your actual site.
Before we wrote a word of our proposal, we analyzed all 6,369 of your public docket pages and catalogued more than 87,000 documents. This is the homework behind our approach, and why our experience migrating unstructured government content is the right fit for the Commission’s project.
0
Docket pages analyzed
0
Documents catalogued
0
Docket categories mapped
0%
Drupal, for government
01 · Why Drupal
A platform built for your problem
The Commission’s project is a content-first publishing challenge at archival scale: a large, growing library of public records that must stay fast, findable, and accessible for decades. That is exactly what Drupal was built to do, and it keeps the State in control.
Fast search at scale
A dedicated Apache Solr layer indexes full document text and metadata, returning results across the whole repository within your performance targets.
Accessible by design
Drupal’s core is built against WCAG 2.1 AA, and authoring tools catch issues before content publishes.
Simple for your staff
With Drupal Canvas, staff build pages from governed, on-brand, compliant blocks. No code, and no way to accidentally break the layout.
Open source, no lock-in
No per-seat license fees. All content and data remain yours, exportable on demand.
Proven in government
Drupal is the go-to CMS for public-sector transparency and records at scale.
02 · Why Agileana
A team that builds only this
We do one thing: Drupal for government and mission-driven clients. That focus shows in the record.
0
Federal Drupal sites for the National Archives, including 14 Presidential Libraries
0+
U.S. Courts websites migrating to Drupal 11
“Exceptional”
CPARS rating operating FCC.gov under FISMA
0+
Acquia certifications, including multiple Triple Certified Drupal Experts
Section 508 Trusted Testers
SDVOSB
ISO 9001:2015
We are among the most credentialed Drupal organizations working in government today. The work above is public-facing, records-heavy, accessibility-bound, and uptime-critical, the same demands the Commission carries every day.
03 · Why Acquia
Hosting that already meets your bar
We host on Acquia Cloud, the managed Drupal platform. The choice is deliberate: it fits your environment, meets your security bar, and takes the operational load off the State.
Already authorized
Acquia Cloud is FedRAMP Authorized, with agency ATOs including the U.S. Departments of the Treasury and Transportation, an annual SOC 2 Type 2 audit, and ISO 27001. Your security review becomes a document exchange, not a research project.
No PHP on State infrastructure
Drupal runs entirely on the managed platform, so nothing runs on your Windows servers. The solution fits your environment as it stands.
Ready for hearing-day peaks
A 99.9% uptime commitment, multi-zone load balancing, and autoscaling for live proceedings.
Disaster recovery included
Automated daily backups, point-in-time restore, and a DR environment in a separate region.
Managed for you
Acquia runs the servers, patching, and scaling, so your staff and BIT do not carry platform operations.
Encrypted end to end
Data encrypted in transit and at rest, with role-based access and audit logging protecting confidential materials.
04 · Our Homework
We already did the homework
Most vendors promise to assess your content after they win. We already did. We built a profiler and analyzed every public docket page on puc.sd.gov, so our approach is grounded in your real content, not a clean sample.
0
Dockets profiled
0
Documents catalogued
0%
Confidential, heaviest in Telecom
0
Irregular pages identified for careful handling
A handful of page templates cover almost everything
Agileana analysisCumulative share of the 6,369 dockets covered as more page templates are handled. The steep early rise is the story: structure, not volume, drives a safe migration.
| Page templates handled | Share of dockets covered |
|---|---|
| 1 | 33% |
| 5 | 75% |
| 10 | 84% |
| 20 | 90% |
| 28 | 90% |
We did not just count documents. We measured the structure, which is what actually drives a safe migration: about twenty page templates cover roughly ninety percent of your dockets, the pages are uniformly generated so most migrate automatically, and we sized the ~500-page irregular tail deliberately instead of averaging it away.
Honest scale note: your full repository, per the RFP, is roughly 156,900 documents and 336.5 GB dating to 1976. Our profiling confirms it is large, but well-behaved.
05 · The Ford Story
Confidence that is not theoretical
On the Gerald R. Ford Presidential Library migration, the challenge was never the number of documents. It was the inconsistency of decades of hand-authored pages.
Layouts that drifted over time, pages buried where no navigation pointed to them, and markup no automated tool could cleanly read. That inconsistency, not volume, is what turns a migration into rework.
We came out of it with a discipline: profile the variance before you commit, build tooling that flags anything it cannot parse instead of silently dropping it, and hunt down the buried pages on purpose.
What we learned on Ford
Legacy government HTML is uneven and full of surprises. Estimate against the real content, or the surprises estimate you.
How it serves South Dakota
It is exactly why we profiled all 6,369 of your docket pages up front. We already know your corpus is tractable, and we have already sized the pages that need careful, manual handling.
Close
We have done our homework
A platform built for your problem, a team that builds only this, hosting that already meets your bar, and a migration approach measured against your actual content and hardened by experience. Quotes that come in far too high or far too low usually mean a vendor has not looked closely. We looked closely.