Repository navigation
Replies: 1 comment
|
Thanks for the clear sketch, @rubicon. Yes, this fits in core as an opt-in in the user layer: nothing changes for anyone who never assigns a template. On your questions:
Happy for it to follow the four open template PRs, as you planned. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
#1692 lists an optional per-application assignment as the last item of its select-and-assign group: a specific job uses a specific template without changing the global default. The gallery (#5945, #5961), manage routes (#5962) and editor (#5963) cover the rest, and #5952 added the user template layer. I left assignment out of those PRs because it changes the PDF flow in core, and web/AGENTS.md routes design proposals to Discussions.
Today the resolver picks an explicit name, then the profile default, then the base template (loadProfileDefault in cv-templates.mjs, used by modes/pdf.md).
Sketch:
Questions:
I will build this only if the shape is agreed. It would follow the four open template PRs.
All reactions