Publishing
Dashboard
Everything that needs a person, in one place. None of it needs a developer.
Pages published
40
of 40 planned
Documents in archive
141
286 pages
Reviews overdue
6
oldest 94 days
Awaiting approval
3
2 editors waiting
Members
25
4 renew this month
Newsletter subscribers
125
all consented
Why a dashboard at all. The failure mode for this site is not a bad launch, it is silent drift. Your current site has an events page last updated in June 2020 and a program still described as “under development”, and your newsletter went on hiatus for eight months in 2024 without a word on the page. None of that happened through carelessness — it happened because nothing ever told anyone. This screen tells them.
Needs your attention
| Item | Type | Owner | Status | Age | Action |
|---|---|---|---|---|---|
| The Tripod archiveHiatus Jan–Aug 2024, then monthly to seasonal, unexplained on the page | Page | Communications | Review overdue | 94 days | |
| EventsMost recent entry is dated June 2020 | Page | Communications | Review overdue | 71 days | |
| Junior TrailblazerPatch described as “under development” | Page | Education lead | Review overdue | 63 days | |
| GalenaCommunity page has no content and is held unpublished | Community | Unassigned | Awaiting content | — | |
| FY2027 trail project grantsSubmitted by an editor, 2 accessibility warnings | Announcement | Editor | Awaiting approval | 2 days | |
| Annual report, FY2024Untagged; photo captions need alternative text | Document | Accessibility | In triage | 5 days |
Most rows here come from your current site
We walked iditarod100.org on October 31, 2026 and wrote down what we found — the empty Galena page, the events page last updated June 2020, the patch still “under development”. Statuses, owners and due dates are illustrative, so you can see how the screen behaves.
Publishing
Document archive
141 files, 286 pages. Each one triaged for accessibility, given a destination, and tracked until it’s done.
Accessibility remediation progress — illustrative mid-project state, February 19, 2027. Titles and page counts are a representative sample of your archive’s shape, not the reconciled inventory. 0 of 141 files complete · 0%
This screen is the project. Your archive is the Alliance’s institutional memory and, on a federally funded award, its largest accessibility exposure. Most vendors will price migration as “move the files”. We counted them, and we track each one to a named outcome that you can audit at any time.
“Accessible equivalent” is not a shortcut. Where an original scan must be preserved for the historical record, we publish a complete accessible version alongside it — carrying the same information and function, not a summary. Both remain available.
Inventory
| File | Collection | Year | Pages | Accessibility status |
|---|
Publishing
Pages
Forty pages, each with an owner and a review date, so nothing goes quiet without somebody being told.
Review dates are the whole mechanism. A page type carries a review interval — governance twice a year, visitor guidance before each season, history rarely. When a date passes the page appears on the dashboard. That is the difference between a site that is current in 2029 and the one you have now.
| Page | Template | Owner | Review every | Next review | State |
|---|
Publishing
Communities
Nine community pages, each written with the community it’s about. A page stays unpublished until someone local has signed off on it.
Galena is the test case. Your current site publishes a Galena page containing the words “no copy at this time”. Empty pages get indexed, get found, and tell a visitor the organization is not maintaining its site. Here the page exists, has an owner, and simply is not public yet — which is the honest state of it.
Image rights are tracked, not assumed. Photographs of communities and of people need permission. The column exists because the Alliance, not the vendor, is accountable for it.
| Community | Region | Content owner | Image rights | State | Action |
|---|
People
Contacts and consent
One place for all of it. Every record carries where it came from, when, and whether that person actually agreed to be emailed.
Members
25
4 renew within 30 days
Donors
38
11 gave more than once
Email subscribers
125
100% with recorded consent
Purchasers without consent
17
not emailed, by design
The seventeen matter. Seventeen people bought something and did not opt in. A great many organizations quietly add those addresses to the newsletter. We will not, and the system will not let an editor do it by accident. That single rule protects your sending reputation, your donor relationships and your position if anyone ever asks.
Attachment 1 asks for “easy collection and management of email addresses for bulk emailing”. Easy is the consent field being captured automatically with a timestamp and the page it came from — not a spreadsheet someone merges by hand twice a year.
| Contact | Type | Email consent | Source | Recorded | Renewal |
|---|
Export prepared. The file records who exported it and when, and is written to the audit log.
People
Access and roles
Four roles, least privilege, and two-factor on anything that can change configuration or see personal data.
RFP §4.4 and §4.6. Editors draft, a reviewer publishes, an administrator holds configuration. Nobody needs to touch the theme, the plugin list or the template files to do their job — which is what keeps a small volunteer-supported team safe. Our own access is temporary and is removed at handover, with a written record.
| Capability | Editor | Reviewer | Administrator | Kode Kinetics |
|---|
Accounts
| Account | Role | Two-factor | Last sign-in | Expires |
|---|---|---|---|---|
| A. HeckartCommunications | Reviewer | On | Today | — |
| Primary editorAlliance staff | Editor | On | Yesterday | — |
| Backup editor 1 | Editor | On | 4 days ago | — |
| Backup editor 2 | Editor | Invited | Never | — |
| Alliance administrator | Administrator | On | 2 days ago | — |
| Kode Kinetics deliveryTemporary project access | Administrator | On | Today | Removed at handover |
The last row is the point
Our access is temporary, visible to you, and removed at handover with a written record. The Alliance owns the hosting account, the domain, the payment provider and the code repository from day one. If you ever want a different vendor, nothing has to be prised out of us.
Reach
Analytics and SEO
What we measure, what we deliberately don’t, and whether the site can be found. RFP §4.4 asks for analytics; Attachment 1 asks for clear hierarchy and internal linking.
Pages indexed
38
of 40 published
Redirects in place
180
every old URL mapped
Orphan pages
2
no internal link points to them
Broken links
0
checked weekly, reported here
Structured data
6
types validating clean
Median page weight
214 KB
2.1s on rural 3G
Findability, item by item
| Check | State | Why it matters to you |
|---|---|---|
| Heading hierarchy | Clean | One h1 per page, no skipped levels. The same structure a screen reader uses is the one a search engine uses — you get both from one piece of work. |
| Internal linking | 2 orphans | Every gateway community, resource and place record links to and from its section. Two pages currently have no inbound link; this screen is how you find them before a visitor doesn’t. |
| Redirects from the old site | 180 mapped | Server-level 301s from every current iditarod100.org URL. Nothing you have ever shared or printed stops working on launch day. |
| Structured data | Validating | Organization, Event, Article, Place, Product and BreadcrumbList. How a search engine learns that Unalakleet is a place on a trail rather than a word. |
| Document findability | 141 titled | Every archived file carries a real title, date and description rather than newsletter-final-v2.pdf. This is most of why the archive becomes searchable. |
| Page weight on a rural connection | 214 KB | Your primary audiences are people already on the trail and the communities along it. A page that needs ten seconds on a weak signal is a page nobody reads. |
What we measure, and what we refuse to
Measured: page views, which resources get opened, which journeys complete a donation, membership or purchase, and which searches return nothing — that last one tells you what to write next.
Not measured: no cross-site tracking, no advertising pixels, no selling of visitor data, no cookie banner demanding consent for surveillance you never wanted. Analytics run privacy-first and in a US region, so the Alliance owns the numbers and nobody else does.
Outbound payment actions are counted as checkout started only. What happens on the processor’s side stays with the processor — see the architecture in Appendix E.
Reach
Room to grow
RFP §4.1 asks for compatibility with future buildouts — e-courses, multimedia collections, virtual tours. None of them are in this build. Here is what each would take, so the answer is a number rather than a promise.
| Future buildout | Needs a rebuild? | What it actually takes |
|---|---|---|
| E-courses For Educators, Professional Development |
No | A new content type with lessons as ordered records, plus progress tracking if you want it. The roles, review workflow and templates already exist. Weeks, not months, and no change to anything already built. |
| Multimedia collections Oral history, documentary, podcast |
No | A media record type sitting beside the resource library and filtering with it. The real cost is not the build — it is captions and transcripts, which WCAG 2.2 requires and which we have deliberately excluded from this fee rather than hide. See finding 3 in section 4 of our proposal. |
| Virtual tours Trail segments, roadhouses |
Partly | The place records and the map are already here, so a tour is an ordered sequence of existing records. A 360° or interactive-map tour needs a third-party viewer, which brings a cost, a vendor and an accessibility obligation. We would scope it honestly rather than bolt it on. |
| Authenticated member area Renewals, member-only content |
No | Priced as an option in section 8 of our proposal, not assumed. The contact repository and role model it needs are built in this phase either way. |
| True interactive GIS map Attachment 1, “Maps (interactive)” |
Partly | Launch ships a route schematic with linked place pages. A real basemap is a real recurring cost, itemised separately so you choose it with the number in front of you. |
Why none of this needs the site rebuilt
Thirty-one sitemap nodes resolve to eight reusable page types with structured fields. A new kind of content is a new type alongside them, not a new website. That is what “scalability — growth without disruption” in Attachment 1 means in practice, and it is the part of this build that most repays getting right at the January design gate.
The one thing that would force a rebuild is a content model invented page by page as the site grows. That is the failure we are designing against.
Release
Launch readiness
The go / no-go board for March 1, 2027. You’re the one who signs it.
Pages migrated
40/40
100%
Documents resolved
141/141
published or approved disposition
Redirects mapped
181
40 pages + 141 files
Open issues
2
0 launch-blocking
Restore rehearsal
Pass
Feb 24 2027
§4.7 and the acceptance table in section 5 of our proposal. This is the same evidence, shown as a screen rather than a promise. A launch-blocking defect is one that prevents a critical journey, exposes sensitive data, creates a material accessibility barrier, or prevents recovery. Anything else is scheduled with your written agreement, with an owner and a date.
Readiness checks
| Check | Evidence | Result | Blocking? |
|---|---|---|---|
| Content and migration reconciled | Every approved page and document maps to a live destination or an approved disposition. Final crawl: no broken internal links. | Pass | Yes |
| Redirects for every changed URL | 181 old URLs mapped; priority inbound URLs validated individually. | Pass | Yes |
| Core journeys tested | Resource finding, contact form, newsletter signup, product purchase, donation, membership. Payment records verified with the Alliance. No live charge taken. | Pass | Yes |
| WCAG 2.2 AA and Section 508 | Automated scan of all published pages plus manual keyboard, focus, zoom and reflow, contrast and screen-reader testing on every template. Written conformance report issued. | Pass | Yes |
| Reflow and browsers | No horizontal overflow at 320 CSS pixels. Chrome, Edge, Firefox, Safari, iOS Safari and Android Chrome, with versions recorded. | Pass | Yes |
| Security configuration | No unresolved critical or high findings. Privileged roles and two-factor verified. No secrets or real donor data in test fixtures. | Pass | Yes |
| Backup and restore | Restore rehearsed in staging on February 24 and succeeded. Rollback plan written. | Pass | Yes |
| Editor independence | Primary editor and two backups each created a page, replaced a document, updated an announcement and exported contacts, using only the handover guide, unaided. | Pass | Yes |
| Performance on representative pages | Lab LCP 2.1s, CLS 0.04, INP 140ms on the agreed mobile profile, inside the committed targets. Third-party impact documented. | Pass | No |
| Two cosmetic issues outstanding | Caption alignment on one resource template; a wrapping label in the store on very narrow screens. Owners and dates agreed. | Scheduled | No |
Written go / no-go
Launch requires the Alliance’s written approval. You receive the test results, the issue register, the deployment and rollback plan, an account inventory and the full handover pack before you are asked to decide.
Go decision recorded against this release, with the approver, the timestamp and the evidence pack attached.