This repository was archived by the owner on Sep 11, 2026. It is now read-only.
Repository navigation
Drop the offline-save/file:// claim from published copy - #11
Merged
Merged
Conversation
Michal's ruling: drop the offline-save feature from the site rather than port it to the wizard-web Astro app or fix the app's asset paths to make it true there. Astro emits root-absolute /_astro/... paths, so a saved copy's CSS/JS 404s under file:// — the claim would be false the moment wizard-web takes over serving markdownwizard.app. This repo's own copy still makes the claim, and it stays the live text until the cutover PR lands, so it comes out here too rather than waiting for the swap to silently retire it: - docs.html "Working offline": dropped the save-locally sentence, kept "the editor keeps working after the page has loaded, with no network connection" (still true, and distinct from the save/reopen claim). - privacy.html "Your document": reworded the "still available offline" bullet to the same narrower, still-true claim; dropped the sentence about Plausible not loading when opened from a saved file:// copy, since that describes a workflow no longer being advertised. Deliberately NOT touched: js/analytics.js's file://-protocol guard and tests/e2e.mjs's "file:// operation" suite. The underlying capability still works today and isn't being disabled — only the published promise that it's a supported way to use the product is being retired. Both still pass (`node tests/e2e.mjs`, `node tests/csp-check.mjs`). Filed so a future reader diffing old vs. new copy finds this commit instead of assuming the offline-save section was lost in the wizard-web migration, the way the troubleshooting section actually was (see wizard-web#118). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EQYeUULNUFx2m5nm6fCLwj
MichalAFerber
marked this pull request as ready for review
September 10, 2026 05:53
MichalAFerber
enabled auto-merge (squash)
September 10, 2026 05:53
MichalAFerber
approved these changes
Sep 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
While comparing this repo against its wizard-web Astro port before adding it to wizard-web's deploy matrix, I found the port had silently dropped the claim that you can save the whole app locally and run it from a
file://copy. I checked rather than assumed the omission was a regression: Astro emits root-absolute/_astro/...asset paths, so a saved copy of the Astro build's CSS/JS 404s underfile://— the claim would be false the moment wizard-web takes over servingmarkdownwizard.app.Michal's ruling on that finding: drop the offline-save feature from the site, rather than port the claim or fix the Astro app's asset paths to make it true there.
What
This repo's own copy still makes the claim today and stays the live text people read until the wizard-web cutover PR lands, so it comes out here too rather than waiting for the swap to silently retire it:
docs.html"Working offline": dropped the save-locally sentence. Kept "the editor keeps working after the page has loaded, with no network connection" — still true, and a distinct claim from saving/reopening a copy.privacy.html"Your document": reworded the "still available offline" bullet to the same narrower, still-true claim. Dropped the sentence about Plausible not loading when opened from a savedfile://copy — it describes a workflow no longer being advertised.Deliberately not touched:
js/analytics.js'sfile:-protocol guard andtests/e2e.mjs's "file:// operation" suite. The underlying capability isn't being disabled today, isn't broken, and the guard is harmless defensive code either way — only the published promise that this is a supported way to use the product is being retired.Naming this so it doesn't come back: someone diffing old vs. new copy in six months could reasonably assume the offline-save section was lost in the wizard-web migration, the same way the troubleshooting section actually was (wizard-web#118). It wasn't lost — it was deliberately cut, for the
/_astro/reason above. This PR body and commit message are the record.Verification
node tests/e2e.mjs— all checks pass, including "file:// operation (offline / double-click use)", unaffected since the capability itself is untouched.node tests/csp-check.mjs— clean, no CSP violations.Not related to the deploy-matrix cutover
This is a copy fix only. It does not touch
.github/workflows/deploy.yml— the standalone repo keeps deploying as-is until the separate matrix-cutover PR pair (wizard-web#117, #118, and the still-to-come matrix-addition + standalone-deploy-disable pair) lands.🤖 Generated with Claude Code
https://claude.ai/code/session_01EQYeUULNUFx2m5nm6fCLwj