​

Kokonut Public Site — Experience & Release QA

Scope: PR C — site-wide visual/experience polish after the Narrative Foundation and Ecosystem Alignment PRs.
Basis: KOKONUT_MESSAGING_GUIDE.md, current Mintlify docs.json and the existing custom React/MDX components.
Status: Source changes implemented; browser/Mintlify preview not yet validated. This checklist does not certify production behavior.

​

Editorial and navigation contract

• Kokonut is open coordination infrastructure for regenerative agriculture. Real farms and their local operators come first; DAO, MRV, Intelligence, finance and agents are supporting layers.
• The main site CTA is Get involved; it leads to Kokonut’s collaboration page. The shared footer still provides a direct meeting link for people who specifically want to connect.
• The shared footer should link How Kokonut works, Kokonut 101, Framework, Syntropic Agent, Builders and Traction. Its source/evidence path should lead to the Adelphi Hub and not imply certification.
• Every custom-page primary CTA must match its actual destination. For example, the Builders page links to its six-project repository directory, not a misleading single-repository GitHub URL.
• The Traction collection is a historical source archive, not a live metrics dashboard or an unqualified independent endorsement; the source library provides the distinctions.

​

Interaction and accessibility contract

• Standard Mintlify navigation already includes a Skip to main content affordance. Avoid duplicating it at the React-snippet layer.
• A keyboard-visible focus ring is required for anchors, buttons, inputs and explicitly focusable custom regions. Use Kokonut green on light surfaces and yellow on dark hero/feature panels.
• Important CTA/jump links and filter/selector buttons should provide at least a 44px target height without sacrificing their accessible names or selection states.
• Stateful explorers should expose selections with aria-pressed or another appropriate control state; changing the attribute must not remove selected-item styling.
• Live text changes should be announced appropriately, but avoid constantly announcing unrelated sections.
• In the RWA map, selected challenge items expose aria-pressed, their details have a stable target ID, empty results expose role="status", and automatic category scroll obeys prefers-reduced-motion.
• Decorative avatar and diagram imagery should not introduce redundant descriptions. Informative images must have meaningful alternative text.
• Users requesting reduced motion must not be forced through animations or smooth-scroll transitions.
• Do not introduce new token prices, unreviewed ecological claims or financial-rights representations during a visual polish.

​

Preview matrix — manually run before merge

​

Page-specific regression scenarios

​

Verification boundary

Source-level QA can validate: route references, JSON parsing, markup balance, CSS bracket balance, control attributes, known code paths and absence of unintended changes. Source-level QA cannot validate: Mintlify build success, runtime React mounting, actual focus/contrast in a browser, breakpoints on physical devices, live remote assets, third-party embeds, or deployment state. Do not mark the browser checks above as complete without inspecting an actual preview.

​

Release review record

• PR: to be filled after creation.
• Reviewer: to be assigned.
• Preview URL: to be supplied by the GitHub/Mintlify workflow, if available.
• Decision: pending visual and accessibility review.
• After merge: recheck public pages and official external launch/source links for unexpected regressions.