No. The GIS map continues to be served by the existing GIS platform (ArcGIS Online, MapServer, or similar). SleekRank handles the textual reference layer: the pages that describe each category in plain language. The two reference the same source data so they stay in sync, but the spatial rendering stays in GIS.

As a markdown or HTML text column on each category row. The intent paragraph is often the most-quoted text from a comprehensive plan, so keeping it on a dedicated URL makes it citable. A selector mapping renders the intent block on every category page exactly as adopted.

Yes, with a small extension. Add columns for acreage at adoption, current acreage, and percent change, plus a simple sparkline rendered from a JSON history field. The page becomes a small dashboard for that category without leaving the reference template.

Edit the affected row in the source and the page refreshes at the next cache interval. For amendments with effective dates, add an effective_date column and gate any field changes behind that date with a small selector mapping; the page can show the pending change with a banner until the date arrives.

Add a status column (adopted, draft, repealed) and use a meta mapping that sets robots=noindex when status is draft or repealed. Adopted categories index normally, drafts stay out of search until they are adopted, and repealed categories keep their URL for archival purposes while staying out of the index.

Yes. Add a policies array column listing the plan policy numbers and titles that govern the category. A list mapping renders them as links to the plan document section anchors, so the category page surfaces both the rule and the policies behind it.

Run a second page group for subarea plans with its own URL pattern (/plans/{slug}/) and base template. Cross-link from the main category pages to any subarea plans that modify the category in a specific geography.

The pattern is identical at any scale. Counties often have land use categories that distinguish urban service areas from rural and resource land. The page group renders one URL per category, and the categories stay distinct from the zoning districts that implement them.