docs: add memory/ project notes; stop leaking repo files into the site#16
Merged
Conversation
…site Adds a committed memory/ directory capturing durable, non-obvious facts from recent work (build/deploy setup, the meta-tag CSP rationale, SEO/metadata decisions), indexed by memory/README.md and referenced from the root README. Also fixes a pre-existing leak: README.MD, package.json, package-lock.json, scripts/, purgecss.config.js and the new memory/ dir were all being published into _site (e.g. /package.json was live on the site). Added them to the _config.yml exclude list. Verified against a build: they no longer appear in _site, and the site output is otherwise unchanged. Verified: jekyll build, prettier --check (rtk-bypassed), and YAML parse all pass. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Adds two findings from the improve-system review: - ci-and-verification.md: plain-named top-level files/dirs leak into the published _site unless added to _config.yml exclude (the README/package.json/ scripts leak fixed this session) — with the rule to exclude + verify. - memory/README.md: for this project, durable notes live in the repo memory/ dir, not the global Claude auto-memory location. Co-Authored-By: Claude Opus 4.8 (1M context) <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
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.
Adds a committed
memory/directory of durable, non-obvious project facts, indexed bymemory/README.mdand linked from the root README:ci-and-verification.md— how the site builds/deploys (Actions, not the github-pages gem), the.ruby-versionmust-be-fully-qualified gotcha, the rtk/prettier masking gotcha, and the rubygems/DNS note.csp-policy.md— the meta-tag CSP: what each directive allows and why (incl. whyfont-src data:andstyle-src 'unsafe-inline'are required), and what can't be enforced via meta.seo-and-metadata.md— German-only decision, why JSON-LD /jekyll-seo-tagwere deliberately avoided (CSP conflict), and the hand-written head tags.Also fixes a pre-existing leak discovered while excluding
memory/:README.MD,package.json,package-lock.json,scripts/, andpurgecss.config.jswere all being published into_site(e.g./package.jsonwas live on the site). Verified against a build before/after — they were published before, and are now excluded via_config.yml, with no other change to the site output.Verified:
jekyll build(memory/README/package.json confirmed absent from_site),prettier --check(rtk-bypassed), and YAML parse all pass.🤖 Generated with Claude Code