Most planning departments already maintain a zoning matrix in a spreadsheet or a GIS attribute table. Either source works: a Google Sheet for staff edits, or a REST endpoint exposed by the GIS team. SleekRank pulls on a schedule and caches the results, so the public site does not hit the source on every page load.

As three array columns on the zone row. Each cell holds a list of use categories (single-family residence, accessory dwelling unit, multifamily, retail under 5,000 sq ft, and so on). List mappings render each array as a labeled bullet list on the zone page, so users can scan the rules without reading the legal text.

Yes. Add an ordinance_url or ordinance_section column to the data, and use a selector mapping to render a citation link at the bottom of every page. The public summary stays plain-language while the citation always points at the authoritative legal text for users who need it.

Run a second page group for overlays and a third for PUDs, each with its own URL pattern (/zoning/overlays/{slug}/ and /zoning/pud/{slug}/) and base template. Cross-link from the base zone pages via a list mapping that renders any overlays affecting that zone.

It complements the map. Users click a parcel on the GIS map, the popup shows the zone code, and the code links out to the SleekRank-generated /zoning/{slug}/ page for the human-readable rules. The map handles spatial lookup; SleekRank handles the textual reference.

Yes. Expose the use arrays as a JSON endpoint and add a small Alpine.js component to the ordinance index page that filters zones by allowed use. The endpoint reads the same data SleekRank uses, so the search results and the per-zone pages stay in sync.

Edit the relevant row in the source, and the affected page refreshes at the next cache interval. For urgent amendments, planning staff can clear the SleekRank items cache via WP-CLI to push the change immediately. The audit trail lives in the sheet revision history or the GIS edit log.

Yes. The pattern is identical: pull the county zoning matrix, render one page per district. Counties often have larger codes with more agricultural and resource districts, so the page count is higher, but the setup is the same. The sitemap registers every district URL automatically.