Bendik Aagaard LynghaugandClaude Sonnet 5
309e3b43df
- The page title is the only question anywhere; alternative and feature names are now statements in our voice. Where we need input we say why (the reply is personal, software lands somewhere, a proposal is a stance), then hand over the field. - The opening question's alternatives become the statements we'd like visitors to get behind: "Good software begins with a clear argument", "Attention is earned", "Capital needs reasons", "Work happens through dialogue, not tickets". - followup: true on the five post-submission pages keeps them out of the question nav until the visitor actually carries a chain. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
44 lines
1.5 KiB
YAML
44 lines
1.5 KiB
YAML
id: /develop-proposal
|
|
route: ^/develop-proposal
|
|
name: Propose a change
|
|
description: >
|
|
This site is built on the same question architecture you're using
|
|
right now — and changes to it are proposed through it. Describe what
|
|
should change and why; an owner reviews every proposal, and approved
|
|
ones become real commits.
|
|
alternatives:
|
|
- name: The change you propose
|
|
description: >
|
|
The proposed content replaces (or creates) one file in the
|
|
questions repo, verbatim — so it has to be complete, valid YAML
|
|
for that file, not a diff.
|
|
action: /proposed
|
|
consequence: [Propose it]
|
|
record_as: development_proposals
|
|
encouragements:
|
|
- Every proposal gets read by a person before anything moves.
|
|
features:
|
|
- name: Sign it
|
|
description: >
|
|
A proposal is a stance — it carries a name, and an address
|
|
if you want the outcome to reach you.
|
|
requirements:
|
|
- name: submitted_by
|
|
label: Name (or what to call you)
|
|
- name: email
|
|
label: Email
|
|
type: email
|
|
optional: true
|
|
- name: The change
|
|
description: ""
|
|
requirements:
|
|
- name: target_path
|
|
label: File path
|
|
placeholder: questions/example.yaml
|
|
- name: rationale
|
|
label: The rationale
|
|
type: textarea
|
|
- name: proposed_yaml
|
|
label: Proposed file content (complete YAML)
|
|
type: textarea
|