Skip to content
wiki.fftac.org

Improving Spiralist Org Navigation And Ux

**Site relevance:** Spiralist.org

**Memory type:** docs archive

**Source path:** Wiki.FFTAC.org/raw/system-archives/spiralist.org/docs-archive/2026-05-10/docs/research/Improving Spiralist.org Navigation and UX.md

**Size:** 2.2 KB

Summary

Improving Spiralist.org Navigation and UX

Source Headings

  • Improving Spiralist.org Navigation and UX
  • Stable Conclusions
  • What Was Removed
  • Current Use

Source Preview

This source file is short enough to preview directly on its source-memory page.

# Improving Spiralist.org Navigation and UX

Status: compressed research archive. The original audit contained a long public-page crawl, repeated route observations, and citation artifacts. Stable findings have been promoted into current docs and the runtime roadmap.

Canonical guidance now lives in:

- [Experience Layer](../experience-layer.md)
- [WordPress Runtime Roadmap](../wordpress-runtime/README.md)
- [Prompt Workspace Architecture](../prompt-workspace-architecture.md)
- [Manuscript Page](../manuscript-page.md)
- [Self-Operation and Peer Moderation](../wordpress-runtime/11-self-operation-and-peer-moderation.md)
- [Automated Testing Strategy](../testing/automated-testing-strategy.md)

## Stable Conclusions

- Keep Spiralist.org human-first. Do not make raw APIs, UAI/UAIX details, or machine payloads dominate reader-facing surfaces.
- Use task-oriented navigation before internal vocabulary. First-time users should reach manuscript reading, Workspace use, prompt running, participation, exploration, and resources without learning the full ontology first.
- Preserve the manuscript-first identity while letting prompt systems serve daily use.
- Add persistent search, visible breadcrumbs on deep pages, and mobile quick actions for high-value tasks.
- Use progressive disclosure for manuscript, symbol, graph, API, and governance details.
- Make prompt discovery practical: starter prompts, use-case filters, clear labels, runnable examples, and visible output samples.
- Keep API examples public and useful for builders without turning the site into a developer console.
- Keep participant safety visible: provenance, reset controls, moderation state, reversible publication states, and memory/runtime-path management.
- Treat page density and redundant sections as UX bugs when they slow the primary task.

## What Was Removed

- Crawl-specific page inventory that can drift quickly.
- Long examples of duplicated footer, legal, and machine-surface content.
- Repeated recommendations that now live in canonical docs.
- Raw citation placeholders from the original research pass.

## Current Use

Use this archive only as design-history context. For active implementation decisions, use the linked current-state docs and roadmap.
Website health report