Preserve the archive.
Preserve retained historical materials and older studies as flat, dated links, with documented exception treatment. Full remediation and full-text search of this older archive are outside the defined scope.
PREPARED FOR THE WAY WEST COUNTY MOVES
Find the meeting.
Read the plan.
Keep it accessible.
A focused website rebuild that makes WCCTC’s transportation information easier to use and gives staff control of what comes next.
Prepared for West Contra Costa Transportation Commission
September 2026 · Proposal for review
One connected region.
- Proposed base investment
- $21,600 Sections 4.1–4.4
- Proposed launch
- Feb 19, 2027 Assumes Oct 30 notice to proceed
- Included after launch
- 4 weeks Stabilization through March 19
01THE RECOMMENDATION
Put public access
and staff control first.
WCCTC coordinates transportation planning, funding and programs across five cities, the county and three transit operators. Its website needs to make that work understandable, and its public records dependable to find.
We recommend carrying this React experience into production with Payload, an established open-source CMS, behind the public pages. Preserve WCCTC’s identity and the reusable layouts already developed, then focus the remaining effort on accessible content and an editing routine a small staff can maintain.
The September 11 clarification gives this project a defined starting point: WCCTC’s content audit and navigation are already complete. We can begin with that inventory and move directly into validation, adaptation and migration.
September 11 Q&A, especially 3, 7 and 2101
Public access
Meeting details and documents in one understandable record.
02
Accessible publishing
A routine for future agendas and full packets, supported by reusable templates.
03
Staff independence
Routine page and navigation changes without paid vendor involvement.
Regional connection.Richmond–San Rafael Bridge · Point Molate
REVIEW BY RFP CRITERION
A clear route through
the recommendation.
Choose what matters to your review. Weights are from RFP Section 9, not a score awarded to this proposal.
Technical approach · 25%
Keep the experience. Give staff an editor.
Retain the developed React experience and integrate Payload’s established CMS starter. Use a defined library of page blocks, structured meeting fields and a dated archive, with real staff publishing after award.
Review platform decisions ↗What to verify
Approve representative home, meeting, document and form patterns before extending the system.
02WORKING PROOF
Don’t just read the approach.
Try the public tasks.
These are functioning journeys in the concept, with a clear boundary between what you can use now and what the awarded project will deliver.
START WITH THE PERSONA record to find.
A record to find.
A program to use.
A next step to take.
Choose a task below and follow it through the working concept.
Explore a journeyWORKING CONCEPT / 01
A meeting record should answer the practical questions first.
Date, meeting body, status and documents belong together. The concept distinguishes scheduled, past and cancelled meetings, then connects people to the official source.
Explore meetings & recordsTry this journey
- Filter by Board or TAC.
- Try a search with no matches, then reset.
- Open a record and follow its official documents.
Selected real records demonstrate discovery. Complete archive migration and PDF remediation remain production work.
03CONTENT, PLATFORM & ACCESSIBILITY
A lean rebuild.
A deliberate content system.
Meetings, plans, programs and utility pages need different structures. The seven approved sections provide the frame; reusable page templates and CMS blocks provide the consistency.
At kickoff, match every retained page and document to a destination, content type and treatment. Confirm the form inventory, legacy URLs and source files with staff. Use the supplied 2025 accessibility scan to focus manual and assistive-technology checks on navigation, meetings, documents and forms.
Use Payload’s established website starter and administration features as the production foundation, integrating the reviewed React components. This is an alternative to the theme-led approach described in RFP Section 4: reuse completed interface work, keep a defined template family and avoid building a CMS from scratch. The current concept does not yet connect to Payload or establish production or PDF conformance.
THE DOCUMENT STRATEGYThree treatments.
Three treatments.
One complete retained record.
Make recent records searchable.
Structure date, time, location, status and documents. Remediate the identified agendas. Full packets from this period remain outside the remediation set.
Keep future content accessible.
Use accessible source templates and a checked posting workflow for both agendas and full packets, including approved procedural translations.
Base remediation: approximately 42–52 documents, comprising seven substantial standalone documents and 35–45 recent agendas. The agency’s finalized list controls. Q&A 7–11
Test the release, not just the theme.
Production acceptance targets WCAG 2.1 AA for the defined scope, as required by the RFP. Check keyboard operation, focus, screen-reader output, headings, labels, contrast, reflow and the reading order and tags of in-scope documents.
Use WCAG 2.2 AA design criteria for this proposal’s controls, target sizes and focus behavior. Neither a successful build nor an automated scan is a conformance certification.
Make language and maintenance practical.
Use browser-based translation for general content. Professionally translate the fixed procedural text for future meeting notices once, then reuse the approved text. Confirm languages and approval responsibility with WCCTC.
Recommend client-controlled managed hosting for the React application, Payload CMS, database and file storage, with staging and backups. Document the provider, dependencies, operating costs and restore procedure before launch.
THE PROPOSED FOUNDATION
This experience.
A real staff editor.
React for the public website. Payload CMS for staff-managed pages, navigation, meeting records and documents. The production recommendation preserves the reviewed design.
Inspect the proposed CMS ↗Keep the design. Reuse the foundation.
Integrate the existing components with an established CMS starter and a defined family of templates. Payload supplies the administration foundation; the project configures WCCTC’s content and publishing needs. This CMS is proposed, not connected to the current concept.
Give staff practical control.
Configure editing for copy, images, navigation, documents and meeting records. Staff can create pages and assemble layouts from supplied blocks. A genuinely new component or data structure requires development, which a qualified replacement firm can perform from the handed-over source.
Address the RFP directly.
Q&A 21 permits a platform other than WordPress. Section 4 still favors lean delivery. Our alternative relies on reusing the developed interface and established CMS functionality, with integration, accessibility testing and handoff included in the proposed scope. No theme or CMS label substitutes for release testing.
04REQUIREMENT TO RESPONSE
See how the scope
is accounted for.
Each entry connects a requirement to the response, evidence and dependency. “Production deliverable” describes work after award, not a completed feature of this concept.
20 of 20 requirement groups
- 4.1 · Q19
Extend the supplied accessibility baseline
Production deliverableUse the 2025 scan, then check key templates with keyboard and assistive technology. Deliver findings ranked by severity and effort.
Dependency: WCCTC provides current-site access and the supplied scan.
Review the testing approach - 4.2 · Q12
Use an established starter and reusable templates
Concept + productionIntegrate the reviewed React layouts with Payload’s website starter and CMS. Explain this alternative to the theme-led scope through interface reuse, a defined template set and the fixed budget.
Dependency: CMS integration, template accessibility testing and staff approval remain production work.
Explore the visual concept - 4.2 · Q7
Retain the seven approved sections
Working conceptOrganize About Us, Meetings, Plans and Studies, Programs, STMP, Funding, and Opportunities around public tasks.
Dependency: The final subpage inventory governs production migration.
Explore the navigation - 4.3 · Q3, Q8
Start with WCCTC’s completed inventory
Production deliverableReconcile retained pages, documents, source files and destinations at kickoff. Do not repeat the agency’s pruning exercise.
Dependency: The finalized list is supplied at notice to proceed.
Review the content ledger - 4.3 · Q7, Q17
Remediate the defined document set
Production deliverableTreat seven substantial documents and approximately 35–45 individual agendas, about 42–52 documents total.
Dependency: Source files and the agency’s final remediation list.
Review the document boundaries - 4.3 · Q10
Structure recent meeting records
Concept + productionMake 2025–2026 meetings searchable by date, time, location, status and attached documents. Remediate agendas, not full packets from that period.
Dependency: The concept contains selected records; production covers the retained set.
Try the records and document browser - 4.3 · Q9, Q10
Preserve the older archive
Production deliverableMigrate retained 2014–2024 materials and older studies as dated links, with a documented accessibility exception process.
Dependency: Archived material is not represented as fully remediated or fully searchable.
Review the archive approach - 4.3 · Q10, Q11
Prevent a new document backlog
Rehearsal + productionFrom launch, use accessible source templates and a checked posting routine for both future agendas and full packets.
Dependency: The sample checks a workflow, not PDF conformance or CMS publishing.
Try the posting rehearsal - 4.3 · Q11
Use readable HTML where it fits
Working conceptPublish simple tabular information as structured web content where feasible, reducing unnecessary document downloads.
Dependency: WCCTC confirms which retained documents can become HTML pages.
Inspect the fee table - 4.3 · Q16
Map every retained URL
Production deliverableTest redirects for retained pages and documents. Retired content can return a proper not-found response.
Dependency: Current URL export and final keep/archive/retire decisions.
Review launch acceptance - Q20
Search webpage content
Concept + productionProvide search across retained webpages. PDF full-text indexing is an optional enhancement, not a base requirement.
Dependency: The concept indexes its public pages; PDF contents are excluded.
Test site search - §3 · Q13, Q15
Connect forms and official social channels
Rehearsal + productionConfirm the form inventory and approved Facebook and Bluesky destinations with staff before production integration.
Dependency: Concept inquiries send nothing; production recipients and delivery must be verified.
Try a local inquiry draft - Q31
Make language access practical
Concept + productionUse browser-based general translation and a one-time professional translation of reusable future-meeting procedural text.
Dependency: WCCTC confirms languages and approves the procedural text. No archive-wide translation promise.
Inspect language assistance - §4 · Q21, Q25
Give staff routine structural control
Production deliverableConfigure staff editing for pages, navigation, meeting records and reusable blocks. Staff can assemble new layouts from the supplied blocks; genuinely new component behavior or data schemas still require development.
Dependency: No custom approval system or production CMS is implied by the React concept.
Review the staff workflow - Q22
Separate hosting setup from operating cost
Production deliverableInclude hosting configuration in the base fee. Recommend client-controlled managed application hosting, database and media storage, with staging, backups and a documented restore process.
Dependency: WCCTC approves the provider and actual recurring fees separately.
Review recurring-cost treatment - 4.4 · Q18
Deliver a release-specific conformance report
Production deliverableCombine automated screening, manual checks and document review; record fixes, retests and exceptions for the defined scope.
Dependency: WCCTC accepts the consultant’s report. No independent audit or current certification is claimed.
Review acceptance evidence - 4.4 · Q4
Train staff and document the routine
Production deliverableInclude one proposed 90-minute remote training session, a short maintenance guide and an accessible-posting checklist.
Dependency: Staff participate in the rehearsal and sign off. Two design review rounds are proposed.
Review the staff checkpoints - 4.4 · Q36
Include four weeks of stabilization
Production deliverableAddress minor launch issues and questions arising from training within the base fee. Later support is separate.
Dependency: Optional Section 4.5 services require separately approved scope and pricing.
Review stabilization dates - §5, §8 · Q26–29
Supply qualifying people and references
Final-offer requirementThe formal offer must identify two genuine comparable website/accessibility engagements, a live accessibility-focused sample and the assigned expertise.
Dependency: Reference consent, comparable scope, dates, named expertise and team availability remain to be confirmed.
Review related work and evidence status - §8 · Q1, Q6, Q32
Complete the signed formal response
Final-offer requirementProvide the 5–8 page narrative, excluded supporting documents, itemized costs, a signed 90-day-valid cover letter and agreement statement.
Dependency: The base fee and The Design Factory applicant presentation are approved. Ari Raphiel is the principal contact. Confirm signature authority, contracting identity, agreement/insurance documentation and any exceptions.
Review submission status
Controlling sources: corrected RFP and September 11 Q&A, including Appendices A and B. Qualifications and signed-offer requirements remain explicitly open.
05SCOPE & INVESTMENT
PROPOSED FIXED BASE FEE
$21,600
One responsible consultant.
The complete Sections 4.1–4.4 scope.
Four weeks of stabilization included.
Within WCCTC’s $22,000 ceiling. The proposed implementation reuses the developed interface, an established CMS starter and WCCTC’s completed inventory. A defined set of templates keeps the remaining work focused on CMS integration, accessibility and migration.
See the delivery planKnow what
the investment covers.
- 4.1 · Discovery & accessibility spot checks
- $2,000
- 4.2 · Template integration & CMS setup
- $5,200
- 4.3 · Content migration, meetings & redirects
- $4,000
- 4.3 · Document remediation & posting workflow
- $5,800
- 4.4 · Acceptance testing, training & launch
- $3,400
- 4.4 · Four weeks of stabilization
- $1,200
- Proposed base total
- $21,600
Included in the base
Defined retained-content migration; template integration and CMS configuration; targeted document remediation; webpage search; inventoried forms and social links; retained-content redirects; testing, hosting setup, training and handoff.
Two consolidated design reviews and one 90-minute remote staff training session are proposed.
Separate operating costs
Recurring hosting and approved licenses are paid separately by WCCTC. The provider, renewal terms and actual cost are documented before approval. Hosting setup is included in the base.
PDF full-text indexing and Section 4.5 support beyond stabilization are optional, separately scoped services.
Commercial boundaries
The standard agreement provides for monthly invoices for completed services, payment within 30 days of a compliant invoice, and the final 10% within 60 days after satisfactory completion and final invoicing. The proposed base fee is $21,600. The signed offer and agreement documentation remain to be completed.
Material scope changes require a written impact statement and approval before work begins. Any requested travel or new paid service needs prior written approval. See Appendix B, Sections 2.1–2.4.
06DELIVERY & REVIEW POINTS
Launch with time
to stabilize.
Assuming the RFP’s October 30, 2026 notice to proceed, the proposed February 19 launch leaves four weeks for stabilization through March 19, ahead of WCCTC’s April 26 milestone.
- 01
NOVEMBER 2026
Confirm & design
Reconcile the supplied inventory, verify the baseline and configure the CMS starter. Review representative page and record patterns.
Staff checkpoint: approve the content ledger and consolidated design direction.
- 02
DECEMBER–JANUARY
Build & migrate
Configure the CMS, migrate retained content, remediate the defined documents and prepare the archive and redirects.
Staff input: source documents, approved copy and procedural translations.
- 03
BY FEBRUARY 19
Test, train & launch
Test templates, documents and journeys. Rehearse publishing, deliver the report and guide, and complete an approved cutover.
Staff checkpoint: accept the defined release and confirm launch readiness.
- 04
FEBRUARY 19–MARCH 19
Stabilize & hand over
Address minor launch issues and training questions, confirm access and document remaining maintenance responsibilities.
Staff checkpoint: close stabilization and confirm ownership of accounts and exports.
Staff sign-off is sufficient under Q&A 4. The schedule depends on access, available source files, translation approval and timely consolidated feedback. Confirm the working calendar at kickoff.
07TEAM & RELEVANT EVIDENCE
Direct responsibility.
Relevant work.
The Design Factory’s proposed delivery model keeps design and implementation under an accountable lead. Ari Raphiel is the proposed principal contact; Sederrick Raphiel provides proposed creative review and asset direction.
Any specialist responsible for document remediation or accessibility testing must be named and their capacity confirmed in the formal offer. TDF remains responsible for the complete deliverable.
THE DESIGNFACTORY
Thoughtful design.
Accountable delivery.
Ari Raphiel
Proposed project lead and principal contact for The Design Factory. Coordinates day-to-day decisions, delivery and implementation.
ari@thedesignfactory.comSederrick Raphiel
Proposed creative review and asset direction. Keeps typography, imagery and WCCTC’s identity consistent through the reviewed templates.
Meet The Design Factory
NONPROFIT / PUBLIC & STAFF EXPERIENCES
Dallas–Fort Worth Urban League
Related work includes website design and development and continued support for public and staff experiences. It connects programs, membership, events and organizational information.
Relevance to WCCTC: structuring varied public tasks and the staff workflows behind them.
Explore the live website
MEMBER ASSOCIATION / TIME-SENSITIVE CONTENT
Code Enforcement Association of Texas
Related work includes website updates, improvements to training pages and job-posting presentation.
Relevance to WCCTC: making recurring information easier to find and maintain.
Explore the live websiteReference status: These are related portfolio examples, not substitutes for the two required comparable website and accessibility-focused references. Completion dates, exact accessibility scope, client consent, the live accessibility-focused sample and assigned expertise must be verified before the signed offer. No WCAG certification or quantified outcome is claimed.
08ACCEPTANCE, OWNERSHIP & RISK
The handoff is
part of the build.
WCCTC should be able to maintain the site and select another qualified provider later. Client-controlled accounts, reusable CMS blocks and a documented release make that practical.
Four things to verify before acceptance
The retained record
A completed content ledger and tested legacy URL map, including the dated archive.
The accessible release
A consultant conformance report tied to the tested templates and document set, with fixes, retests and documented exceptions.
The staff routine
A publishing rehearsal covering meeting fields, documents, approved procedural text, corrections and search.
The transferable system
Client accounts, source, database and media exports, dependency/license records, maintenance guidance and a restore procedure.
Content or source-file gaps
Reconcile the agency’s list at kickoff, identify missing editable files early, and assign a resolution before affected migration work starts.
Review or scope changes
Use consolidated staff feedback and agreed checkpoints. Record the effect of any material change before approving additional work.
Launch and continuity
Use staging, a pre-cutover backup, tested redirects and a documented recovery procedure. Confirm who owns updates and backups at handoff.
Privacy and measurement
Keep production forms limited to necessary information. Agree measurement and retention with WCCTC; do not make an analytics dashboard or an unrequested integration a condition of using the website.
09THE NEXT STEP
A public website
WCCTC can keep improving.
An established platform. A defined document strategy. Clear public journeys. A practical staff handoff.
Explore the working tasks, review the scope and discuss the recommendation with Ari. The signed formal response will remain the procurement record; this page makes the proposed experience and delivery plan easier to inspect.
Review version, not a signed offer. The base fee and applicant presentation are approved. Ari Raphiel is the principal contact; the final cover must carry an authorized signature. References, assigned expertise, team availability and agreement/insurance documentation must be finalized before submission. No proposal has been sent through this page.