diff --git a/.abstract.md b/.abstract.md deleted file mode 100644 index e2d919bd4e..0000000000 --- a/.abstract.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -type: atlas -layer: l0 -corpus: code-repo -scope: top -root: pascalandy-blog-paper -parent: -date_updated: 2026-03-13 ---- -# Abstract - -This repo is an Astro 5 blog codebase with Bun/Just tooling and a large Markdown post corpus. Use it to locate canonical site config, route behavior, content schema, workflow commands, or published posts. Treat the atlas as a routing layer only; read source files for exact behavior, rendering, and frontmatter rules. - -## Use this when -- you need the fastest entry point for setup, local QA, or build commands -- you need canonical site config, theme settings, or content schema -- you need the implementation behind blog routes, tags, or post visibility -- you need to edit published posts or public workflow docs -- you need to separate maintained project docs from scratch notes - -## Main areas -- `README.md` — setup and high-level repo entry point -- `src/` — Astro app code, routes, layouts, utilities, and config -- `src/data/blog/` — published posts and public development workflow docs -- `scripts/` — maintenance helpers for tags, imports, and frontmatter cleanup -- `./.overview.md#reference-map` — Detailed map - -## Out of scope -- generated output in `dist/`, `.astro/`, `cache/`, and `public/pagefind/` -- secrets or environment files such as `.env` -- treating `dev_notes/` as canonical project documentation diff --git a/.overview.md b/.overview.md deleted file mode 100644 index b35b7836db..0000000000 --- a/.overview.md +++ /dev/null @@ -1,51 +0,0 @@ ---- -type: atlas -layer: l1 -corpus: code-repo -scope: top -root: pascalandy-blog-paper -parent: -date_updated: 2026-03-13 ---- -# Overview - -## Corpus Type - -`code-repo`. The entry points that shape navigation are `README.md`, `AGENTS.md`, `package.json`, `astro.config.ts`, and the executable files under `src/`. `src/data/blog/` is large, but it is governed by code and schema files rather than standing alone as a separate docs corpus. - -## Navigation Strategy - -Start with `README.md` for setup, then use `AGENTS.md` for repo-specific workflow and architectural conventions. For behavior questions, go straight to `src/pages/` and follow imports into `src/layouts/`, `src/components/`, and `src/utils/`. For content questions, trust `src/content.config.ts` plus the files in `src/data/blog/`; use `dev_notes/` only as working context. - -## Reference Map - -| Path | Role | Use When | Trust Level | Notes | -| --- | --- | --- | --- | --- | -| README.md | entry-point | You need setup, stack, or the primary repo starting point | high | Shortest path to local commands and project framing | -| AGENTS.md | authoritative | You need repo-specific agent workflow, architecture, or coding rules | high | Stronger than ad hoc notes when workflow guidance conflicts | -| src/config.ts | authoritative | You need site metadata, theme selection, or publish timing rules | high | Defines `SITE`, theme catalog, and active theme | -| src/content.config.ts | authoritative | You need blog schema, loader rules, or ignored-file behavior | high | Canonical frontmatter schema for `src/data/blog/` | -| src/data/blog/ | authoritative | You need published posts or the public workflow-doc corpus | high | Markdown source of truth; `_`-prefixed files are excluded by loader rule | -| scripts/ | implementation | You need cleanup or migration helpers for content maintenance | medium | Useful for tag, import, and filename hygiene; not the main runtime path | -| src/pages/ | implementation | You need route behavior, static path generation, or page-level rendering | high | Start here for `/`, `/blog/`, `/tags/`, `/search/`, and RSS routes | -| justfile | reference | You need the supported dev, QA, CI, build, or cleanup commands | high | Prefer this over memory or stale notes for command names | -| src/data/blog/dev_workflows/ | tutorial | You need published workflow guidance for contributors or agents | medium | Public-facing how-to material; useful, but not executable truth | -| dev_notes/ | archive | You need scratch context, plans, or abandoned ideas | low | User scratchpad; may lag behind current implementation | - -## Retrieval Routes - -- If you need local commands or quality gates, read `README.md` -> `justfile` -> `.github/workflows/ci.yml` when CI behavior matters. -- If you need theme, metadata, or publish-window behavior, read `src/config.ts` -> `astro.config.ts` -> `src/utils/postFilter.ts`. -- If you need content schema or why a post is missing, read `src/content.config.ts` -> the target file in `src/data/blog/`. -- If you need page behavior or URL generation, read `src/pages/blog/[...page].astro` or `src/pages/blog/[...slug]/index.astro` -> imported layouts/components/utils. -- If you need contributor workflow docs, read `src/data/blog/dev_workflows/` first; only consult `dev_notes/` for non-canonical working context. -- If you need tag or frontmatter maintenance, read `justfile` -> `scripts/check-tags.sh` -> the relevant helper in `scripts/`. - -## Gaps and Cautions - -- `dev_notes/` looks important at a glance, but `AGENTS.md`, `justfile`, and executable source files are the safer defaults. -- Command guidance is split between `justfile` and public workflow posts under `src/data/blog/dev_workflows/`; when wording differs, prefer executable files. - -## Child Maps - -- No child maps currently needed. diff --git a/AGENTS.md b/AGENTS.md index f6c14782c5..ccffe18865 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -1,3 +1,10 @@ +## Project overview using progressive disclosure + +1. Read and understand: `.napkin/NAPKIN.md` +2. run `napkin overview --json` + +--- + # Project Preferences ## Browser, esign/Style diff --git a/src/data/blog/vinyl.md b/src/data/blog/vinyl.md index f61ba739ff..f631f46857 100644 --- a/src/data/blog/vinyl.md +++ b/src/data/blog/vinyl.md @@ -8,7 +8,7 @@ description: "J'ai posé cette question sur ce groupe Facebook et j'ai reçu plu ogImage: ../../assets/images/og-legacy/2021/11/vinyl-1.jpg --- -Voici la liste ultime pour faire vos prochaines trouvailles! +Voici la liste ultime pour faire vos prochaines trouvailles: ## **Indies**