Add the site sources, a Common questions section, and npm keywords - #2
Merged
Merged
Conversation
The deployed page inlines dist/, so it needs rebuilding on every release — which is only maintainable if the template and build script live in the repo. docs/blog/README.md documents the rebuild, the verification pass, and the two search-engine steps that cannot be done from here. Also expands package.json keywords. npm search is a bigger discovery channel for a package like this than search engines are, and the previous five missed the terms people use: optimistic-updates, rollback, aria-live, a11y. No keyword for anything the runtime does not do — there is no redo. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Follow-up to #1. The site is already redeployed with everything here — this PR is the source it was built from.
Why it belongs in the repo: the deployed page inlines
dist/undoable.global.js, which is what makes the demo on it real rather than a mock. That means the site holds a copy of the build and needs rebuilding on every release. That is only maintainable if the template and build script live here.docs/blog/README.mddocuments the rebuild, the Chromium verification pass, and the two search-engine steps that cannot be done without your login.What is already live
TechArticle+FAQPageJSON-LD, mirroring those answers exactly.sitemap.xml, and an IndexNow key so Bing, Yandex, Seznam and Naver can be notified without an account. Submission returned202 Accepted.In this PR
package.jsonkeywords: addsoptimistic-updates,rollback,a11y,aria-live,framework-agnostic,zero-dependencies. npm search is a bigger discovery channel for this package than search engines are. Nothing added for behaviour the runtime does not have — there is noredokeyword..gitignorefor the generatedsite/andpost.html.Two things that still need you
/robots.txt— belongs to thesharma-open-source.github.ioroot repo, not this one.🤖 Generated with Claude Code