Skip to content

Publish the first LastCode Pages release #164

Description

@lastobelus

Target

Implement this ticket in lastobelus/lastcode-docs after validation and the managed updater are ready.

Acceptance

  • Deploy the production VitePress artifact from docs main to the github-pages environment.
  • Run the same frozen validation command before deployment.
  • Retain the deployment artifact for one day.
  • Smoke-check the home page, all ten launch routes, and every registered README media URL at https://lastobelus.github.io/lastcode-docs/.
  • Leave the previous site live when a build or deployment fails.
  • Report a failed deployment through the existing docs incident path.
  • Do not add a preview service, deployment database, rollback system, gh-pages branch, or committed build output.

Retry the workflow or publish a follow-up change when deployment fails. Do not build a separate release controller.

Activity

  1. lastobelus commented on Oct 6, 2026

    @lastobelus
    OwnerAuthor

    Carry forward the site-shell interaction QA deferred under closed #154.

    Before calling the first Pages release complete, verify responsive navigation, the narrow-screen drawer, appearance selection, keyboard focus, the skip link, and page navigation in the actual docs site. The earlier build checks and approved visual prototype did not complete these interaction checks. This is documentation-site QA, not mobile product QA.

    Keep the existing checks for all ten public routes and registered README media URLs. The merged docs PRs do not establish that this launch issue is complete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions