Skip to content

Lead the docs site with the evaluate sequence - #9

Merged
russwyte merged 1 commit into
mainfrom
docs/revamp
Oct 11, 2026
Merged

russwyte merged 1 commit into
mainfrom
docs/revamp

Conversation

@russwyte

Copy link
Copy Markdown
Contributor

Summary

  • The front page is the sequence: state and questions in, structured answers out. Specular 0.20 still writes a summary index, so afterBuild copies that page over index.html. It is not a sidebar item.
  • Chrome and install snippets advertise 0.1.0 when the raw version contains -ci, +, or SNAPSHOT. stripCi is not applied first (stripCi("0.1.1-ci") is 0.1.1, which is not published). ShipGroup stays 0.1.1.
  • Docs move to specular 0.20 and mermoid-ascent 0.2.0. Neither is on the published artifact. There is no docs client, so ascent-js is not on this classpath. Specular's heddle 0.9 and ascent-preview edges are excluded so the client stays on heddle 0.4 and zipx can resolve.
  • zipxWorkflowGenerate rewrote the workflows. ci.yml and zipx-release.yml did not change.

Test

  • docs/testFull
  • docs/specularSite
  • Headed Firefox against DocsServe at 1280 and 390: the stake, the sequence, and 0.1.0 are on the first page. The cite footer is github.com/early-effect/hexis/blob/<sha>/core/src/main/scala/hexis/client/SystemOne.scala#L21-L25.

The front page is state and questions in, structured answers out. Specular 0.20 still writes a summary index, so the build copies that page over index.html.

A raw version containing -ci, +, or SNAPSHOT advertises 0.1.0. stripCi is not applied first.

Docs use specular 0.20 and mermoid-ascent 0.2.0. Neither is on the published artifact. Specular's heddle 0.9 edge is excluded so the client stays on heddle 0.4.
@russwyte
russwyte merged commit bca6cf2 into main Oct 11, 2026
14 checks passed
@russwyte
russwyte deleted the docs/revamp branch October 11, 2026 00:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant