Concept B · Region Atlas
About this concept
Region Atlas is one of three directions Clearview built for GHRPC’s Website Development Services RFP. It is a working website, not a picture of one, so its ideas can be clicked, sorted, tabbed through and read aloud before anyone commits to them.
Content captured from ghrpc.org on 22 Sept 2026 · Updated 23 Sept 2026
Why we built it
GHRPC’s work is organized by place. A hazard mitigation plan belongs to a county. A collection event happens in a town. A grant lands in one community and serves eleven. So this concept starts where the work starts: with the region itself, drawn as a map you can choose from, and backed at every step by a list or a table that says the same thing in words.
GHRPC also told us what today’s site cannot do: attach the documents and reports that funding agencies and the public need, and put a map, a data table or a spreadsheet on a page rather than hand out a link to a PDF. The hazard mitigation data page is the demonstration: a map, a summary, a sortable HTML table, and a document that arrives with a plain-language summary attached.
The eight pages
- Region map The home page. Choose a county on the map or from a list and see what GHRPC does there.
- Harrison County A county page: its plan, its meetings and events in date order, flood plain permits and who represents it. One template for all eleven counties.
- Hazard plans The data page: map, legend with counts, sortable table and a document with its summary.
- Meetings Agendas and minutes for five bodies, with the board-day pattern and an honest “minutes not yet posted” where that is the case.
- Public comment The open Chillicothe item on a map, how to comment today, and the online comment pattern.
- Solid Waste District A program page: collection events on a map and in a table, fees, grants and goals.
- Documents The archive, filtered by type and program; agendas and minutes open their meeting record.
- About this concept This page.
The map
The county shapes are real. They are the U.S. Census Bureau’s county boundaries (TIGERweb, Counties layer, 2026), queried as GeoJSON and drawn straight into each page as SVG: text labels, keyboard focus, no picture of a map and no embedded map service. The scale bar is computed from the same geometry. Town points are Census internal points for each town, not street addresses.
On the live site, GHRPC’s own maps take their place the same way. Amanda George exports a layer from ArcGIS Pro as GeoJSON, and the site draws it in the page. GHRPC keeps its Esri workflow; the website simply stops flattening maps into PDFs.
Every map has a twin in words. On the home page and the data page, each county is a real control: Tab reaches the map, the arrow keys move from county to county in the direction you press, and the selection is announced. A county list sits beside the map for phones and keyboards, and the tables carry the same facts.
What it is not
- It is not the official GHRPC website. Nothing here is published by GHRPC. The official site is ghrpc.org.
- It is not the full site. Eight pages, chosen to show a home page, a county page, a data page, meetings, public comment, a program page, the archive and this note. The real information architecture would be set with staff in the remote sessions GHRPC asked for.
- The documents are not hosted here. Every document link opens the original post on ghrpc.org. We have not copied GHRPC’s files.
- Nothing here submits anything. The comment form sends nothing and says so. The filters and sortable columns run in the page. There is no account, no sign-in and no back end in this concept.
- No invented facts. Every date, fee, address and figure comes from ghrpc.org as captured on 22 September 2026. Where the source is silent, the page says so (“Minutes not yet posted”, “Closing date: not stated on ghrpc.org”) rather than guessing. Where a count is our own tally of a published list, the page says that too.
What is labeled as concept or proposal
A few things on these pages show how the live site would behave rather than what ghrpc.org says today. Each one is labeled where it appears:
- Concept slots: “Next meeting: appears here when staff post the agenda” on the meetings page, the closing-date slot on the public comment page, and the next-item slot on the Harrison County page.
- The comment form, which shows the pattern and sends nothing.
- “Our proposal” blocks: how staff add a meeting, what happens after a comment, one template for eleven county pages, and documents as pages.
The images are GHRPC’s own photographs from ghrpc.org.
How it was made
Plain HTML, one stylesheet and one small JavaScript file, all of it ours and none of it fetched from anywhere. The pages work without JavaScript: the menu stays open, the county facts show as a list and the meetings show grouped by body. JavaScript adds the county selection, the filters, the sorting and the phone menu.
Accessibility, checked not claimed
One h1 per page and no skipped heading levels. A skip link and visible focus on everything interactive, including each county. Tables use captions and th scope; sort buttons sit in the header cells with aria-sort. Every form control has a label. Contrast meets WCAG AA in every state, including the current page in the menu. Motion stops for visitors who ask for reduced motion. Every page is tested with axe-core against WCAG 2.0, 2.1 and 2.2 A and AA plus best practice.
Where it is hosted
This concept is built on Nanopage, an AI-assisted site platform that our CTO, Jasmin Ihtijarevic, is involved in building. It’s one of three platforms in our proposal, at the same price. The same design can be built on WordPress or a purpose-built CMS.
How we handle it
If this direction is the one GHRPC picks, the build follows the same shape as the concept.
- Documents are records, not uploads. Each document gets a title, a summary, a type, a program, a date and the counties it concerns. Those fields make the archive filter and the county pages assemble themselves, and let staff add or remove an annual report, a newsletter or an audit without a developer.
- Meetings are records too. One form per meeting; the minutes join the agenda on the same record.
- Maps stay GHRPC’s. ArcGIS Pro layers are exported and drawn inline, as on these pages.
- Tables come from spreadsheets. An Excel file becomes an HTML table on a page, with the file still attached for anyone who needs the original.
- Staff sign in with Microsoft 365. No extra password for a ten-person office.
- Training, then a light touch. Remote sessions on look and feel and information architecture during the build, training for the whole office at launch, and support kept deliberately limited afterward, as GHRPC asked.
Talk to us
This concept was built by Clearview as part of our response to the Website Development Services RFP. The other two concepts take different directions; we would rather show three and talk than guess once.