Ysopwnable
5065fcd520
Several guides use broad headings and repeat their summaries, making the main example harder to follow. This change names each task directly, keeps Notion's clipboard investigation in the main reading path, and moves the Markdown example and longer provenance into expandable details. The browser guide now opens the hosted example, and the first native CLI query works without a global install. The existing figures, prompts, source excerpts and comparison controls remain the teaching material. Provider details now fit narrow screens. The repository README links to all Showcases, and the website authoring docs share a signed design principle: a good website is like a good paper—easy to follow, clear and concise, with a clean, refined presentation. A new style guide and scoped AGENTS.md explain how to maintain that approach. Closes #985. Validation: - `python3 scripts/prepare-website.py` and `python3 scripts/verify-website.py`: 12 HTML pages, 183 local references, SVG XML, the six-file ZIP and the sole manual Pages publisher. - Oxfmt checks and `git diff --check`; `npm run check:fast` with Node.js 24.18.0. - Browser checks at both `/` and `/rea/`: 24 routes, 68 copy buttons, 20 comparison steps, two CSV exports, two ZIP downloads and eight viewport widths from 320px to 1440px. - Existing code excerpts, expanded details, keyboard access, no-JavaScript content, continuous cursor animation and reduced motion checked. Existing analysis and compiler-check evidence is retained; real native-provider verification and compiler replay were not rerun for these copy and layout changes. The homepage content and publication triggers are unchanged.
1.2 KiB
1.2 KiB
Website maintenance
A good website is like a good paper: easy to follow, clear and concise, with a clean, refined presentation.
— N0zoM1z0
Read README.md and style-guide.md before changing
website content, layout or figures. Use figures.md and evidence/
for asset notes and the source of case-study claims.
- Write English, direct headings and concrete instructions. Each paragraph should explain a new fact or action.
- Reuse the shared styles, prompts, figures and code-step components. Keep a case study focused on one question, with further examples in native details.
- Show what REA returns and how the agent uses it. Preserve source attribution, target identity and verification scope.
- Keep personal paths, account data, credentials and raw captures outside the public assets. Use generic inputs and label shortened display paths.
- Check both local root and
/rea/paths, mobile layouts, expanded details, copying and downloads. Runscripts/prepare-website.pyfollowed byscripts/verify-website.py. - Keep
website-pages.ymlas the sole, manual Pages publisher. Follow the publication procedure in the website README.