site: saving mode on the page, not just in the inlined bundle - #16
Merged
Conversation
0.4.0 shipped a feature the plugin's own page did not mention. It was technically "on" the page — the default nudge is a string in lib/core.js and build-site.mjs inlines that file — but a reader cannot see a feature because its text happens to be inside a <script> block. So the page argues for it: the readout is the default and stays the default, a number nobody acts on saved nothing, and here is the config line. The three properties that make it honest are stated where a sceptical reader is — same clock as the bill, weekends get no nudge, byte-identical inside a window so it does not roll the prompt cache. Rendered in a real browser at 1280 in both themes, no overflow.
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
0.4.0 shipped a feature the plugin's own page did not mention.
It was technically on the page — the default nudge is a string in
lib/core.jsandbuild-site.mjsinlines that file, socurl https://dsh.works/dsh-meter/ | grep -i "saving mode"returns hits. Areader cannot see a feature because its text happens to sit inside a
<script>block.
So the page argues for it now: the readout is the default and stays the default,
a number nobody acts on saved nothing, and here is the one config line. The
three properties that make it honest are stated where a sceptical reader is —
same clock as the bill, weekends get no nudge at all, byte-identical inside a
window so it does not roll the prompt-prefix cache.
Nav gets a
saving modeentry.Rendered in a real browser at 1280 in both themes: section lands, no horizontal
overflow.
npm test130 green, all three generated artifacts in sync.