What adding a gateway community actually looks like
Your RFP says two people will run this site. That claim is only worth anything if the editing experience is built for them, so here is the whole task, start to finish: one staff editor adds Unalakleet as a gateway community, and a board reviewer publishes it. Six steps. No developer.
Why this is the prototype that decides the project. A redesign that looks beautiful and is miserable to edit goes stale in a year — which is, with respect, roughly what happened to the current site, and not because anyone did anything wrong. The content model above is the thing that prevents it: structured fields rather than a blank editor, accessibility enforced at the point of entry rather than audited afterwards, and a review step that does not depend on anyone remembering.
Acceptance is tested, not asserted. Before we hand over, an Alliance editor completes three tasks like this one unaided, with us watching and not helping. If they cannot, that is our problem to fix, not yours to live with.