Skip to content

docs: add RFC process for design discussions; fix post-#83 review notes#84

Open
marcelocra wants to merge 2 commits into
mainfrom
claude/devmagic-notes-and-docs
Open

docs: add RFC process for design discussions; fix post-#83 review notes#84
marcelocra wants to merge 2 commits into
mainfrom
claude/devmagic-notes-and-docs

Conversation

@marcelocra

Copy link
Copy Markdown
Owner

Summary

Two things: a home for design discussions (as requested), and a handful of small fixes from reviewing merged PR #83.

docs/rfcs/ — design discussions

Introduces the missing piece between "just a TODO.md" and the existing ADRs: a place for the process of reaching a decision (problem, context, every option considered, an append-only discussion log — including verbatim excerpts from AI pairing sessions), as distinct from ADRs, which stay short and record only the result.

  • docs/rfcs/README.md — explains RFC vs. ADR vs. docs/archives/ (the informal precursor to this convention, left untouched), when to bother writing one, the format, and a Further Reading section with the sources behind this design (Pragmatic Engineer's RFC/ADR workflow piece, a company-examples survey, a broader design-doc-practices gist, and the OpenBMC design doc guidelines).
  • docs/rfcs/template.md — Problem, Context, Discussion Log, Options Considered, Open Questions, Decision, Related.
  • docs/rfcs/0001-unify-installer-implementation.md — a real first entry, capturing (verbatim) the "[script]/route.ts does two structurally different things" discussion from the feat: generic project-template installer #83 review, deliberately left unresolved (Status: Exploring) per request. ADR 0006 and its README now link to it both ways.

Fixes from the #83 review

  • install-scripts.yml — clarified the scripts: vs. templates: comment (they looked identical without one; now states the real distinguishing factor — arbitrary logic vs. plain file copy — and links to RFC 0001); updated the editorconfig description to match the expanded template (PHP/Laravel, Rust, Dockerfiles, nu shell).
  • /install-scripts page — backtick-quoted text in descriptions (e.g. `prettier`) now renders as real inline <code> instead of literal backticks; each card gets an id anchor for deep-linking.
  • Home page — new "More Templates & Scripts" section listing every script/template as a chip linking to /install-scripts#id, reading the same registry the catalog page uses (no duplicated content). The catalog page wasn't linked from anywhere in the site before this.
  • Footer — adds a direct "Templates & Scripts" link.
  • README — mentions --proto '=https' --tlsv1.2 as an optional hardened curl invocation (same flags rustup uses).

Test plan

  • pnpm run build passes
  • Rendered both / and /install-scripts in both locales: chips render, link to the right anchors, anchors exist on the target cards, inline code renders correctly, editorconfig description updated
  • Prettier clean on all changed files

Notes

  • No code behavior changes beyond the two page/component edits described above — [script]/route.ts itself is untouched, as requested; RFC 0001 tracks it for later.

🤖 Generated with Claude Code

https://claude.ai/code/session_01LuKjgTCp3QuvUWqxPf7Q1y


Generated by Claude Code

claude added 2 commits July 14, 2026 19:59
Introduce docs/rfcs/ for the living discussion that precedes (and often
outlives) a decision: problem, context, options considered, and an
append-only discussion log — including verbatim AI pairing excerpts,
which is exactly the context that gets lost when only the final
decision is kept. ADRs stay short and final; RFCs hold the process.
docs/archives/ is left untouched as the informal precursor to this.

RFC 0001 captures the '[script]/route.ts does two things' discussion
from the #83 review (embedded bash-with-interpolation, and scripts:
vs. templates: being two mechanisms for the same job) without
resolving it, per request. ADR 0006 and its own README now link to it.

Site fixes from the same review round:

- install-scripts.yml: clarify the scripts: vs. templates: comment
  (they look identical without one), update the editorconfig
  description to match the expanded template, and link the comment to
  RFC 0001
- install-scripts page: render backtick-quoted text in descriptions as
  actual inline code instead of literal backticks; add id anchors to
  each card for deep-linking
- home page: new 'More Templates & Scripts' section listing every
  script/template as a chip linking to /install-scripts#id, so the
  catalog is discoverable from the home page (it wasn't linked from
  anywhere in the site)
- footer: add a Templates & Scripts link next to Features
- README: mention the --proto '=https' --tlsv1.2 curl hardening flags
  (same ones rustup uses) as an optional, more defensive install command

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LuKjgTCp3QuvUWqxPf7Q1y
Sources consulted while designing the RFC convention weren't saved
anywhere outside the chat. Add a Further Reading section listing them,
including a company-examples piece the reader found independently
(Airbnb/Amazon/Stedi templates) that complements the newsletter piece
already cited.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LuKjgTCp3QuvUWqxPf7Q1y
@vercel

vercel Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
devmagic Ready Ready Preview, Comment Jul 14, 2026 10:21pm

@greptile-apps

greptile-apps Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR adds an RFC process and surfaces the installer catalog more clearly. The main changes are:

  • New RFC docs, template, and the first installer-unification RFC.
  • ADR and README links that point to the new RFC process.
  • Home-page and footer links for the templates and scripts catalog.
  • Install-scripts card anchors and inline-code rendering for registry descriptions.
  • Updated English and Portuguese messages for the new UI text.

Confidence Score: 5/5

This looks safe to merge.

  • No blocking issues found in the changed code.
  • The new catalog links use the same registry ids as the target card anchors.
  • The new translation keys are present for both supported locales.

Important Files Changed

Filename Overview
www/app/page.tsx Adds a home-page catalog section generated from the existing installer registry.
www/app/install-scripts/page.tsx Adds card anchors and renders backtick-delimited registry text as inline code.
www/components/footer.tsx Adds a footer link to the templates and scripts catalog.
www/messages/en.json Adds English strings for the new home-page and footer UI.
www/messages/pt-BR.json Adds Portuguese strings for the new home-page and footer UI.
www/data/install-scripts.yml Clarifies installer registry comments and updates the EditorConfig description.
docs/rfcs/README.md Documents the new RFC process and index.
docs/rfcs/template.md Adds a reusable RFC template.
docs/rfcs/0001-unify-installer-implementation.md Captures the open design discussion about unifying installer implementations.
README.md Documents an optional hardened curl invocation for the installer command.

Reviews (1): Last reviewed commit: "docs: save the RFC/ADR research referenc..." | Re-trigger Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants