Workflow
Draft, review, approve, publish, expire, redirect, and archive states for court content owners, with one approver before publish per the Q&A.
Evaluator shortcut. This page maps the clickable prototype to Attachment A requirements. It is not a substitute for the proposal; it is the working proof behind it.
What the prototype demonstrates
| RFP item | Prototype proof | Production CMS plan |
|---|---|---|
| Home page and audience-focused navigation | Home | Drupal homepage, audience taxonomy, alerts, popular tasks, source-backed content. |
| Contacts template | Contact and directory | Directory content type grouped by role, location, court level, phone, and office. |
| Department page template | Court Services | Program groups, owner/reviewer fields, document metadata, review dates, audience tags. |
| Judge/division list | Judges & Directory | Searchable, filterable judicial and staff directory; Active Directory automation stays the optional opportunity the Q&A describes. |
| Daily docket / Central Case Management integration (required scope per Addendum 1) | Daily Docket | Hourly ingestion of the Tyler Odyssey report (the pattern in the County’s Q&A), validated and published each hour, live at initial launch. |
| Dynamic news, RSS, and event calendar | Calendar | News/event content types with RSS feeds, publish/expire dates, and audience targeting. |
| Nominating Commission site | Commission | Second-site routing for jocojnc.org with shared CMS governance and analytics. |
| Metadata-driven search and document libraries | Search | Drupal Search API/Solr-ready architecture indexing pages and documents (PDF, Word, Excel, PowerPoint) per site, with metadata, synonyms, and facets. |
| WCAG 2.1 AA (confirmed in Addendum 1), WCAG 2.2 preferred, ACR | Accessibility | Automated scanning that verifies WCAG 2.1 AA as required, plus manual keyboard/screen-reader QA, ACR, and document guidance. |
| Multilingual support (top languages: Spanish, Arabic, Portuguese, Mandarin) | Self-Help Center en español | Drupal core multilingual (~100 languages, right-to-left included) with per-language editorial workflow; the Spanish self-help page demonstrates the pattern. |
| Online payments for non-case fees (Attachment B 5.11, in scope per Q&A) | Court Services payment pattern | Drupal payment integration with the County’s Alacriti platform for record-request fees and attorney registration. |
| Attachment B and Attachment C | Completed upload files in proposal packet | Attachment B CMS matrix (updated per Addendum 1) and Attachment C security checklist submitted separately. |
| No initial pricing | No public bid price shown here | Cost requested only of interviewed finalists, per Attachment A and the Q&A; priced then on Cost Proposal Worksheet_v2. |
Addendum 1 and the published Q&A, reflected here
The County published Addendum 1 and 184 question-and-answer responses on June 9, 2026. The prototype and proposal were updated the same day to match.
| What the County clarified | How this submission responds |
|---|---|
| Daily docket integration is required scope; Odyssey hourly report is the working pattern | Docket page models the hourly Odyssey feed; included in base scope, live at launch. |
| Browser standard is current Microsoft Edge plus one prior version (replacing IE) | Attachment B 1.3 updated to Included; templates target current Edge, Chrome, Firefox, and Safari. |
| WCAG 2.1 AA confirmed (2.2 preferred); automated scanning tool required | Accessibility page; scanning workflow verifies WCAG 2.1 AA, with manual and assistive-technology QA included beyond the requirement. |
| Alacriti payments for non-case fees are in scope | Attachment B 5.11 updated to Included; payment pattern noted on Court Services. |
| Top four languages: Spanish, Arabic, Portuguese, Mandarin | Spanish Self-Help demonstration; Drupal core multilingual with right-to-left support covers all four. |
| 90 percent or more of content remains; vendor remediates all active content before launch | Migration plan sized to the full retained corpus with document remediation and a redirect map preserving existing URLs. |
| 10 contributors and 5 approvers at go-live; MFA required for both roles | CMS roles, training, and MFA enforcement sized to exactly that team. |
| Two sites stay separate; single joint go-live; four environments | Shared CMS and design system across courts.jocogov.org and jocojnc.org; dev/test/staging/production; one launch. |
CMS, governance, and analytics proof points
Analytics
Usage, search terms, failed searches, docket lookups, document downloads, and service-demand dashboards.
Migration
Inventory both sites from source (granted after award), plan for 90 percent retention, remediate active pages and documents, and preserve URLs with redirects.
Training
Role-specific CMS training sized for the Court’s 10 contributors and 5 approvers, virtual-first, with recorded walkthroughs and 60 days of post-launch knowledge transfer.